Server Fault is a question and answer site for system and network administrators. Join them; it only takes a minute:

Sign up
Here's how it works:
  1. Anybody can ask a question
  2. Anybody can answer
  3. The best answers are voted up and rise to the top

I have a local website running on "localhost" on port 80 in IIS 6. On Windows XP (machine name WINXPMAC), I'm able to setup IIS 6 so that my local web application is visible on our company network. I don't even have to set up another binding for it in IIS 6. In order to do so, I go into the Windows Firewall and let port 80 through. If I'm on another machine within our intranet domain, I can go to this location to see my web application: http://WINXPMAC/default.aspx. If I'm on the machine where the web application is being hosted (on WINXPMAC), I can also visit http://localhost/default.aspx to see the site. However, I recently tried setting this up using Windows 7 and when I allowed port 80 as an incoming and outgoing port (2 different rules) in the Windows 7 Firewall, it did not work. My machine name in Windows 7 is WIN7-MAC). I want to be able to view the site on another machine on our intranet as I did with Windows XP. How can this be done?

share|improve this question
up vote 1 down vote accepted

It's the same concept in Windows 7. The bindings at the site level are in the Actions pane on the left. If you want to listen to everything on a server and you only have 1 websites, just leave the IP to (All Unassigned) and the host header blank. That will catch all traffic.

Also make sure that you can ping the server name and that it resolves to the correct IP.

Here's a short video that will bring you up to speed on this:

share|improve this answer
Thanks, that worked! The "host name" field was my issue. – MacGyver Sep 13 '11 at 14:04

Your Answer


By posting your answer, you agree to the privacy policy and terms of service.

Not the answer you're looking for? Browse other questions tagged or ask your own question.