Windows Server NIC in Unknown state

So I have noticed if we have a Windows server (monitored via WMI) where the NIC on it goes into an Unknown state the statistics seem to "hang" and the node has to be deleted and re-added to get things to start working "normally"... Has anyone else seen this and come up with a different solution?

Find more posts tagged with

server 2012

Accepted answers

All comments

llemieux

I know this is from over a year ago, but I've been able to get around this by just deleting the unknown NIC, performing a rediscover on the node, and then listing the nodes resources.

My issue with this though, is that sometimes when I attempt to relist the nodes resources after doing a rediscover, it tells me that the node is unreachable or currently unavailable even tough it's still being monitored.

I've then noticed that when I attempt to test the credentials being used for WMI polling on the server, the credential test fails. This is the oddest part as these are the credentials this server, and all of our servers, use for polling in the environment.