Connection reset by peer: why?

stupendus · 01-07-2007, 08:19 AM

Hi all,
my ssh-connection got closed after some minutes with this message:

Read from remote host <name>: Connection reset by peer
Connection to <name> closed.

Directed by results of a google search I've added this line:

ClientAliveInterval 300

to this config file:

/etc/ssh/sshd_config

and then I reloaded service:

/sbin/service sshd reload

but there was no improvment.

Do you have any idea what's the problem? I'm using wireless connection.

Do you know how to solve this problem?

Many thanks in advance for any suggestion!

Marco

stress_junkie · 01-07-2007, 08:37 AM

This could be caused by several types of things. Since you are using a wireless network my first idea is that your wireless network signal quality is poor and the remote computer cannot maintain a link. My next idea is that there is a process monitor on the remote machine that kills idle processes. Does this happen when you are actively interacting with the remote computer or when you have not been busy on the remote computer? My last idea is that someone on the remote computer is killing your login process. Are you connecting to a business server where a system administrator might be watching the system? Maybe the system administrator doesn't want you to connect to that machine. (Admittedly that seems unlikely since you must have an account on that machine and you have already configured that account to use ssh.)

Of these three ideas I think that only the first two are realistic.

stupendus · 01-07-2007, 08:44 AM

Quote:

Originally Posted by stress_junkie

This could be caused by several types of things. Since you are using a wireless network my first idea is that your wireless network signal quality is poor and the remote computer cannot maintain a link. My next idea is that there is a process monitor on the remote machine that kills idle processes. Does this happen when you are actively interacting with the remote computer or when you have not been busy on the remote computer? My last idea is that someone on the remote computer is killing your login process. Are you connecting to a business server where a system administrator might be watching the system? Maybe the system administrator doesn't want you to connect to that machine. (Admittedly that seems unlikely since you must have an account on that machine and you have already configured that account to use ssh.)

Of these three ideas I think that only the first two are realistic.

Hi,
I'm at home using my private wireless connection. Strenght is excellent since wireless router is in the room where I'm working; I'm using a DSL.

It happens both when I'm actively working and in terminals in which pine is runnig, for example.

Marco

stress_junkie · 01-07-2007, 11:52 AM

Are you connecting to a server that is managed by some else? If so it is possible that the system administrator has a batch job/daemon that closes login processes during certain times of the day/week or for for certain people. If this is happening when you are connecting to a server that is managed by someone else then you should talk to them about it. They may already know the answer.

stupendus · 01-08-2007, 03:42 AM

Quote:

Originally Posted by stress_junkie

Are you connecting to a server that is managed by some else? If so it is possible that the system administrator has a batch job/daemon that closes login processes during certain times of the day/week or for for certain people. If this is happening when you are connecting to a server that is managed by someone else then you should talk to them about it. They may already know the answer.

Hi again (and many thanks for taking care of this!),
the servers are owned by a commercial company. I could ask them then.

Many thanks,
Marco

stupendus · 08-07-2007, 01:50 AM

Hi all,
just to say that I found the solution to the problem; I've added this line:

ServerAliveInterval 5

in:

/etc/ssh/ssh_config

The company providing me internet access told me that the problem was due to the limited number of 'real' ipnumbers they have so from time to time I was losing my ipnumber and then getting a new one. They suggested to use public ip number, but it is expensive.
I found that that extra line fixes the problem...

Ciao,
Marco