Link to home
Start Free TrialLog in
Avatar of rogue028
rogue028

asked on

IIS localhost works ip address doesn't

Hello,
I have a server running Server 2008 Standard edition with IIS 7.5.  I have a web site in iis that I can get to internally if I use localhost in the address but if I use the ip address I get page cannot be displayed.   I have checked nslookup, the bindings, and the dns on my server and they all look good.  My vendor thinks something is blocking port 80.  I'm at a loss.  We even setup a new site and cannot get to it.  

Any help would be greatly appreciated.
ASKER CERTIFIED SOLUTION
Avatar of Patrick Bogers
Patrick Bogers
Flag of Netherlands image

Link to home
membership
This solution is only available to members.
To access this solution, you must be a member of Experts Exchange.
Start Free Trial
It is the Firewal"  that blocks the World Wide Web Services port by default (Port 80).

To fix this: goto control panel,  Windows firewall

goto the Exceptions tab and Scroll  down to World Wide Web Services (HTTP).

Click the check box and click OK.

Now your machine is accessible to the outside world.

Click the check box and click OK.
Can you do these steps please:

- Confirm the binding on the website
- netstat -nob from cmd to see what is using port 80.

Thanks

Dipopo
Avatar of rogue028
rogue028

ASKER

Will do as soon as I get back to the server.  When I try by IP address I am at the server.  The bindings are set for all IP addresses.  More when I get back to shop
I have checked port 80 on the windows firewall and when I run the command netstat -nob it does not show port 80.
What if you disable the firewall?
I just realized that the netstat -nob is giving me a couple of messages in the middle of the listing.  
1.  Can not obtain ownership information
2.  X:  Windows sockets initialization failed: 5
Disable and re-enable the IP v6 on server. Also check driver\etc\ host file , if it has any wrong entries like IP is mapped to some domain address which does not exist!
Can not obtain ownership information - its a message by design and does not mention for any problem .
 X:  Windows sockets initialization failed: 5  - Its for IP v6 problem.
I disabled and re-enabled the IP v6, and the hosts file is fine.  Still cannot access by ip address or name, only localhost
So the server is in fact multihomed.. great this issue is solved.
This question has been classified as abandoned and is closed as part of the Cleanup Program. See the recommendation for more details.