6

I have a ssh server on my Windows 10 computer at home and when I set up a reverse tunnel from my Windows 10 work computer with PuTTY with this command:

putty.exe -ssh user@xxxxxxxxxx -R 9999:localhost:3389

I can use remote desktop at home and log into my work computer.

This works until I move the PuTTY window, then my local window freezes. The workaround is to do not touch that window, but that is very annoying. Is this a known problem?

To make it clear: only the window on my home computer in which I'm viewing my work computer (the remote desktop window) freezes. Everything else on my home computer works fine and when I ask my colleague who is at work to look at my work computer he says that he can see the PuTTY window with a message that the connection is lost. He is able to close PuTTY and reconnect to my home computer with the above command and everything works again until I accidentally click the PuTTY window again.

5
  • Which version of putty do you use? – vp-platform Nov 15 '17 at 8:39
  • Only the window on my home computer in which I'm viewing my work computer (the remote desktop window) freezes. Everything else on my home computer works fine and when I ask my colleague who is at work to look at my work computer he says that he can see the putty window with a message that the connection is lost. He is able to close putty and reconnect to my home computer with the above command and everything works again until I accidentally click the putty window again. – Joost Nov 18 '17 at 12:13
  • 3
    I have this same issue. To work around it, I connect and then minimize PuTTY. I still occasionally manage to restore the PuTTY window while in remote desktop which promptly freezes the session. If you just need the tunnel, maybe try plink.exe instead of a full PuTTY session. – Ouroborus Dec 8 '17 at 23:07
  • @Ouroborus thanks for the plink tip; works like a charm! If you'd post it as an answer, you'd have my vote as the answer. – Nebula May 22 '19 at 19:38
  • Same issue with KiTTY. klink.exe workaround works there too. – genpfault Mar 27 '20 at 19:30
0

The problem is manifested when the putty application is launched from the user's session, which is then connected via RDP. The problem can be bypassed if to launch putty from another user's session or to create a job that will launch putty under NETWORK SERVCE user. examble of job four launch putty from system account to permit connection to RDP trough ssh tunnel

Your Answer

By clicking “Post Your Answer”, you agree to our terms of service, privacy policy and cookie policy

Not the answer you're looking for? Browse other questions tagged or ask your own question.