Products

Solutions

Resources

Partners

Community

Blog

About

QA

Ideas Test

New Community Website

Ordinarily, you'd be at the right spot, but we've recently launched a brand new community website... For the community, by the community.

Yay... Take Me to the Community!

Welcome to the DNN Community Forums, your preferred source of online community support for all things related to DNN.
In order to participate you must be a registered DNNizen

HomeHomeUsing DNN Platf...Using DNN Platf...Administration ...Administration ...Very interesting questuionsVery interesting questuions
Previous
 
Next
New Post
4/6/2011 8:07 PM
 

THANKS,  Very thought provoking questions!!!

The server is on a 192.192.192.xxx subnet behind a several year old SonicWall firewall

 

There are 5 fixed IPs coming to the firewall.  I actually only use one of the IPs.     All port 80 IP traffic for 75.148.151.113 is a redirect to 192.191.192.15 (the web server),  The actual IP of the router firewall is 75.148.151.117.  As you would expect when I go to something like Whatismyip.com it shows server and all workstations coming from the 117 IP.

 

The only server is the one I am browsing FROM.  Normally I browse from a local workstation on same subnet. The only reason I am browsing for the server is because I want to be SURE it was on Internet.  I try to not use server as a workstation, but heck this is a fairly hot server and could easily do both..

 

Previously I had DNN on this server for many MONTHS and developed my site www.Pearland.com on it with no problem (well no problem with the dns  LOL).   I moved to a hosting company and actually reformatted that server.   Today I installed 5.6.2 on this server to do some testing and development on with effecting my main site.

 

It is a brand new DNN install and I would be GLAD to give you Host password or even give you remote access to the entire server.   The server is JUST used for my development testing and like I said, I did a reformat recently.

 

Question:  Could it be a problem that this site is Pearland.Pearland.com and my main site is Pearland.com??  Naturally I just put another DNS record that points to my server here and the main records point at web server and a email server at hosting company.  It SHOULD work ok like that???

 

Thank you for some excellent thoughts. 
Joel inHouston


Original note
A couple of questions

 - is  the web server sitting directly connected to the internet or is it behind an internal firewall (fwiw it should be)


 - are you attempting to browse to a web server that is INSIDE the same firewall / router subdomain as the computer you are browsing on.

Ok to explain:

The ip address that your give as 75.148.151.113
 - is this the physical address of the Ethernet connection of your new server ?
- or is this the physical address of the ROUTER / ADSL MODEM connection to the internet

If it is the physical address of the ROUTER - and your server is then attached to this - then you can get into some wierd issues with the way asp.net handles callback processing among other things if you dont have your router and INTERNAL DNS / domain name management configured correctly.

Westa

 

 

 
New Post
4/6/2011 9:47 PM
 
ASP.NET uses a postback system to call home to the orginateing server when you click on many buttons and links.
This system requires properly configured firewalls and dns addressing for things to behave properly.

The problem is most common in situations where you are trying to access a LOCAL server using its INTERNET side domain name and ip address.

Lets say you are sitting on a computer 192.168.1.3 and your server is 192.168.1.2  both of which are routed out to the internet thru router 192.168.1.1
that is on its internet side represented as 75.150.150.151   -  and which also redirects 75.150.150.152  BACK to your 192.168.1.2 server.
and the DNS record for myserver.com points to 75.150.150.152  with the 192.168.1.2 server itself configured to host myserver.com.

IF you browse to myserver.com from the OUTSIDE world that is any computer not inside your 192.x group -  the request arrives at the ROUTER SIDE 75.150.150.152 and is redirected internally using NAT translation to 192.168.1.2  which generates the page and passes it back thru the router to the client browser - all things good - the postbacks behave and the tricks that the ROUTER are doing with NAT are hidden to the end users browser who is happy in the belief that it talked to a server at 75.150.150.152  ---  although it really talked to a server that lives on 192.168.1.2.

BUT now you browse to myserver.com from INSIDE your 192.x. group - this is where the problems start.

You are sitting on 192.168.1.3 or any other terminal inside your local network
you try to browse to myserver.com and DNS does a lookup and gets 75.150.150.152
so it trys to connect - it hits the ROUTER coming from the inside that goes hmmm hang on - you are trying to talk to me on BOTH sides - one as OUTBOUND via the gateway 192.168.1.1 -> 75.150.150.151  and then again as inbound 75.150.150.152  oh but then i have to forward this request on to 192.168.1.2.

Which it does manage to do - it gets the request to the server which forms a page with callbacks and sends it again around this loop in your router - and across the EXTERNAL - INTERNAL router boundary.  BUT somewhere in all that things get confused BECAUSE when you hit any button that relies on the postback mechanism - IT is lost and unable to sort it ways back across this loop.  In effect the server managed to get the page to you by accident but has no way to hear the callbacks because the identity information that is being set back by the callback is confused.  

To put it another way - the callback is saying its coming from a different place than what the server expects it to be - and it doesn't get recognized correctly - it fails its validation - resulting in the server rejecting the callback and a page not found error being generated.

There are a few different ways to handle this - but the most common way is by setting up your LOCAL systems so that when they do an DNS query they are directed straight to the server locally at 192.168.1.2.

Either using HOSTS files on each local machine or thru a local DNS.

Something to thing about

Westa
 
New Post
4/6/2011 11:16 PM
 

I so very much appreciate your help.

Actually one of the BEST things about DNN is this forum and people who will help other DNN users. Heck I even got good response when I asked a STUPID question that in a matter of 15 minutes I figured out myself.   I actually posted my OWN response one (with an apology for stupid questions).

I put a host file (added to) on both machines and it did not resolve it.  I feel that DNS issue you are discussing IS a problem and I might even have something in my firewall wrong.

The Host line I added   192.168.168.15  pearland.pearland.com  and got same error as before

then I added line 75.148.151.113  192.168.168.15  and got same error as before

However, I did notice something I am confused with.   The page it can NOT find is:

http://pearland.pearland.com/port/Host/Module%20Definitions/tabid/18/portalid/0/Default.aspx

 

There is NO DIRECTORY called Host on my site and actually only one default.aspx and it is in root.  So is the file looking for one that DNN generates on the fly  RIGHT?????  For example there is NO file named http://yourdomain.com/port/Home.aspx but that is the top page of every DNN site (port is alias of my site )

 

If you would be willing, I would be GLAD to email the host password and even a way to get to the server remotely (using www.Logmein.com).   I will also email you any screen prints that might help.

 

THANKS
Joel in Houston
Email JOEL914@Yahoo.com

 
New Post
4/6/2011 11:26 PM
 
WOW the more I work with DNN the more I realize I do not understand how it works.

I went to my site (on a hosting server in Arizona) and went to add a module then select module

Here are the pages it goes to:

http://www.pearland.com/pol2/Host/Module%20Definitions/tabid/18/portalid/0/Default.aspx
http://www.pearland.com/pol2/Host/Module%20Definitions/tabid/18/ctl/Install/rtab/18/portalid/0/Default.aspx


Neither of these pages exist so obviouly DNN generates them on teh fly.

Now I think I am more confused than ever.

 
New Post
4/7/2011 9:38 AM
 
Yep - dnn generates and creates urls dynamically on the the fly.  As such all requests are actually pretty much all being made to default.aspx in your websites root directory.

Westa
 
Previous
 
Next
HomeHomeUsing DNN Platf...Using DNN Platf...Administration ...Administration ...Very interesting questuionsVery interesting questuions


These Forums are dedicated to discussion of DNN Platform and Evoq Solutions.

For the benefit of the community and to protect the integrity of the ecosystem, please observe the following posting guidelines:

  1. No Advertising. This includes promotion of commercial and non-commercial products or services which are not directly related to DNN.
  2. No vendor trolling / poaching. If someone posts about a vendor issue, allow the vendor or other customers to respond. Any post that looks like trolling / poaching will be removed.
  3. Discussion or promotion of DNN Platform product releases under a different brand name are strictly prohibited.
  4. No Flaming or Trolling.
  5. No Profanity, Racism, or Prejudice.
  6. Site Moderators have the final word on approving / removing a thread or post or comment.
  7. English language posting only, please.
What is Liquid Content?
Find Out
What is Liquid Content?
Find Out
What is Liquid Content?
Find Out