I am using DNN as the foundation for our company Intranet and have the system functioning great but have run into a snag in allowing a remote site access to it. The remote site is a company that is connected with a persistant VPN and a static route to the main office's subnet. DNS is also set with a forwarder to the DNS server in the main office.

The old Intranet was a static site with .htm files run on IIS (win2K3) on port :83 and displays fine in both locations. The new DNN site will display fine for the main office, any remote user that VPN's into the main office, the Server at the remote location, any user that VPN's into the remote locations server, BUT none of the desktops in the remote location can see the new Intranet.

If I add a index.htm (hello world) file in the main directory of my DNN site and change the Documents in IIS for Index.htm to be the top Doc. Everyone can see it.
 
Using Fiddler on the default.aspx page I can see the return of a page with a DNN Error page with Server 2003 in the page. This does not show in the browser but only in fiddler.

I am using the IP address in the address to the Intranet (http://192.168.xxx.xxx) and the new Intranet resides on Port 80. 

I have Alias's setup on the portal for the IP address of the webserver and also the VPN adapter.

It seems that DNN is being reached but something isn't allowing the .aspx page to be displayed but will allow a .htm one.

I have tried everything I can think of to get this to work but could really use some suggestions since I have only been working with DNN a short time.