Member Avatar for mustafabrew

Hi,

I have built a website that uses ASP and am running IIS on windows XP professional. On my local machine I can access the website either by going to or .

THe problem comes is that I need other computers on the network to access the site, but when they type the same thing in to their web browser, it cannot find the site/domain ip etc.

They can see my computer on the network via my network places, we are in the same workgroup, (MSHOME) and I can ping the IP and get a reply via the command prompt. However, I cannot get it access the website.

Is this an IIS setting or is it more likely that it being blocked byt the network setup? Does it have anything to do with PORT 80?

Help would be very much appreciated.

Nick

  • 3 Contributors
  • 2 Replies
  • 494 Views
  • 3 Years Discussion Span
  • Latest Post Latest Post by rezax123

Dani AI

Generated

Most likely causes: the HTTP listener isn't reachable from other machines (TCP 80 blocked by a firewall or NAT), IIS is bound only to localhost or a specific host‑header, or the site is running on a nonstandard port. raised the name/firewall angle and ’s port reminder is useful — the fact that ICMP (ping) works but browsers fail points toward a TCP/HTTP issue, not basic IP reachability.

Quick, targeted checks (run on the IIS machine and from a remote client):

On the server:
netstat -an | findstr :80

From a client:
telnet 192.168.x.y 80

Expected: server shows LISTENING on 0.0.0.0:80 or server-IP:80. A 127.0.0.1:80 or absence of a listener means IIS isn’t listening on the LAN address. If telnet times out, TCP port 80 is being blocked somewhere (firewall/router/ISP). If telnet connects, typing GET / HTTP/1.0 then Enter twice should return headers.

IIS and firewall checklist (concrete actions to correct common causes): confirm the site binding in IIS Manager → site Properties → Web Site tab — set IP to “All Unassigned” or the server’s LAN IP and remove host headers unless DNS/hosts entries exist for that name; if a custom port was used, the client must include :port in the URL; open/allow TCP port 80 in Windows Firewall (Control Panel → Windows Firewall → Exceptions) or temporarily disable any third‑party security suite to test; ensure World Wide Web Publishing Service is running.

Other items: if access is from outside the LAN, configure router port‑forwarding for port 80 to the server and verify the ISP doesn’t block port 80. Check IIS logs (C:\Windows\system32\LogFiles\W3SVC*) and the Event Viewer for refusal/errors. Note that IIS on Windows XP is intended for development and has connection limitations — use a server OS for production deployments.

Recommended Answers

All 2 Replies

Member Avatar for f1 fan

it could be a firewall issue. if they are on the same network you might be closed down on your machine on port 80 if you are running windows firewall or someother on the machine. Most likely it is because they cannot find your machine name. you say you can ping the ip but have you tried pinging the machine name? I would think this is your problem. needs dns or wins setup on the network for them to see it

Member Avatar for rezax123

dude use ur ip address rather the host name. like rather than . if ur ip address is and u setup ur website port address 4521. try it. and i think u will got ur answer. and if u r using real IP than anyone can visit ur website by this way. if u r not using real ip than only those ppl who r in ur network will c u. the problem is u didn't connect ur ip address with and domain. i hope it will help u.

Be a part of the DaniWeb community

We're a friendly, industry-focused community of developers, IT pros, digital marketers, and technology enthusiasts meeting, networking, learning, and sharing knowledge.