G
GFBryan
Guest
Hello, everyone. I have a very weird issue with Remote Desktop that just started a few days ago. My setup: I have a Windows 7 computer (stand alone Lenovo desktop), connecting over remote desktop to a Windows 10 (virtual desktop running on VMware - we'll call this the REMOTE computer). For close to a year now, this has worked flawlessly, but a few days ago the following issue started to occur.
If the user on the Windows 7 computer is idle for a certain period of time on the remote desktop window (haven't been able to pinpoint the timing), they will lose their connection, and the remote desktop window will close. When they go to reconnect, they get the following error: "can't connect to the remote computer". The error message is INSTANT with no time delay. The main fix I have working now is to open up the console via VMware to the REMOTE computer, and login "locally". This seems to kick the REMOTE computer back into gear, and my RD user can reconnect. Sometimes however even this doesn't do the trick, and I have to restart the REMOTE computer to get it working.
I've experienced the same issue trying to connect to the REMOTE computer from MY Windows 10 laptop, and the problem persists. Because of this, I believe it has something to do with a sleep/timeout issue on the REMOTE computer or maybe a problem with the Remote Desktop service on it.
Anyone have an idea on what is causing this and how to fix?
Thanks!
Bryan
More...
If the user on the Windows 7 computer is idle for a certain period of time on the remote desktop window (haven't been able to pinpoint the timing), they will lose their connection, and the remote desktop window will close. When they go to reconnect, they get the following error: "can't connect to the remote computer". The error message is INSTANT with no time delay. The main fix I have working now is to open up the console via VMware to the REMOTE computer, and login "locally". This seems to kick the REMOTE computer back into gear, and my RD user can reconnect. Sometimes however even this doesn't do the trick, and I have to restart the REMOTE computer to get it working.
I've experienced the same issue trying to connect to the REMOTE computer from MY Windows 10 laptop, and the problem persists. Because of this, I believe it has something to do with a sleep/timeout issue on the REMOTE computer or maybe a problem with the Remote Desktop service on it.
Anyone have an idea on what is causing this and how to fix?
Thanks!
Bryan
More...