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.
|What is checked out and how big is it?
|Cut the (Cable) Cord
Updated: August 28, 2013
|Nokia Lumia Stuck on Gears
Updated: August 26, 2013
|IE 10 and SharePoint Explorer View
|Using 301 Redirect URL Rewrite module to Redirect SharePoint urls
|Hide Search Box in SharePoint Online
Updated: May 9, 2013
|So you want to brew beer
Updated: April 30, 2013
|The Sponsor role in SharePoint Saturday