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

When I execute the command

netsh http show iplisten

It returns a list of IP addresses I added manually:

IP addresses present in the IP listen list:


However, when I run

netstat -an

None of the IPs above are listed. What is even weirder is when I try to add an http binding on a website through the IIS Management Console, the available IPs to choose from is d, e, f, g - even though I've specifically removed d. Of course, a, b, and c are not available.

I have already reinstalled IIS on the server. What else can I try beside reinstalling the server now?

share|improve this question
How were the IPs added to the listen list - the netsh commands? Is it still listening on, or was that removed? – Shane Madden May 9 '12 at 20:36
Yes, they were added using netsh commands. No programs are listening to port 80 at I didn't explicitly remove the binding. – Wei Wong May 9 '12 at 23:55
Are there any bindings at all on port 80? (IIS is running, right?) – Shane Madden May 10 '12 at 3:20
Yes, it is, WWW Publishing service is running and the Management Console claims the server is running. Nothing is bound to port 80. – Wei Wong May 10 '12 at 12:52

Turns out that the web host assigned the wrong IPs. Even after adding the IP addresses to the network adapter and IP listen list, IIS somehow figured the IPs were not going to work and simply not list them.

I couldn't find anything in the event viewer to suggest IIS' failure to bind. Anyway, we now know how IIS deals with shady IP addresses and I wasn't crazy.

share|improve this answer

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.