Remote Desktop

I have a group of servers all in the same subnet.
One of the nine refuses much of the time to accept remote desktop requests.  The other eight do so quite snappy.  Sometimes after I've tried and its timed out for four or five times it will suddenly connect.
If I am looking at computer management or the services or such of one of the machines (right click - connect to another computer) and try to connect to others again no problem except for this one machine.

It didn't used to be this way?  What can I do to make connections to this machine more reliable/timely?

Who is Participating?

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

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.

JohnBusiness Consultant (Owner)Commented:
On the problem server, check the firewall to make sure it is allowing requests.

Again on the problem server, run TCP/IP Reset and DNS Flush.

Open cmd.exe with Run as Administrator
Then  netsh int ip reset c:\resetlog.txt
Also, ipconfig /flushdns followed by net stop dnscache followed by net start dnscache
Then restart the Server.

You might also ensure all Windows updates are current.

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
Chris HInfrastructure ManagerCommented:
On a workstation you know that has intermittent connectivity issues, can you do a:

ping -t serveripaddress

You should receive replies if ICMP isn't being blocked.  From there, try connecting to the server via remote desktop.

I'm interested to know if when you can connect you're getting replies and when you're not, you're getting timeouts.

This would indicate network connectivity issues.  Are you virtualized?

Are you using any teaming or advance vswitch feaures?  

Was this sserver p2v'd?  Do you have more than one nic?  Have you checked nic binding and adpater order?  Have you checked to see if you've implicitly set a network adapter on you RDP connector in rds configuration?
Chris HInfrastructure ManagerCommented:
I had a similar issue where one of my servers in a TS farm was on a teamed nic, but the physical switch it was plugged into didn't recognize it.  It would commonly refuse ts connections.  Make sure if it is virtualized, you're using the recommended adapter type and not vmxnet adapters for the guest operating system in question when testing.
JohnBusiness Consultant (Owner)Commented:
@David. - Thanks and I was happy to 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 Server OS

From novice to tech pro — start learning today.