On Mon, 20 Aug 2012 19:04:38 +0100 Mick wrote: ...[snip]...
> You're welcome. BTW, port 22 in your example above does not *have* > to be port 22. As a matter of fact if it isn't, it would avoid > zillions of connection attempts by stupid botnets that could drive up > your bandwidth consumption. It could also be the same port as the one > you use at your local host. Whichever port you choose, you'll have to > allow it through the firewall at the remote machine and of course > whichever application is running at the remote host that you want to > connect to, should be listening on said port. -- > Regards, > Mick The remote machine(s) were set up by someone else. My firewall deals with port 22 by periodically checking for multiple failed logins from the same IP address and then blocking that address. The list gets long, but with the automatic handling, it's not a problem :->
