problem seeing IIS Website on a LAN

problem seeing IIS Website on a LAN

am 27.07.2007 12:06:54 von cjspin

I have created a simple website on ISS on my local machine running XP
pro. It works locally using http://localhost or http://[ipaddress]

The problem is that I cannot see it from other PCs on the LAN, even
though they are in the same workgroup as my PC, and even though I can
ping my machines IP Address from the other machines. To try and open
the website from the other machines I am using an address of the form
http:/[ipaddress]. My default IIS website is running on port 80.

Not being a networking expert I cannot think what to test next. Any
suggestions would be welcome.

Re: problem seeing IIS Website on a LAN

am 27.07.2007 12:19:09 von David Wang

On Jul 27, 3:06 am, cjspin wrote:
> I have created a simple website on ISS on my local machine running XP
> pro. It works locally usinghttp://localhostorhttp://[ipaddress]
>
> The problem is that I cannot see it from other PCs on the LAN, even
> though they are in the same workgroup as my PC, and even though I can
> ping my machines IP Address from the other machines. To try and open
> the website from the other machines I am using an address of the form
> http:/[ipaddress]. My default IIS website is running on port 80.
>
> Not being a networking expert I cannot think what to test next. Any
> suggestions would be welcome.



Are you running personal security software and/or firewalls on the XP
Pro machine. They can block other PCs from seeing your website.

Being able to PING between machines says nothing about ability to HTTP://
between machines -- totally different network protocols and ports. The
only thing PING proves is that the physical link between the machines
is there, so the issue is caused by some user misconfiguration.

You can check the IIS website log files to verify that the requests
from other LAN PCs do not reach IIS -- which combined with PING saying
other PCs can reach the XP Pro PC, it says that something running on
the XP Pro PC is intentionally blocking access.


//David
http://w3-4u.blogspot.com
http://blogs.msdn.com/David.Wang
//