I have a DNN site set up on my windows XP machine locally with configuration shown below:

OS Version: Microsoft Windows NT 5.1.2600 Service Pack 3
Web Server Version: Microsoft-IIS/5.1
.NET Framework Version: 4.0.30319.1
ASP.NET Identity: PC1\ASPNET
Computer Host Name: pc1
Physical Path: C:\Inetpub\wwwroot\dnn
Site Url: localhost/dnn
Relative Path: /dnn
The home page of the site viewed locally is: http://localhost/dnn/Home.aspx

I'm trying to configure hosting this site over the internet using dyndns, which points to my router IP address with a port forward to the XP machine.
I can successfully point to a test index.htm file located in root of C:\Inetpub\wwwroot and view it from outside my router.
What do I need to do to get my Home.aspx file to be called? I'm probably missing some basic understanding of IIS and DNN.

Thanks for any advice.

Thanks, that did the trick!. By the way, is there any way to get around having to append the /dnn folder name to the end of my url, or is that just the way it is? /dnn is the relative path. Thanks again.

I have somewhat similar situation to Tony's (a site hosted by No-IP.com) on IIS 7.5, Win7 64-bit, DNN 6.0.1 and I can't cope with relative paths to files on my localhost/dotnetnuke server vs. the same files on my www site.

The physical path on both is the same: "C:\inetpub\wwwroot\dotnetnuke" by they differ in relative paths:

local is "/dotnetnuke"
remote is "/"

I have both aliases pointing to:
on localhost: "localhost/dotnetnuke" (default) and my site's URL (without the "http://")
on remote: my site's URL (without the "http://") (default) and "localhost/dotnetnuke"

For obvious reasons and due to such discrepancy I need to write code focusing on my remote website relative paths.

Is there any way of matching the relative paths in both locations?

Any straightforward advice would be appreciated - even that that I will have to live with such DNN's feature.

---