We had a similar event on a handful of our HyperV virtuals.
This is a clip of the reg file
[-HKEY_LOCAL_MACHINE\SYSTEM\CurrentControlSet\Control\Network\{4d36e974-e325-11ce-bfc1-08002be10318}\{72891E7B-0A3D-4541-BDCB-3DA62E25B6A8}]
[-HKEY_LOCAL_MACHINE\SYSTEM\ControlSet002\services\eventlog\System\Teefer3]
[-HKEY_LOCAL_MACHINE\SYSTEM\ControlSet002\services\Teefer3]
[-HKEY_LOCAL_MACHINE\SYSTEM\CurrentControlSet\services\eventlog\System\Teefer3]
[-HKEY_LOCAL_MACHINE\SYSTEM\CurrentControlSet\services\Teefer3]
Or manually remove the keys, then follow these steps: (make sure you have
local login creds)
Login locally, remove network card from device manager (will have a yellow
! next to it, remove JUST the network card, not the other stuff)
Shutdown
In hyper-v manager, remove network card for the virtual, add a new virtual
NIC (synthetic, not emulated/legacy)
Start virtual back up.
Login locally
Device will be found by windows.
Cheers,
Robert
On Tue, May 27, 2014 at 4:09 PM, Melvin Backus <[email protected]>wrote:
> Yes, we are.
>
>
>
> --
> There are 10 kinds of people in the world...
> those who understand binary and those who don't.
>
>
>
> *From:* [email protected] [mailto:
> [email protected]] *On Behalf Of *Robert Cato
> *Sent:* Tuesday, May 27, 2014 4:00 PM
> *To:* [email protected]
> *Subject:* Re: [NTSysADM] Invisible NIC - now there's no network
>
>
>
>
>
> Are you running SEP by chance?
>
>
>
> Robert
>
>
>
> On Tue, May 27, 2014 at 2:53 PM, Melvin Backus <[email protected]>
> wrote:
>
> OK, after about a day and a half looking at this I’m officially, well,
> that might get me tossed… J
>
>
>
> Sorry for the long post but I want to make sure I’ve got everything so we
> can avoided as many of the preliminary “did you” questions as possible.
>
>
>
> We had a maintenance event last week. We had to shut down all our VMs to
> make some changes to the SAN. Everything we smoothly for the most part,
> but our Lync server decided it didn’t want to play well when it came back
> up. The NIC shows up in the Network Connections GUI, but under netsh /
> ipconfig, there are no NICs, only the loopback adapter.
>
>
>
> Initial reaction was to remove/re-add the NIC which had no impact. So, we
> added a new different adapter to make sure it wasn’t a corrupted driver,
> etc. Originally it was an E1000, now VMXNET 3. Neither one shows up. So,
> since it was late, we decided they could live without it until later, we’ll
> restore from backups and move on.
>
>
>
> We came in this morning, restored the machine from backups. There was
> what we initially thought was a snapshot from the backup software as well
> as the main drive, so we only restored that. Everything comes up, talks to
> the network, I can login to the domain, all is well, we thought. 2nddrive is
> missing which as it turned out wasn’t a snapshot, it was a D:
> drive where all the IIS, etc., lived.
>
>
>
> Soo, we restored again, this time everything. Things are looking better,
> but now the domain trust is whacked, which we pretty much expected. But I
> can talk to the network, Lync clients are actually connecting, but we don’t
> want to leave it running this way so to make sure everything is back to
> normal we disjoin / rejoin the domain and **WHAT!!**. You guessed, it’s
> right back to no network again. Thinking it was something to do with the
> domain join (who knows what, but that seemed to be the when part) we’ve
> disjoined it from the domain again, but no joy, still no network. I’ve
> added an additional NIC to the VM in the hopes that I could configure it
> and move on, but no joy, regardless of the NIC type. Now the both show up
> in the GUI, but neither shows up via IPCONFIG or NETSH.
>
>
>
> This is a 2008r2 server, fully patched, running on ESX 4.1. I’ve found
> lots of links about resetting the IP stack, none of which worked, and a few
> about the hotplug capability in vsphere causing things to get removed from
> the configuration, but that isn’t consistent with this since they still
> show up both in the GUI and in the VMWare settings. (We actually have
> people do that occasionally in our VDI environment, and now I actually know
> how to prevent it. )
>
>
>
>
>
> advTHANKSance
>
>
>
> --------------------
> Melvin Backus | Sr. Systems Analyst | Byers Engineering Company |
> 404.497.1565
>
> Service Desk | 404-497-1599 | http://servicedesk.byers.com
>
> --
> There are 10 kinds of people in the world...
> those who understand binary and those who don't.
>
>
>
>
>
