OK, I think I have found a work-around.

The trick seems to be having two entries in the PortalAlias table - both with and without the extra port number. Just to recap my config so those trying to figure this out can reproduce it on their side, here is what I have setup.

1. IIS is configured for port 8088 only, and no host headers. (I haven't confirmed if the host header makes any difference)
2. I have two entries in my PortalAlias table, which I added manually.
    mydomain.com:8088 and mydomain.com (in that order)
3. I have Friendly URLs turned ON (turning them off removes the requirement for the second alias entry)
4. I have UsePortNumber set to true in web.config.

I can access the site via mydomain.com:8088, and mydomain.com does not work (as expected) since IIS is not listening on that port.

I'm not sure why I would have to have both entries in there if the site is only configured for port 8088, but it seems to work in my limited testing. I guess if I get some time, I will look in the code and try to figure out why this is the case.

--Eric

Url are ok with port number, but some bugs persists...  :

If I create a child portal and I'm going to its admin menu, I continue to get error 404. I can only go to the admin menu of root portal ! Anyone can confirm please ?

I test with 5.1.1 ; I don't think it's better on 5.1.4.

I have tried adding portal alias with port number in version 5200 of DNN. I couldnt add portal alias with port number in this version as well, but i added portal alias in the portal alias table with port number in the database directly.

when i try to got to page it gives me error :

Server Error in '/DNN5200' Application.

---

The resource cannot be found.

I have  <add key="UsePortNumber" value="true" /> in web.config.

this is specially happens when i redirect to one page to other.

Has anyone got idea on this?

Thanks