Terminal Server Communication Issues

I have a Windows Server 2008 R2 Terminal Server that randomly will stop responding to pings.  When this happens the users that are on the terminal server can still work.  However, no new users nor i can remote into the server.  I nor anyone in my network operations center can ping the server when this happens.  The only solution that we have found is to reboot the server.  Has anyone come across this unusual behavior?  If so, were you able to fix it and what was the fix?  Thanks for everyone's help with this issue.

Thanks,

Chris
BosaloskiAsked:
Who is Participating?

[Product update] Infrastructure Analysis Tool is now available with Business Accounts.Learn More

x
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.

jacobstewartCommented:
I have come across the ping response issue with windows autotuning.  Perhaps try to disable autotuning and see how it goes.

netsh interface tcp set global autotuning=disabled

Reboot
McKnifeCommented:
Hi.

You should run some tests, first. When in error state, disable and enable the network interface card. Also disable the local firewall, if installed and/or active and see if ping responses return. Also see if the server still "believes" it has open ports by using the command netstat -ao

When reading your thread, first thought was "firewall or security software running wild". [Of course it could also be malware running wild]
markgossettCommented:
just a thought maybe a NIC issue?

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
BosaloskiAuthor Commented:
I ended up upgrading the nic firmware/driver and running the netsh command and so far it's looking good.

Thanks for your help.
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
Microsoft Legacy OS

From novice to tech pro — start learning today.