Hi,

 

I have a new installationof DNN 4.3.1 on a Windows Server 2003 R2 webserver at my work that is behind the institution firewall. The site is installed as an http site within the wwwroot directory of C:\inetpub. I can connect to the intranet via a Citrix VPN connection. While the site works fine within the WAN, when I try to connect through the VPN it fails. Also fails on a different installation using Windows XP workstation running ASP.net 2 and DNN4.0. My current intranet site runs on  MS Community Starter Kit website running ASP.net 1.1 architecture and I have no problem connecting via the VPN. I can successfully browse to a regular .htm page through the newer site ( DNN 4.3.1) but not the .ASPX page. Any Ideas? could it be a SQL2005 Express permissions issue. I did a default install using VWD2005 and DNN 4.3.1 Starter Kit. I've checked all IIS permissions, ASP.net version, DNS settings etc. I created an incoming connections object in the network connections and permitted all possible users including the IUSR system account and ASPNET machine account. I have alias settings for the portal referring to the webserver both by name and IP address. Also there is another domain on our intranet which is not forrested with ours, but still within the WAN and connects through DNS. A connection from a workstation in that domain also fails in the same way  including successfuly navigating to the regular .htm page.

 

any suggestions or thoughts would be greatly appreciated.

 

Hal Saville

Hi,
I'm having a similar problem.
I believe is something related with DNS and the ALIAS Setting of the Portal (Host > Portal).

I was able to get everything working adding as ALIAS the IP address.
After that you have to reach your website using the IP like:

http://192.168.0.1/dnn/

I did plenty tests. In my case it doesn't work if I connect the Portal with an URL like (also after adding the computer name as ALIAS):

http://mycomputer/dnn/

Please consider this just as a guess because I'm really a novice in DNN installation. Furthermore this isn't (for me at least) an acceptable solution, just a work-around.....

Kind Regards

Here's an update... I'm hoping that something here will click.

 

I am able to reach an .htm page here and even an .aspx page so long as there is no data actually being called ( no active controls operating). I am wondering if there is something with the SQL, some port that needs to be open for the Citrix Secure gateway VPN ( formerly Net6) or perhaps some other lockdown of the SQL Server surface area manager that needs to be loosened or enabled.  also does access differ depending on whether I install as a virtual directiry vs. installing within the default website folder ie: C:\inetpub\wwwroot\Sitename?

 

Hal