SSH /Conection reset by peer [Solved]?

And so the problem is in the network computer that is pinged, but ssh is responsible through time, periodically issuing, then connection refused, then (after entering password)

Permission denied<br>
Read from socket failed: Connection reset by peer



then respond in the same connection refused for any inquiries. Restarting network service fixes the situation. But after attempting I / o throws with the message Write failed: broken pipe. And again, connection refused.


I come under root, so write failed is very alarming.


System CentOS 6.2 minimal, server Dell PowerEdge R310.


Thanks in advance for any info.

UPD. The Solution

The solution was as always the most logical: went to DELL ovsky system settings, poyavlyaeshsya at boot, right after BIOS and reset all settings to the ip. All regularly worked. Apparently, the DELL controller a tries to participate in the process, resulting in a session of the flies.


Thank you all!
October 8th 19 at 00:56
3 answers
October 8th 19 at 00:58
You have to look at who is running sshd. And test right on your root directory. Root access is better in *nix don't work, high set up something.
sshd is running under root. Right to the root 0555/root:root. The only "out of the box", so I suspect that the case in some configs. Looks like iptables resets the connection after a connection. Can this be? - forrest.Volkman commented on October 8th 19 at 01:01
a 555 is also from the box set? it is only read and execute, although I'm not sure that it should not be, it is not possible to check now - Leonie.Lowe29 commented on October 8th 19 at 01:04
actually, I remember that sshd is to be when an incorrect password, if I'm not mistaken - Leonie.Lowe29 commented on October 8th 19 at 01:07
Password 1000 times introduced "on paper", so that invalid passwords are eliminated. Especially because sometimes he has to use. - forrest.Volkman commented on October 8th 19 at 01:10
October 8th 19 at 01:00
Write failed — most likely, someone in the network with the same ip was blinking.
In General you're right! It is the very Dell ovsky firmware "blinked"... - forrest.Volkman commented on October 8th 19 at 01:03
October 8th 19 at 01:02
Network all's well that ifconfig | grep errors says?
Says
RX packets: 42 errors:0 dropped:0 overruns:0 frame:0<br> TX packets: 30 errors:0 dropped:0 overruns:0 carrier:0<br> RX packets: 0 errors:0 dropped:0 overruns:0 frame:0<br> TX packets: 0 errors:0 dropped:0 overruns:0 carrier:0<br> - forrest.Volkman commented on October 8th 19 at 01:05

Find more questions by tags System administrationCentOS* nix-like systemsLinux