Dave O Connor wrote:
> The -P option makes ssh use a non-priveleged local port (in this case, you're
> using 1022, which is priveleged). Your firewall may be having issues
> sending/recieving packets on privileged ports (i.e. ports less than 1024).
> And no, you don't have to reconfigure ssh. Just go
> ssh -P 140.203.12.14
> and see if that works.
>> - DoC
ah! I see...Still doesn't work though.
ash-2.04$ ssh -v -P 140.203.12.14
SSH Version 1.2.22 [alpha-dec-osf4.0], protocol version 1.5.
Standard version. Does not use RSAREF.
tina: ssh_connect: getuid 60005 geteuid 0 anon 1
tina: Connecting to 140.203.12.14 port 22.
tina: connect: Connection timed out
tina: Trying again...
So I'm REALLY confused. I've tried sshing to another machine inside the
140.203 firewall, everything ok. And from there I can ssh to
140.203.12.14...no problems. The sys admin was good enough to give me an
extract from the firewall conf, and it confirmed that connections to
140.203.12.14 via port 22 were ok! Where the hell else do I look when
I'm not even behind a firewall myself. Have MI5 set up a ssh block on my
or something!!! ok--so I'm getting a bit carried away.... any other
ideas?
cheers,
g
Cheers,
g
--
----------------------------------------------------------
Gerard Gorman Tel. 00 44 (0)171 594 9323
Applied Modelling and Computation Group
T. H. Huxley School
Imperial College
Prince Consort Road
London SW7 2BP
U.K. o~o
-----------------------w-v-w------------------------------
Maintained by the ILUG website team. The aim of Linux.ie is to
support and help commercial and private users of Linux in Ireland. You can
display ILUG news in your own webpages, read backend
information to find out how. Networking services kindly provided by HEAnet, server kindly donated by
Dell. Linux is a trademark of Linus Torvalds,
used with permission. No penguins were harmed in the production or maintenance
of this highly praised website. Looking for the
Indian Linux Users' Group? Try here. If you've read all this and aren't a lawyer: you should be!