My connection to a remote server using SSH command dies automatically after 10-15 minutes and this message appears on the screen:
----------------
Read from remote host hostname: Connection reset by peer

Connection to hostname closed.
----------------

Does anyone know what the problem might be and how to fix it?

Thanks.

Could you give us more information about your network connection?

Is it in LAN, are you using wi-fi, are you connecting to the other side of the world?

Have you noticed any other network problems?

Does it always die in exactly 10-15 minutes?

My guess is, it's not a problem of ssh but the network configuration or physical problem. More background information would probably be useful.

Thanks for the reply.

My network connection is DSL, I am not using wireless. I am connecting to the other side of the world, the institute I work for. I am away for a while but I do need to continue my work from here remotely. As far as I know, everything with the network works well.

10-15 minutes is just an approx, it might be shorter, but whether it happens after a certain amount of time every time? I can't say yes for certain.

I think your guess is correct that the problem is with the network configuration or it is a physical problem, somebody told me the same thing, but I am not a pro so I really can't imagine what might be wrong, is it the remote server, or somewhere inbetween?? And, how to fix it?

Any idea?

.

I thought to bring this up one more time, maybe someone can give me some advice.

Thanks.

.

Hi
I am trying to connect to a remote server using cygwin. But each time after entering my password, it gives this error below:
-bash: lesspipe: command not found
-bash: dircolors: command not found
-bash: uname: command not found
-bash: uname: command not found
-bash: [: !=: unary operator expected
-bash: [: too many arguments
-bash: [: too many arguments
-bash: [: =: unary operator expected
-bash: [: too many arguments
-bash: [: too many arguments
-bash: [: too many arguments
-bash: [: too many arguments
-bash: [: too many arguments
-bash: [: too many arguments
-bash: [: =: unary operator expected
-bash: [: =: unary operator expected
-bash: [: =: unary operator expected
-bash: [: =: unary operator expected
-bash: [: =: unary operator expected
-bash: [: =: unary operator expected
-bash: [: =: unary operator expected
-bash: [: =: unary operator expected
-bash: [: =: unary operator expected
-bash: [: =: unary operator expected
-bash: [: too many arguments
-bash: [: =: unary operator expected
-bash: sed: command not found


Could you please help me what can create this problem and how can i solve it?
I fairly new to linux.
Thank you

All I can recommend to you, is to see, if you can connect to the same ssh server from other computers (networks) and if you can connect to other ssh servers. That could at least make sure where's the problem.

You could also check the logs in the ssh server, there might be something there.

2 things:

1) esra, don't hijack someone else's thread start your own.

2) linux_2007_: it sounds as though the ssh server is disconnecting your client after the idle time threshold is exceeded. There are a couple different ways to resolve this. Read the following page: http://madphilosopher.ca/2005/07/an-ssh-keep-alive-tip/