I had an interesting experience trying to run Windows Updates this weekend. One of the servers didn’t come back up after I rebooted it. — At least that is what I could tell from home. I ran to work in the middle of the night to find the server up. The funny part of this is that I could not access any of the services running on the server, however from the server I could access other services on the network.
Anyway, because I can connect to other devices on the network, that ruled out a hardware issue. So I checked the event log. There I found this event:
Event Type: Error
Event Source: ipnathlp
Event Category: None
Event ID: 32009
Date: 8/12/2010
Time: 3:32:36 AM
User: N/A
Computer: Server
Description:
The Windows Firewall/Internet Connection Sharing (ICS) service could not start because another program or service is running that might use the network address translation component (Ipnat.sys). This can occur when Routing and Remote Access is enabled. If this is the case, you must disable Routing and Remote Access before the Windows Firewall/Internet Connection Sharing (ICS) service can start.
For more information, see Help and Support Center at http://go.microsoft.com/fwlink/events.asp.
Hmm. I go and check the services running and it doesn’t show Windows Firewall/Internet Connection Sharing running, but it is set to start automatically. I then changed the startup to disabled, reboot the server and everything starts to work again magically (Except for IAS —- And that could be broken because of some other things I did to the server). So if you are having odd connection problems, make sure that Windows Firewall/ICS is not running or attempting to start at boot.
Share on Facebook
