This alert message is generated when OpManager server fails to contact the monitored device during its periodic availability status poll. This error generally appears in a VM environment where the Virtual devices are running any Windows OS and when they are unable to reach outside the network due to any of the following causes.
This error occurs in your VM when there is a possibility of WinSock and WinSock2 setting being corrupted.
You could try to point to the following registry paths:
This issue is caused by a duplicate Security Identifier (SID) in a Windows 2008 or Windows 2012 virtual machine, when the either of them are deployed from a template or a cloned virtual machine. And the guest customization option is not selected while deploying the virtual machine.
To resolve the issue, you need to run the sysprep tool to generate a new security identifier for the virtual machine. To do this,
When you are unable to ping the loopback address/local setup, there are chances of your TCP/IP stack being corrupted.
Turn off User Account Control (UAC) and login with the domain admin account. Follow the below steps to reset TCP/IP to its original state:
netsh int ip reset resetlog.txt
When you run the reset command, it overwrites the following registry keys, both of which are used by TCP/IP: