Tags: 1deault, 80iis, access, addresses, iis, localhost, microsoft, msdn, responds, siteall, software, solution, sp2, unassignedport, web, windows

XP SP2, can access IIS through localhost and 127.0.0.1 but no other addresses

On Microsoft » Microsoft IIS Development

4,073 words with 3 Comments; publish: Fri, 23 May 2008 10:25:00 GMT; (300140.63, « »)

I have seen this problem posted by many but have never seen a solution.

Windows XP SP2.

IIS 5.1

Deault Web Site

All Unassigned

Port 80

IIS responds to connections on localhost or 127.0.0.1 but nothing else.

No other IP addresses nor the computer name will allow a connection.

I have reinstalled IIS without any change.

I can telnet to localhost and 127.0.0.1 on port 80 and get a

connection. No connection with any other address.

I have tried changing to different ports and it has the same results.

Only localhost and 127.0.0.1 accept the connections.

There are not any firewalls installed and the Windows Firewall is

disabled.

I have checked the security policies. The user that IIS is using for

access is set to allow and I have compared this with a machine that

works without a problem to verify they are set the same. I have copied

over the Metabase.bin from a working computer with no change.

Anyone have any ideas at all?

Thank you.

All Comments

Leave a comment...

  • 3 Comments
    • I am having the exact same problem. I had posted this sometime ago but could

      not be resolved.

      Several of our installations are having this problem. Mostly XP SP2.

      We checked all anti-virus settings and firewall settings.

      Any help would be appreciated.

      Thanks

      Vikram

      "Nathan" <nhicks.iis.todaysummary.com.gmail.com> wrote in message

      news:1137002311.711305.233840.iis.todaysummary.com.g43g2000cwa.googlegroups.com...

      >I have seen this problem posted by many but have never seen a solution.

      > Windows XP SP2.

      > IIS 5.1

      > Deault Web Site

      > All Unassigned

      > Port 80

      > IIS responds to connections on localhost or 127.0.0.1 but nothing else.

      > No other IP addresses nor the computer name will allow a connection.

      > I have reinstalled IIS without any change.

      > I can telnet to localhost and 127.0.0.1 on port 80 and get a

      > connection. No connection with any other address.

      > I have tried changing to different ports and it has the same results.

      > Only localhost and 127.0.0.1 accept the connections.

      > There are not any firewalls installed and the Windows Firewall is

      > disabled.

      > I have checked the security policies. The user that IIS is using for

      > access is set to allow and I have compared this with a machine that

      > works without a problem to verify they are set the same. I have copied

      > over the Metabase.bin from a working computer with no change.

      > Anyone have any ideas at all?

      > Thank you.

      >

      #1; Fri, 23 May 2008 10:26:00 GMT
    • On 11 Jan 2006 09:58:31 -0800, "Nathan" <nhicks.iis.todaysummary.com.gmail.com> wrote:

      >I have seen this problem posted by many but have never seen a solution.

      >Windows XP SP2.

      >IIS 5.1

      >Deault Web Site

      >All Unassigned

      >Port 80

      >IIS responds to connections on localhost or 127.0.0.1 but nothing else.

      >No other IP addresses nor the computer name will allow a connection.

      >I have reinstalled IIS without any change.

      >I can telnet to localhost and 127.0.0.1 on port 80 and get a

      >connection. No connection with any other address.

      >I have tried changing to different ports and it has the same results.

      >Only localhost and 127.0.0.1 accept the connections.

      >There are not any firewalls installed and the Windows Firewall is

      >disabled.

      >I have checked the security policies. The user that IIS is using for

      >access is set to allow and I have compared this with a machine that

      >works without a problem to verify they are set the same. I have copied

      >over the Metabase.bin from a working computer with no change.

      >Anyone have any ideas at all?

      Still sounds like a firewall issue. Or other security software.

      Jeff

      #2; Fri, 23 May 2008 10:27:00 GMT
    • Yes, it appears it was Norton Antivirus and it's internet worm

      protection. I can't believe it was such a simple thing as that.

      #3; Fri, 23 May 2008 10:28:00 GMT