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
Shawn WoodsSenior IT ManagerAsked:
Who is Participating?
I wear a lot of hats...

"The solutions and answers provided on Experts Exchange have been extremely helpful to me over the last few years. I wear a lot of hats - Developer, Database Administrator, Help Desk, etc., so I know a lot of things but not a lot about one thing. Experts Exchange gives me answers from people who do know a lot about one thing, in a easy to use platform." -Todd S.

gheistCommented:
Can you access the network from server's desktop?
There is recent patch to afd.sys rolled out by microsoft. Do you have good e1000 driver? Like one in windows catalog...
0

Experts Exchange Solution brought to you by

Your issues matter to us.

Facing a tech roadblock? Get the help and guidance you need from experienced professionals who care. Ask your question anytime, anywhere, with no hassle.

Start your 7-day free trial
Shawn WoodsSenior IT ManagerAuthor Commented:
No, I was not able to access the network from the server.   The network drivers are Windows and from 2008, so I would say updating these would be a good start.   Do you have the KB# or l ink for the afd.sys patch?
0
gheistCommented:
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.
0
compdigit44Commented:
Have you tried to switch to vmxnet3?

https://connect.nimblestorage.com/thread/1516
0
It's more than this solution.Get answers and train to solve all your tech problems - anytime, anywhere.Try it for free Edge Out The Competitionfor your dream job with proven skills and certifications.Get started today Stand Outas the employee with proven skills.Start learning today for free Move Your Career Forwardwith certification training in the latest technologies.Start your trial today
Windows Server 2008

From novice to tech pro — start learning today.