View Single Post
  #4  
Old 01-18-2005, 03:49 PM
rwatson rwatson is offline
Registered User
 
Join Date: Jan 2005
Posts: 3
trace...

The only data from the trace was at the beginning of the session:

SSH: connected
SSH: RCVD: server public key
SSH: SEND: session key
SSH: setting cipher to 3DES
SSH: RCVD: success
SSH: SEND: username
SSH: RCVD: failure
SSH: SEND: Auth Password
SSH: RCVD: success
SSH: SEND: max packet size: 4096
SSH: RCVD: success
SSH: SEND: request pty
SSH: RCVD: success
SSH: SEND: exec shell

After being idle for about 12 minutes SecureCRT reported the session was terminted. This ony happens a few seconds after I attempt to enter a command. As you can see from the data below the session was still active on the server 6 minutes later. I have a ssh timeout on the server set to 30 minutes so the server should not be timing out the session.

USER TTY FROM LOGIN@ IDLE JCPU PCPU WHAT
root pts/0 xxxxxxxxxx 3:58pm 12:48 0.05s 0.05s -bash
root pts/1 xxxxxxxxxx 5:27pm 0.00s 0.03s 0.01s w

USER TTY FROM LOGIN@ IDLE JCPU PCPU WHAT
root pts/0 xxxxxxxxxx 3:58pm 18:52 0.05s 0.05s -bash
root pts/1 xxxxxxxxxx 5:27pm 0.00s 0.04s 0.02s w
Reply With Quote