Server Fault is a question and answer site for system and network administrators. Join them; it only takes a minute:

Sign up
Here's how it works:
  1. Anybody can ask a question
  2. Anybody can answer
  3. The best answers are voted up and rise to the top

Within a minute of connecting to my remote Linux server through SSH, my session times out and I cannot contact the server until a few seconds have passed. Meanwhile, I'm connected to other servers without interruption. This is only happening when I establish connection from an hotel wireless AP. When I connect from my phone's Internet, the problem does not occur. Does anyone know what might be causing these unusual timeouts?

share|improve this question

migrated from May 16 '10 at 0:51

This question came from our site for professional and enthusiast programmers.

What error message do you get? Are you actively using the connection when it times-out? – Steve Emmerson May 15 '10 at 23:30
This answer has some useful info: – gareth_bowles May 16 '10 at 2:00
Sounds like the hotel's network has a really poor NAT implementation. – Zoredache May 16 '10 at 7:07

On your server, add the following line to /etc/ssh/sshd_config and restart the SSH daemon:

ClientAliveInterval 30

This will cause the server to send a message to the client requesting a response, if there has been no activity for 30 seconds. (Basically a ping to see if the client is still there).

If the hotel's firewall is kicking off "inactive" connections, this should keep your connection open as it will see activity at least once every 30 seconds.

share|improve this answer

If it only happens when you are at a hotel, then the problem is the hotel.

It sounds to me like the hotel's NAT is configured to aggressively time-out idle-looking sessions.

share|improve this answer

Your Answer


By posting your answer, you agree to the privacy policy and terms of service.