I installed a DotNetNuke 5 on an IIS 6 development server using a remote desktop. On the remote machine I can browse the website, but as the IP adress or computername is always resolved to 'localhost' i can ONLY browse the website on the virtual machine, but everywhere else in the network an error is produced (of course, as on the other computers there is no localhost running).

But I found that both on the remote machine and any other client computer only http://ip-adress/ will result in an "under construction" page, but the IP adress ist not resolved to localhost. Furthermore, trying http://ip-adresss/DotNetNuke/admin will also not resolve to localhost but simply show a "Directory Listing not allowed".
So could it be the configuration of the /DotNetNuke?

Ping to the IP works fine.

On the remote machine:
- http://localhost/DotNetNuke --> works fine
- http://ip-adress/DotNetNuke --> http://localhost/DotNetNuke --> works fine
- http://ip-adress/ --> under construction page
- http://localhost/ --> under construction page
- http://ip-adresss/DotNetNuke/admin --> Directory Listing denied

On any other computer:
- http://ip-adress/DotNetNuke --> http://localhost/DotNetNuke --> cannot work as there is not server running on localhost
- http://ip-adress/ --> under construction page
- http://ip-adresss/DotNetNuke/admin --> Directory Listing denied

First of all: Thanks you so much, that was the solution for my problem :-) At least now we can access the site from other computers. Anyways, now a new issue appeared: on every computer we now get a prompt for username and password. Although I can simply use the login which I also use to access the remote desktop to my development server, then these user details will be used for DotNetNuke too (as we are using AD). So this is not a good way to test how AD works with our other users. Before we go live we of course have to test if every user can access our site from his computer with his AD details (and if the roles etc. are correct).

Hi Jeff, regarding the Windows authentication I attached a screen from our IIS configuration. The "Integrated Windows authentication" is what we you mean, right?

After putting the site in the intranet zone now I can access without being prompted for a login, but it does not seem that user credentials are passed as I cannot see my AD user in the user account list of DNN. Furthermore I would like to know if there isn't a more convenient (automatic, central) solution, or do we really have to manually add the domain to the intranet zone on every employee computer (which would be 300+ computers to do)...