When attempting to connect via ssh -L 3389 etc etc  does the firewall/router
have to have any specific instructions report 3389??    I keep getting an
error message that ssh is not able to forward to that port.  

-----Original Message-----
From: [EMAIL PROTECTED] [mailto:[EMAIL PROTECTED]
On Behalf Of Dr John Van Dyck
Sent: Tuesday, 4 July 2006 11:04 AM
To: 'General Practice Computing Group Talk'
Subject: RE: [GPCG_TALK] Knock, knock

The other thing I had problems with Peter is the password/keys
I could generate the keys ok but could not find a file authorized-keys to
copy them into.  Where is this supposed to be    ? in home\ssh  or in \etc

-----Original Message-----
From: [EMAIL PROTECTED] [mailto:[EMAIL PROTECTED]
On Behalf Of Peter Machell
Sent: Tuesday, 4 July 2006 10:42 AM
To: General Practice Computing Group Talk
Subject: Re: [GPCG_TALK] Knock, knock

It's a standard SSH command line:

ssh [EMAIL PROTECTED] -L 3389:192.168.1.10:3389

Where 192.168.1.10 is the internal IP of the computer you want to  
connect to.

Once you authenticate you will be in a shell which needs to stay  
open. Minimize this and start an RDP connection to localhost (or  
127.0.0.1).

This is the same way you connect from any host using SSH, except  
Windows XP, as localhost connections are forbidden, but you can  
connect to the address 127.0.0.2

So the connection there would be:

ssh [EMAIL PROTECTED] -L 127.0.0.2:3389:192.168.1.10:3389

then RDP to 127.0.0.2

regards,
Peter.
_______________________________________________
Gpcg_talk mailing list
[email protected]
http://ozdocit.org/cgi-bin/mailman/listinfo/gpcg_talk


_______________________________________________
Gpcg_talk mailing list
[email protected]
http://ozdocit.org/cgi-bin/mailman/listinfo/gpcg_talk


_______________________________________________
Gpcg_talk mailing list
[email protected]
http://ozdocit.org/cgi-bin/mailman/listinfo/gpcg_talk

Reply via email to