Remote Desktop Has Stopped Working After Successful Connection Windows 8 64 Bit But Works Fine From Other RDP Machine

Problem:
Remote Desktop Has Stopped Working After Successful Connection From Machine 1 to Machine 2. Work can be done quickly in that short time without any problems until the error occurs.

Error:
Remote Desktop Has Stopped Working

Facts:
1.     Machine 1 to Machine 2 errors after 10-15 seconds consistently
2.     Machine 3 to Machine 2 works flawlessly
3.     Machine 2 to Machine 1 works flawlessly
4.     All machines are all on an internal network.

Machines:
1 - Windows 8 64 Bit - Intel Machine - < 1 year old
2 - Windows 8 64 Bit - Intel Machine - < 4 years old
3 - Windows Server 2003 - Older HP Server

Any help would be greatly appreciated!
MAISTOAsked:
Who is Participating?
 
Jackie ManCommented:
how about Machine 1 to Machine 3?

have you tried Unchecking "Printers" in "Local devices and resources"?

Source:
http://social.technet.microsoft.com/Forums/windows/en-US/80592a1a-941a-4387-82a0-799eb8c307a6/reinstall-remote-desktop-connection-client-windows-8
0
 
Jackie ManCommented:
1.     Machine 1 to Machine 2 errors after 10-15 seconds consistently -> via wireless NIC of Machine 1?
0
 
MAISTOAuthor Commented:
They are all Cat 5 wire connected. They are all extremely stable machines as well.
0
Free Tool: Subnet Calculator

The subnet calculator helps you design networks by taking an IP address and network mask and returning information such as network, broadcast address, and host range.

One of a set of tools we're offering as a way of saying thank you for being a part of the community.

 
donnkCommented:
clear up any doubt with connectivity, open up a command prompt and "ping machine2 -t" then RDP into it. Soon as your RDP drops check the ping for a timeout and report back.
0
 
MAISTOAuthor Commented:
Good Idea. I tried it and it pings through no problem though, no connection lost even when the error comes up.
0
 
donnkCommented:
next then, is there any AV on the machine in question ?
0
 
MAISTOAuthor Commented:
Thank you! Unchecking "Printers" in Local Resources before connecting resolved the issue!
0
Question has a verified solution.

Are you are experiencing a similar issue? Get a personalized answer when you ask a related question.

Have a better answer? Share it in a comment.

All Courses

From novice to tech pro — start learning today.