Hi there,
some of my users use putty to connect to my server via ssh protocol. After some time they get the above error message, and it could be that my CentOS-side configuration caused this. Do anybody has experience with this problem?
- Gergely
I had that problem on a Ubuntu workstation a couple of weeks before the network card stopped working so I'm guessing on hardware failure..
On 3/29/08, Gergely Buday gbuday@gmail.com wrote:
Hi there,
some of my users use putty to connect to my server via ssh protocol. After some time they get the above error message, and it could be that my CentOS-side configuration caused this. Do anybody has experience with this problem?
- Gergely
CentOS mailing list CentOS@centos.org http://lists.centos.org/mailman/listinfo/centos
Gergely Buday wrote:
some of my users use putty to connect to my server via ssh protocol. After some time they get the above error message, and it could be that my CentOS-side configuration caused this. Do anybody has experience with this problem?
I have seen similar problems if ICMP is blocked.. On my LAN, putty sessions live forever.
On 29/03/2008, Morten Nilsen morten@runsafe.no wrote:
some of my users use putty to connect to my server via ssh protocol. After some time they get the above error message, and it could be that my CentOS-side configuration caused this. Do anybody has experience with this problem?
I have seen similar problems if ICMP is blocked.. On my LAN, putty sessions live forever.
They connect via the internet, could it make a difference? And, how can I check if ICMP is blocked?
Now I have made a test from Unix machines using ssh (the program), I did not experience the same problem so it might be with putty and/or with company firewall/user's ISP.
- Gergely
Gergely Buday wrote:
On 29/03/2008, Morten Nilsen morten@runsafe.no wrote:
some of my users use putty to connect to my server via ssh protocol. After some time they get the above error message, and it could be that my CentOS-side configuration caused this. Do anybody has experience with this problem?
I have seen similar problems if ICMP is blocked.. On my LAN, putty sessions live forever.
They connect via the internet, could it make a difference? And, how can I check if ICMP is blocked?
Now I have made a test from Unix machines using ssh (the program), I did not experience the same problem so it might be with putty and/or with company firewall/user's ISP.
- Gergely
CentOS mailing list CentOS@centos.org http://lists.centos.org/mailman/listinfo/centos
Yes it makes a difference, since the internet is less reliable than a local LAN. in /etc/ssh/sshd_conf enable TCP_KEEVALIVE (or something like that), and in Putty > Connection > tick Enable TCP_keetalives
This will help quite a bit, but still can't compensate for packet loss on the internet, for example your ISP, or one of the many routers (do tracepath from the one machine to the other to see how many there are) could have intermittent problems. I know ADSL isn't a guaranteed service in our country, so some days my SSH sessions will stay open for days at end (even with the quick ADSL reset), but other times it resets often
Gergely Buday wrote:
On 29/03/2008, Morten Nilsen morten@runsafe.no wrote:
I have seen similar problems if ICMP is blocked.. On my LAN, putty sessions live forever.
They connect via the internet, could it make a difference? And, how can I check if ICMP is blocked?
Ping sends ICMP packages, so try pinging the server from the clients whom experience problems.
Hi there,
some of my users use putty to connect to my server via ssh protocol. After some time they get the above error message, and it could be that my CentOS-side configuration caused this. Do anybody has experience with this problem?
- Gergely
Gergely,
Start putty.
Click on a profile you use
Then click on load
Then on the left goto "connection"
Change "seconds between keepalives" from 0 to some number like 5 or whatever
Save
In general, You should now be fine.
- rh
Gergely Buday wrote:
Hi there,
some of my users use putty to connect to my server via ssh protocol. After some time they get the above error message, and it could be that my CentOS-side configuration caused this. Do anybody has experience with this problem?
it could be a lot of things, including a NAT router's session tracking timing out on an idle session.
in their putty configuration, enable 'tcp keep-alives', this is on 'connections', also set the keepalive timer to like 30 seconds.
-
Gergely Buday -
John R Pierce -
Morten Nilsen -
Nicolas Sahlqvist -
Robert - elists -
Rudi Ahlers