Who am I:
I am a proficient DNN user from the 3.X days as many of us are. I currently run 18 DNN sites on my server. I am very versed in all manners of installs and DNN mgmt (except upgrades, I suck at that). Very few problems to date.
Here is my configuration:
Web Server – IBM, 8 processor, 16gig Ram, 1TB HD Raid
SQL - SQL 2005 Enterprise
OS – Windows Server 2003 Enterprise 64 bit
DNS – Host my own DNS
DNN – 4.5.01 (14 sites DNN 4.5.01, 4 sites DNN 4.4.0)
Firewall/Router – Microsoft ISA 2006 using NAT
IP addressing – Single public static IP address. All 18 hosted sites are using NAT to private addresses behind the ISA server.
Here is my situation:
I can setup a new DNN install of v.4.5.01 or earlier using the exact configuration listed above, with either the custom, typical, or legacy installation and it works (partially). I can login to the new install. However, I cannot go to Host settings or Admin settings because the URL reverts to my internal private NAT’ed address. For example:
When I try to go to Host settings or Admin settings my URL changes to –
http://10.8.x.x/default.aspx?tabid.....etc........Reverting to the private addressing in the URL instead of the fully qualified domain name (FQDN). I then have to remote into my server, login to DNN locally to be able to access host settings and turn off Friendly URL’s. When I do this I no longer get URL’s with internal addresses. I get URL’s with FQDN only. Once I discovered this, I posted my findings to this forum. So that is no problem. I found a work around using version 4.5.01.
I recently started playing with version 4.91 and version 5.0. I discovered the same symptoms regarding URL’s with private addresses instead of FQDN’s. So I proceeded to turn of Friendly URL’s. It appeared to provide me the same results as with version 4.5.01. However, once I go to Host settings or Admin settings, make any change I desire and I hit the “update” button, my session times out because it wants to revert to a URL with a private address. I can go back to the page and the changes took place, however there is a problem with private addressing.
For example:
I then tried versions 4.6.x, 4.7.x and 4.8.x with the same results. The only version that does not do this is version 4.5.01 and before.
My alias always is set to the internal private address, not the FQDN.
Same results even after the new alias is added.
Why is there a problem now with DNN and NAT’ed addresses?
There wasn’t an issue with this before once the Friendly URL workaround was in place.
LOGIN AND SEE FOR YOURSELF. It might help you understand better than reading my long description.
I know this is confusing, so I have setup a demo site to illustrate what is happening.
Please login and test out my problem.
This DNN site is running 4.8.04 on the same server I have listed above.
username: admin
password: password
Follow my instructions listed above and you will see what is happening.
I will take any and all suggestions, trials or configurations. I am not above making any change necessary to get this resolved. I love DNN and do not want to change to other open source portal frameworks due to this issue. I know the DNN community can solve this problem.
Developers, please help me!!! Any advanced user….. please help me!!
I can’t be the only one hosting sites using NAT instead of public IP’s for each site.
Thanks in advance for community assistance.