By Eric Harlan
Published: May 23, 2011
Updated: May 23, 2011
Print    Email

I saw a VERY interesting little issue today that had SharePoint completely unresponsive. I’ve have literally never seen this issue.

Went on site today and the customer was speaking of an issue that was happening with their SharePoint environment. The environment was on VMware 4.x, which ended up being a very big piece of the puzzle. 

For some reason every time the server was rebooted the NIC cards on two of the virtual machines couldn’t find the network.  The reboot was causing the NIC to not be able to detect the network and as a result was defaulting to NIC settings that were making it unable to connect to its own virtual private network.

After some investigation, it was determined that the two servers in question had recently installed the latest version of NetMon on them.

NetMon and its driver were making it so that the Network Locator Assistant Service couldn’t correctly ID the network security settings and kept the settings that were enabled for this NIC from applying.

After we removed NetMon and rebooted the servers the NIC was able to find its settings and connect to the private network.

Amazing, and another check in the box for why I’ve always preferred Hyper V.

Submit Article

40776 Views - View Comments (0)