Hi Ken,

I've attempted to get my portals to work on ports other than 80 with that element commented out, uncommented set to true and uncommented set to false.

When the element is either commented out or uncommented set to false, I can get to the portal homepage with no issues. But I can neither navigate to other pages nor can I login as in either case I get "Could not display webpage" in IE and "Can't establish a connection" in Firefox.

When the element is uncommented and set to true, I can't get to the homepage at all. I get the above errors.

And please read my first post in this thread with reference to the DNN version in question. The issue began not with the last release of DNN, but the initial cut-over from v4.x to v5.x

I very much appreciate your responding to this thread. But it's a long standing issue and I've not received a lick of help from the DNN team. I must say frankly, and yet in a friendly manner, I feel like I've been hung out to dry by the DNN team and am losing faith in the product. Please help sir! Thanks so much!

Boyd

Ken,

Thanks for looking into this. My situation is exactly the same as Boyd's, so I know I'm not crazy. The line in the config file is commented out, and I tried the same changes as Boyd, with the same results.

My environment is:

Expression Web 3

Windows 7 Pro

sqlexpress.

IIS permissions granted:

DefaultAppPool set to full control

First time I've ever had serious issues w/using DDN in the years I've been working with it. Have several sites on the production server running with the latest version of DNN as upgrades. Server is MS Server 2003 runnning Sql 2005.

I'm stumped.

Jim

I had same problem.

My environment is:

Windows Server2003/SQL2005 installed on port 99