Hi all...

I've got a new DNN 4.8.4 installed and running on a dev. server on my local domain.  Install method was done using the starter kit, using http and localhost/dotnetnuke01 as the destination.

So, I've got a virtual directory under the Default Web Site in IIS 6.0, etc.  Server is running W2K 2003 R2, SP2.

Local access to the site works great... meaning if I am at the server where I did the install, it's all good.  However, when I try to hit the site from somewhere on the LAN, I get Page Cannot be Found, using http://servername/dotnetnuke01.  Aren't you supposed to be able to hit a website like that from another machine using the servername/virtualdirectory?

I figure I'm missing something basic.  This dev box doesn't really have much else on it, so.... any ideas are appreciated.

I have added localhost/dotnetnuke01 as a site alias from w/in the new portal.

Couple additional ideas:

Have you either disabled your server-specific firewall (usually Windows Firewall) or opened port 80 on yoru dev machine?  You'll need to allow inbound connections for any http traffic.

Can you resolve the dev machine name ("ping [servername]")?

Ensure you can telnet to your dev machine from another LAN node on port 80 ("telnet servername 80").

If any of the above fail, then the problem is with your network configuration and not DNN.

Brandon

Oh, I should add that trying to visit the server's default web site also does not work.

When I just type in http://192.168.1.163, the server's IP address, I also get a Page Cannot Be Displayed.