Thanks Peter -----Original Message----- From: [EMAIL PROTECTED] [mailto:[EMAIL PROTECTED] On Behalf Of Peter Machell Sent: Tuesday, 4 July 2006 6:13 PM To: General Practice Computing Group Talk Subject: Re: [GPCG_TALK] Knock, knock
On 04/07/2006, at 6:01 PM, Dr John Van Dyck wrote: > 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. No, the connection is tunneled over 22 and you end up with the local host listening for a connection on port 3389. You only need to allow 22 through the firewall. If you have something like zone alarm on you may need to allow 3389 locally - turn off the firewall to debug. > 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 In \home\john\.ssh where john is your username. Note the period before ssh - this specifies a hidden directory. authorized_hosts should be created in there the first time you connect using ssh - connecting to localhost will do it. If not, just $ touch ~/.ssh/authorized_keys cheers, 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
