Member Avatar for RaymondXie

Hello guys,

I have a website on a server (win2003), I have no problem open it with

but I just can't open it with

Why? How to fix it?

Thanks.

  • 4 Contributors
  • 3 Replies
  • 230 Views
  • 3 Years Discussion Span
  • Latest Post Latest Post by Muhry

Dani AI

Generated

Brief primer for the common IIS6 symptom where succeeds but http://<IP>/site does not. ’s pointer about site identity and ’s note about binding to the NIC are both on target; the explanation below clarifies the request-routing behavior and gives practical checks that go a step beyond “check the binding.”

IIS decision logic in short: an incoming HTTP request is matched by IP address and TCP port first. If more than one site is listening on the same IP:port, IIS uses the Host header to choose which site serves the request. A numeric-IP request arrives without a name-based Host header, so it will be served by whichever site is bound to that IP:port with no host name (often the Default Web Site). That is why name-based sites (bound to a host header) can work when accessed by name but not when accessed by raw IP.

Practical diagnostics (perform on the server and from a client) — confirming which component is at fault:

  • From the server, request both the loopback and the server IP: compare and http://<server-ip>/site; mismatch points at firewall/network vs IIS.
  • See which process is listening on port 80:
    netstat -ano | find ":80"
  • Confirm name resolution and which site answers: 
    ping computername
curl -v -H "Host: computername" http://<server-ip>/site
  • Temporarily stop the Default Web Site (or move its binding) to see whether raw-IP requests are being captured by another site.

Typical resolutions (based on the above results): ensure a binding exists that will accept requests addressed to the server’s numeric IP, or keep the name-based binding and make clients resolve that host name to the server IP (DNS or hosts file). For external-access scenarios also verify NAT/port-forwarding and that any firewall allows TCP/80 to the correct NIC. These tests will point to whether the root cause is IIS binding behavior, name resolution, or a network/firewall issue.

Recommended Answers

All 3 Replies

Member Avatar for freshfitz

what's the error? in iis you need to right click the website goto properties goto advance make sure is says default 80 leave host header value blank. ip (all unassigned)

Member Avatar for ramngna

Hi,
I have changed default 80 and left host header value blank. ip (all unassigned).

Even now also facing the same issue.Please help me out to resolve the issue

Member Avatar for Muhry

The IP Address you assign to the in the (IIS) Site Binding MUST match the IP assign to the NIC for the site. For example: Inside Site Binding configuration, you will have: Type---http, Port----80, IP---, whatever the Ip of the NIC configured inside your control panel/networking/IPv4. This IP must also be the same assigned by the company that host the website. Check your configuration.

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.