We're new to DotNetNuke and are thinking of using it for our new intranet site. We want to be able to show the marketing team as well as our boss all the cool stuff we can do with it. The problem is that they are on a completely different network from us (in another part of the country).

To make it easy for anyone to access my development portal I have redirected a port on the firewall to port 80 on my machine. So if you enter http://x.x.x.x:port/myDNN from the internet, your request is sent through to IIS on my machine and you can see the welcome page of my development portal.

I had to play with the aliases in the DNN portal. I added:

<local_ip>/myDNN
<computer_name>/myDNN

This all works fine until I click on a link on the DNN welcome page, which takes me to for example: http://x.x.x.x/myDNN/Login/tabid/55/Default.aspx

But the page is actually at:
http://x.x.x.x:port/myDNN/Login/tabid/55/Default.aspx

It's like DNN lost the port number. I have used port forwarding with other sites so I don't think it has anything to do with IE or IIS.

Thanks for any help.

Thanks for that. I did find a lot of helpful posts. Unfortualtely it seems like there is no easy way around the problem.

I found out that turning off friendly URLs makes a big improvement. (To turn of friendly URLs go to Host>Host Settings>Advanced Settings>Other Settings and turn off Use Friendly URLs)

Now most of the links work ok, the port number does not get stripped out of all the URLs. But some of the DNN links such as the "Search" button and the "Login" button try to take me to a URL with the port number removed... which doesn't work.

As this is only a temporary setup to show bits of funtionality we can probably get by with this. Thanks for your help mikekist.

As a matter of interest, port forwarding works (besides DNN sabotaging some URLs) with only 2 aliases:

localhost/mysite
external_ip/mysite

I imagine it only needs the second one for remote access. Adding a port number has no effect.