0
Is it possible to increase the timeout time for attempting to connect to a computer using Windows Remote Desktop client?
My Windows Server 2012 computer was running very slow yesterday, and then became unresponsive. This morning, I was able to get a single ping reply from it, which leads me to assume it's on and functioning, just very very slowly. As it stands, RDC just fails to connect, but I hypothesize if I can increase the timeout time, it might be able to connect so I can reboot the machine. Is it possible to do this? Is there any way to increase the Remote Desktop Connection client's connection timeout/number of attempts?
I would suspect that increasing the timeout to connect (if you can find a way to do it) is not going to help when following packets are coming too slow for the connection to hold. – Ƭᴇcʜιᴇ007 – 2013-12-18T16:56:51.633
I don't have physical access to it. It's a server I left in my apartment, but since I'm home for the holidays I can't get to it, and I was an idiot and didn't enable any other ways to access it besides remote desktop. – 404 Not Found – 2013-12-18T16:58:30.220
Crappy. For future reference: Remotely turning on or rebooting a frozen computer :)
– Ƭᴇcʜιᴇ007 – 2013-12-18T17:20:58.337Try using an alternate RDP client like freerdp? My guess is that it won't help though. – Zoredache – 2013-12-18T17:51:55.417
Unfortunately, it looks like freerdp is made to be built on Linux/Mac. I could try to get a PC ready to build it for Windows, but I don't feel like going through the trouble right now. Though to maybe prove my point, further attempts to connect have gotten beyond "Initializing remote connection" all the way to the "securing remote connection" stage. That initializing part seems to be the problem area that stops if it takes too long; latter stages will go on for a while before they quit. – 404 Not Found – 2013-12-18T20:06:09.930