asked on

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

SOLUTION

jacobstewart

membership

This solution is only available to members.

To access this solution, you must be a member of Experts Exchange.

Start Free Trial

McKnife

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]

ASKER CERTIFIED SOLUTION

markgossett

membership

This solution is only available to members.

To access this solution, you must be a member of Experts Exchange.

Start Free Trial

Bosaloski

ASKER

I ended up upgrading the nic firmware/driver and running the netsh command and so far it's looking good.

Thanks for your help.