The other day I was setting up a new SQL 2005 box for a client. The base operating system was Windows Server 2008 Enterprise, and was running in VMWare. Nothing unusual about the setup at all.
Well, after installing SQL 2005, then installing SQL 2005 Service Pack 3 I rebooted it. Whenever I reboot anything I immediately start running a continuous ping so I know when that machine boots back up. Well, the pings never came back! I logged into vSphere to see if perhaps I accidentally powered it off instead of rebooting, but that wasn’t the case. It had rebooted fine. So why was it not replying to ping requests?
I checked the firewall, and it was off. I tried pinging my workstation, and that was a no go. I decided to take a look at the network settings. Sure as s#!t when I looked at the IPV4 properties for the NIC the default gateway was empty. WTF?
I manually typed in the default gateway and restored internet connectivity. Then I had to install a Backup Exec agent and reboot it again. Once again, when it came up the default gateway was blank! Seriously now! WTF?!?!?
It turns out that my coworker recently re-built our server templates in VMWare, and there was a problem with SYSPREP on the Server 2008 template. To fix my NIC I had to reset the Internet Protocol for the adapter. To do that:
- Open a command prompt as administrator
- Run netsh int ip reset
When you come back up, go back into your adapter settings, and manually put back in your static IP address. Reboot again to make sure it sticks.
Now we have to go back and re-do our template so this doesn’t happen again. Did this happen to you? Did you have to do something else to fix it? Let me know in the comments.