Awhile back, I posted a guide
detailing how you can configure CopSSH on your home computer and use it
to securely route your Windows Remote Desktop traffic in order to add
an extra layer of security to the whole process.
Typically, once Putty was configured and used to create the SSH tunnel to the remote machine, all I would need to do is simply create a loopback RDP connection on port 3390, and I was in business. In my testing of Windows 7, I found that when attempting to create a loopback connection on port 3390, I would receive an error that a connection was already established. The exact error reads as follows:
I changed Putty’s configuration to forward on port 3391 instead of
3390, and the problem was solved. I’m not sure why Windows 7
establishes some sort of connection on 3390, but at least the workaround
is pretty painless.
I just wanted to pass along this info for anyone having issues with RDP tunneling.
Typically, once Putty was configured and used to create the SSH tunnel to the remote machine, all I would need to do is simply create a loopback RDP connection on port 3390, and I was in business. In my testing of Windows 7, I found that when attempting to create a loopback connection on port 3390, I would receive an error that a connection was already established. The exact error reads as follows:
Your
computer could not connect to another console session on the remote
computer because you already have a console session in progress. |
I just wanted to pass along this info for anyone having issues with RDP tunneling.
Комментариев нет:
Отправить комментарий