Lost Gateway?

No, this post isn't about the season finale of Terra Nova (though it was as good an episode as they've had, finally...). This is a strange bit about a short problem I encountered with several virtual machines in Hyper-V. In my network adapter (synth) on a few machines I've been noticing lost gateways. Since the machines were largely standalone test VMs going through the paces for eventual production use, there was little loss of function until we got to our SQL box and our ForeFront EndPoint Security install going - whereupon I realized that my SQL box was not only losing it's gateway, but also it's entire IP address.

Rather than throwing an error, the only to see the issue was to do an ipconfig, which spat back the default self-assigned IP (that pesky 169 APIPA range). These are all static address assignments, so it's not a DHCP problem. In the end, I had to wipe the IP info from the adapter with a "netsh int ip reset" command from elevated rights. Note that there's precious little in the Microsoft TechNet annals regarding this problem, but I've seen it on several VMs so far.

Odd. But it worked.

Here's to hoping that it's not a recurring problem, else I'll need to update my runonce script.