Does it die after a certain period of inactivity? Have them leave a
shell open, running something like:
watch -n 3 w
and see if it still happens...if it does not disconnect, I think I can
dig up a solid lead for you :)
regards,
Ben
Jim Beard wrote the following on 2/3/2005 12:37 PM:
So he
Steve <[EMAIL PROTECTED]> wrote:
> PuTTY keeps known_host keys in the registry in Winblows. Nuke that
> regkey and force PuTTY to re-read and store a new host key for your
> server.
Running 'putty -cleanup' in a DOS window will clear out the registry
stuff.
(from the Putty.hlp file)
On Windows,
On Thu, 2005-02-03 at 12:37 -0800, Jim Beard wrote:
> So he just got disconnected again. The error messages that get
> displayed are as follows:
>
> debug1: channel 0: free: client-session, nchannels 1
> debug3: channel 0: status: The following connections are open:
>#0 client-session (t4 r0
I was just having a strange issue with ssh -X, for some reason, gkrellm was
puking on me, so I googled, and found ssh -Y, which seems to be working.
Jamie
On Thursday 03 February 2005 12:37 pm, Jim Beard wrote:
: So he just got disconnected again. The error messages that get
: displayed are as
Jim Beard wrote:
> Neat. The -vvv option seems like it might help shed some light on the
> situation, at least as long as he uses a client that allows it. He is
> working from a windows workstation.
>
> There is no NAT between the server and client. It's a rather small
> LAN, I think there
I think putty has verbose logging, and allows you to set the keepalive
send interval
I've hear do of various interactions between windows networking and
persistent connections
On Thu, 3 Feb 2005 11:46:18 -0800, Jim Beard <[EMAIL PROTECTED]> wrote:
> Neat. The -vvv option seems like it might help
So he just got disconnected again. The error messages that get
displayed are as follows:
debug1: channel 0: free: client-session, nchannels 1
debug3: channel 0: status: The following connections are open:
#0 client-session (t4 r0 i0/0 o0/0 fd 4/5)
debug3: channel 0: close_fds r 4 w 5 e 6
Read
Neat. The -vvv option seems like it might help shed some light on the
situation, at least as long as he uses a client that allows it. He is
working from a windows workstation.
There is no NAT between the server and client. It's a rather small
LAN, I think there is a hub and two switches betw
You can connect using
ssh -vvv [EMAIL PROTECTED]
and see all the debug messages ssh will give you
If there is a NAT box between the two machines you will occasionally
see connections terminating on idle, the solution for that is to make
sure that both the client and the server are issuing keepal
One person in our office is experiencing some mysterious SSH connection
problems. When they connect to a specific server their connection dies
frequently. No one else on the LAN has experienced this. Network
cables have been tested and changed, and there doesn't seem to be a
problem. Other
10 matches
Mail list logo
