Shawn Woods
asked on
Windows Server 2008 R2 RDS suddenly stopped responding to network
In the middle of the day, our Windows Server 2008R2 RDS host suddenly stopped responding on the network. Both LAN and WAN connections wouldn't respond to PING or any attempts to log in. I was able to log into the console and see all remote sessions listed as disconnected, but the network adapter appeared to still be connected (no Red X). I checked the performance, and all usage was normal, and well below the VM's allocated resources. Checked the event viewer, and the only errors that i received was a TermDD error Event ID 56, then a Netlogon error that it could not find a DC to authenticate to.
This is the first time this has happened in the 4 months since we rolled out this server. The only was I was able to recover, was to reboot the server. All connections then came back. I am continuing to monitor this server. I can not find any clear indication as to why this happened.
This is a VM running on ESXi 5.1
Windows Server 2008R2 SP1
Single host, not clustered or load balanced.
Virtual NIC adapter type is E1000
Server NIC model is Intel Pro/1000 MT
This is the first time this has happened in the 4 months since we rolled out this server. The only was I was able to recover, was to reboot the server. All connections then came back. I am continuing to monitor this server. I can not find any clear indication as to why this happened.
This is a VM running on ESXi 5.1
Windows Server 2008R2 SP1
Single host, not clustered or load balanced.
Virtual NIC adapter type is E1000
Server NIC model is Intel Pro/1000 MT
ASKER CERTIFIED SOLUTION
membership
This solution is only available to members.
To access this solution, you must be a member of Experts Exchange.
AFD patch that breaks network drivers is
KB2975684
If you have that installed update drivers or revert it.
If not lets see what else can go wrong.
KB2975684
If you have that installed update drivers or revert it.
If not lets see what else can go wrong.
ASKER