The official blog for Windows Server Essentials and Small Business Server support and product group communications.
EPS Team Blogs
[Today's post comes to us courtesy of John Bay from Commercial Technical Support and Chris Puckett from Product Quality]
When you reboot an SBS 2008 server, you may experience some of the following symptoms:
If you run ipconfig on the SBS 2008 server you will notice that the default gateway is blank.
If you manually assign the default gateway the connectivity will be restored until you reboot the server. After you reboot the server, the default gateway may again be lost.
This issue occurs because of a problem with the netsh utility in Windows Server 2008. The issue is documented in knowledge base article 973243: The default gateway is missing on a computer that is running Windows Server 2008 or Windows Vista after the computer restarts if the default gateway is set by using the Netsh command
In certain conditions, the netsh command improperly adds a Unicode Null character before the real value for the default gateway in the registry. Note: The Small Business Server Connect to the Internet Wizard uses the netsh command to set the default gateway on the server.
Use the following steps to resolve this problem.
Here is an example of an incorrect registry value:
After you remove the blank line, the registry value should look like:
If you receive the following warning while saving the registry value, simply click OK
Is the Netsh command used/driven by the wizards in SBS? As this seems to the case with one of our clients. And we have not manually used NETSH CMD
Weird problem ... thanks for a good fix-it post!
The did fix gateway missing. Made registry change rebooted server still reverted back to missing Gateway address.
I face the same issue after i installed Network Load Balancer. once i remove NLB, then the problem got solved!!
Similar problem with missing standard gateway and additional second IP Adress visible only in GUI, not by
'netsh interface ipv4 show config'
Hotfix seems pretty old, didnt use it - problem is gone after using
'netsh interface ipv4 >Name here< reset'
and reconfigure interface using netsh
full story here (in german):