Hi!

I'm in the process of setting up an ASP service in Salt Lake City. I have a client that needs a website and I would like to use DotNetNuke as the basis for the project.

I have successfully set DNN 4.05.03 up in a localhost environment and have a prototype skin I would like to demonstrate to my client. However, I have been unsuccessful in the following:

                       a) placing my development machine outside my firewall and having my client access the site using the following syntax: 
                           (http://XXX.XXX.XXX.XXX/HDR)
                       b) installing the DNN software on one of my webservers behind my exterior firewall and getting the installation scripts to run. I am
                            able access and "Under Contruction Page" with no problem so I feel my firewall (ISA2004) is working properly and passing 
                            requests to the webserver.
                       c) less pressing, but still and issue: using Firefox 2.0 to access the site; I keep getting requests for a UID/Password.

I would be grateful for any help/counsel that could be provided.

Sincerely,

Warren Page

Hey Mike. . .

I've discovered a couple of things since the original post.

1)  Although ASP.NET 2.0.XXX showed up as installed, it apparently had not registered with IIS (wasn't showing up under IIS Web Service Extensions. I found this article ( http://office.microsoft.com/en-us/winsharepointadmin/HA100598511033.aspx ) which helped resolve the problem.

2)  I setup DNN v4.5.3 on a webserver, but when I tried to access the site to run the Installer from a machine sitting out on the internet using the actual domain name, the InstallWizard would would startup but (first clue) no images, like the left or right arrows, would show up. I could proceed to test the file permissions (responded that permissions are OK), then move on to test the database connections, which also tested correctly.

The whole thing fell apart when I got to the page where the database scripts run. The progress bar would indicate something was happening but no scripts appeared in the window where installation success is reported. Everything would hang right there. I suspected there was some kind of a file permissions problem. In setting the permissions for my D:\Website folder, I copied the permissions on the C:\inetpub\wwwroot folder and added full control for NETWORK SERVICE. When you run the install locally, everything goes as you would expect, however, even after adding a Portal Alias, when you try to access the site from the Internet, the browser indicates it's trying to load either localhost or, if the Installer ran under an internal address, the internal ip address.

Any ideas?

Warren