Re: SSH problem. (fwd)
From: Ho Chaw Ming (chawming_at_pacific.net.sg)
Date: 01/30/04
- Previous message: Mike Hoskins: "Re: SSH problem. (fwd)"
- In reply to: Mike Hoskins: "Re: SSH problem. (fwd)"
- Messages sorted by: [ date ] [ thread ] [ subject ] [ author ] [ attachment ]
To: <secureshell@securityfocus.com> Date: Fri, 30 Jan 2004 13:59:02 +0800
I face this as well. One way to prevent this really is to keep something
running: what I do is to have top running. As there's updates and continuous
activity, the connection will not be dropped.
regards
----- Original Message -----
From: "Mike Hoskins" <mike@adept.org>
To: <secureshell@securityfocus.com>
Sent: Friday, January 30, 2004 10:14 AM
Subject: Re: SSH problem. (fwd)
Maxwell Bottiger wrote:
> This is a message I'm forwarding along from a friend. Any ideas?
> ---------- Forwarded message ----------
> Date: Tue, 27 Jan 2004 09:07:18 -0500
> Subject: SSH problem.
> I'm connecting from home to work using ssh. Nothing fancy. But if I
> leave the connection open for more than 10 minutes without typing in
> it, I get:
> Read from remote host glowlight.stsci.edu: Connection reset by peer
> Connection to glowlight.stsci.edu closed.
this could be a number of things...
proxies/firewalls in the IP path setting TTL, dropping idle connections,
etc. to ensure no one person is "hogging" resources -- this is
particularly important at univsersities for obvious reasons.
software like idled on the remote server could do similar things, but
the fact that you receive an RST (I assume, from the "reset by peer"
message -- what's a sniffer show?) seems to imply it is almost certainly
a proxy or firewall imposing "policy". has your friend asked the
admin(s) of glowlight? :)
- Previous message: Mike Hoskins: "Re: SSH problem. (fwd)"
- In reply to: Mike Hoskins: "Re: SSH problem. (fwd)"
- Messages sorted by: [ date ] [ thread ] [ subject ] [ author ] [ attachment ]
Relevant Pages
|
