Hyper V - Unidentified Network

[NetworkNinja]

Hi Guys,

 

Got a small problem which we can't seem to figure out.

 

Host Server - Connected and working as expected

DC - Virtual Machine - Connected and working as expected

FS - Network Adapter says "Unidentified Network"

 

The FS was working completely fine last week & then we installed the Print Nightmare updates and since then the VM has now been working. We can't ping the server and we can't ping out from the VM. We originally thought updates killed it so removed those but same issue. Restore from the last known working backup and still same problem. Created a new external V Ethernet adapter and this still hasn't solve the problem. Like I have mentioned the DC is using the same adapter and is working fine.

 

Any help greatly apprenticed.

[ITJS2015]

Are your NIC cards Teamed on your local server ? I have disabled your Vms NIC card and enabled it again.

[NetworkNinja]

Are your NIC cards Teamed on your local server ? I have disabled your Vms NIC card and enabled it again.

 

Hi

 

Yes the NIC Card's are teamed. We have tired to disconnect/ disable the NIC Card on the affected VM however this hasn't made a difference. We have also deleted the adapter for all virtual machines and re created a brand new one but this one VM is still having problems.

[Steve21]

If you run Get-NetConnectionProfile does it show it's set to public rather than domain? If so have you tried restarting the NLA service? (Network Location Awareness)

 

If it's got upset and thinks it's public network etc would explain why the firewall would be blocking access

 

Steve

[NetworkNinja]

If you run Get-NetConnectionProfile does it show it's set to public rather than domain? If so have you tried restarting the NLA service? (Network Location Awareness)

 

If it's got upset and thinks it's public network etc would explain why the firewall would be blocking access

 

Steve

 

Morning Steve,

 

I have just tried restarting NLA however nothing happened.

[ITJS2015]

I am not sure if i am correct on saying this but is there something called WMI for hyperV connections ?

 

I had issues which my local Host could not see the connections on my server manager when i tried to used the Teaming on the NIC. I used a WMI powershell script which deleted the unknown connections and removed the VMS from HyperV but it didn't delete the VHDX.

 

Once i restarted the local server and created a new VM with the existing VHDX both of my DC and FS servers where working fine.

 

I am not saying that you should do this but it something which you could try as a last resort but out of hours.

 

I hope you get this sorted quickly

[Jaan]

Hi I had a very similar issue ages ago.

 

Mine was "not connected to a network" but work absolutely fine! it was something to do with the private/public/domain profile against the network card having a issue.

 

i ran this on the server in question:

 

net localgroup administrators networkservice /add

net localgroup administrators localservice /add

 

 

sources

https://answers.microsoft.com/en-us/windows/forum/all/you-are-not-currently-connected-to-a-network/cd7dbd92-4322-4dcf-a7f8-c6e720a60a18

[NetworkNinja]

Thanks all for your suggestions however none of them have worked. Contacted Microsoft who bent the rules and they sent 2 hours looking even though the server is Windows Server 2012 R2 which is EOL? They didn't manage to solve it until there manager came over and told them to stop lol We have now upgraded the FS to Windows 2016 and seems the issue is still occurring.

[Guest Guest]

Thanks all for your suggestions however none of them have worked. Contacted Microsoft who bent the rules and they sent 2 hours looking even though the server is Windows Server 2012 R2 which is EOL? They didn't manage to solve it until there manager came over and told them to stop lol We have now upgraded the FS to Windows 2016 and seems the issue is still occurring.

Server 2012 R2 isn't eol

[psydii]

It is past the end of mainstream support though, so investigating the problem under a pss ticket is bending the rules.

 

Server 2016 goes end of mainstream support at the end of THIS year! Jump straight to 2019 if you can.

 

Side note: SQL 2016 goes end of mainstream support today!

Edited July 14, 2021 by psydii