Re: SSH timing out



__/ [ Aaron Gray ] on Saturday 25 February 2006 18:42 \__

We have two remote servers both RedHat 9. One times out on SSH the
other
does not.


My initial, instinctive gut feeling: firewall. I have been down that route
before. Check firewall policies and attempt to temporarily disable it.

Okay

How do I stop the one timing out from doing so ?

It's difficult to say, but could look at your /etc/ssh/sshd_config and
enable TCPKeepAlive on the server,

TCPKeepAlive yes

It does not appear to be in '/etc/ssh/sshd_config' as this is the same on
both systems.

sshd_config config file has a KeepAlive but no TCPKeepAlive, so I tried
both, neither works.


I wouldn't have thought that descending to that level was necessary.


If the problem would be client side, then look at the
/etc/ssh/ssh_config,
there you find ConnectTimeout, setting this to 0 should prevent client
side disconects

ConnectTimeout 0


But there can still be other problems like a bed gateway in between,
which
can cause the connection to break, but thats not so common.

Yes it could possibly be the firewall router box on that server ?


If the firewall is controlled by an intermediatery box, try some simpler
SSH
tests that go in different routes. Try other remote connections like
telnet
if necessary, even ping just to ensure nothing more fundamental is
preventing a connection.

The connections fine it just times out sooner than I would like.

It may well be the firewall router as this is different from my second site
which does not timeout.

Aaron


.



Relevant Pages

  • Re: SSH timing out
    ... I have been down that route ... Check firewall policies and attempt to temporarily disable it. ... there you find ConnectTimeout, setting this to 0 should prevent client ... Yes it could possibly be the firewall router box on that server? ...
    (alt.linux)
  • Re: Web server behind Symantec Enterprise Firewall
    ... I've published a virtual IP at the Firewall to which i route the http ... NAT rule AccesoServer was chosen, but client transparency is ... Since the web server is on the LAN, you shouldn't have to add any route ...
    (comp.security.firewalls)
  • Re: Urgent RRAS wont work Help!
    ... plus it worked before without a route on the FW. ... > Where you need the extra routing is on the firewall. ... > port access rights to clients on the 184.155.0.0 network. ...
    (microsoft.public.win2000.ras_routing)
  • Re: Web server behind Symantec Enterprise Firewall
    ... It seems it does not matter wich interfaces i set at the rule, ... tries to route it trought the same interface. ... firewall to the internal sever?... ... > on the firewall to point to the web server. ...
    (comp.security.firewalls)
  • Re: Urgent RRAS wont work Help!
    ... Where you need the extra routing is on the firewall. ... route but whatever config I use it won't route. ... The clients on the ... network have the default gateway set as 184.155.0.80 via DHCP. ...
    (microsoft.public.win2000.ras_routing)