Greetings all,

Not sure if this is the correct forum or not, but I will start here.
Myself and my IT Crew have been fighting with DNN trying to get it working in our environment.

Ok here is what we have:

DNN Version: 4.09
IIS: 6.0 (windows 2003)
SQL: SQL Server 2005

I have the domain name www.somedomainname.com (fictional name) registered.

My IT crew told me to point that domain to IP 1.2.3.4 (fictional address) which is our corporate Proxy Server.

They set up the proxy server to forward requests for www.somedomainname.com on port 80 to InternalWebServer port 23456.  They have configured the proxy server to pass the host header along.

(I have set UsePortNumber to true in the web config.)

Now I have installed DNN.  I can get to the admin portal and do admin things by going to http://internalwebserver:23456.  No problems with this route.  This route is not using the proxy server.

I then created a new parent portal on my DNN installation using the address www.somedomainname.com (which will, as I understand it, manage all requests to www.somedomainname.com)

Now, we bounced the app pool for our site, tried to go to it from an external line and it failed.  I created a chimpy test aspx which just dumps all the request parameters and we noticed the request URL waswww.somedomainname.com:23456.

So the proxy server is converting www.somedomainname.com to www.somedomainname.com:23456 (best I can guess)

I then added a portal alias www.somedomainname.com:23456.  I bounced the App Pool.

I then navigated to http://www.somedomainname.com and I got to the right portal (I changed the content of the home page to tell me where I was).  However, now if I click on the login link, the browser hangs and eventually said it was taking to long to respond.

I noticed the address on the address bar of the page is:
http://www.somedomainname.com:23456/Default.aspx?tabid=210&ctl=Logoff

The failure makes sense as the port number 23456 is not open on our proxy server.

Now it seems this problem occurs only when attempting to do postbacks for controls.  If I am navigating to pages around the site, it seems to work without issue. 

I have tried turning off the "UsePortNumber" option, that didn't work.

I have tried putting :18002 in the web.config hostheader entry to see if it would strip 18002 off the address.  No effect.

Any one out there have some thoughts, comments, suggestions?  What am I missing?

Thanks in advance,

cmb..