Still no direction on what could be the cause of this. I dropped a generous bounty on Stackoverflow and had a few folks give suggestions, but still no ultimate resolution to this issue. I'm still forced to use Port 80 and the minute I decide to hook up any of my other portals, I'll have to tapdance around to keep the current portal on port 80.

Help???

Boyd/Jim;

Can you look in your web.config for these lines?

        <!-- set UsePortNumber to true to preserve the port number if you're using a port number other than 80 (the standard)
    <add key="UsePortNumber" value="true" /> -->

Are the commented out as above or enabled as so:

        <!-- set UsePortNumber to true to preserve the port number if you're using a port number other than 80 (the standard)  -->
    <add key="UsePortNumber" value="true" />
   

Just wondering if we managed to introduce a bug that got through upgrade scenarios in 5.2.3.

TIA;