Server Fault is a question and answer site for system and network administrators. It's 100% free, no registration required.

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've previously added two IP addresses to a Windows 2008 R2 server and it's worked fine but when I add another one to the Network Adaptor IIS stops serving any of the existing websites. Resetting IIS or restarting the server doesn't fix it.

I've tried turning off Windows Firewall and checked the Event Log but there's nothing relevant.

Any suggestions on how I can fix or debug this?


share|improve this question
Can you access other services on the machine when this happens? Are you sure the IP you are attempting to add is not your gateway or broadcast address? – devicenull Mar 25 '12 at 22:43
Did you specify in IIS which IP address applies to each website? – murisonc Mar 25 '12 at 22:59
Yes, I can FTP, RDP to the server while this is happening and each website has bindings for IP address/domain name. – Glen Mar 26 '12 at 19:33

Finally sorted this now. Turned out after I added the IP address then reset IIS, when the website tried to connect to the database server, it tried to connect from the last IP address added which was blocked by the DB server's firewall.

Someone had added a 240 second timeout to the connection string so it appeared that IIS wasn't responding when it was actually just trying for 4 minutes to connect before timing out.

Adding the new IP to the DB server's firewall fixed the problem and I've reduced that connection string timeout!

Sorry and thanks for your help devicenull & murisonc.

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.