Hello admin folks -
I had a problem with users and telnet this morning. Some users had their
telnet sessions timeout, others could connect. The desktops are NT
workstations using exceed, the server is an Alpha 4100 running 4.0G. The
workstations are on one network, (172.16.1.x) the Alpha on another
(172.16.2.x). The route was there from one net to other (netstat -rn proved
that). I tried rcinet restart, that didn't help. Rebooting the NT machines
didn't do it either. A reboot of the 4100 fixed the problem for now. I found
the following in the daemon.log file:
Jan 17 09:05:21 dragon telnetd[10993]: ttloop: read: Connection reset by
peer
Jan 17 09:09:47 dragon telnetd[12629]: ttloop: read: Connection reset by
peer
Jan 17 09:09:48 dragon telnetd[11235]: ttloop: read: Connection reset by
peer
Jan 17 09:09:49 dragon telnetd[12882]: ttloop: read: Connection reset by
peer
Jan 17 09:09:59 dragon telnetd[13271]: ttloop: read: Connection reset by
peer
Jan 17 09:10:00 dragon telnetd[13042]: ttloop: read: Connection reset by
peer
Jan 17 09:10:01 dragon telnetd[12169]: ttloop: read: Connection reset by
peer
Jan 17 09:12:49 dragon telnetd[10813]: ttloop: read: Connection reset by
peer
Jan 17 09:12:50 dragon telnetd[32524]: ttloop: read: Connection reset by
peer
Jan 17 09:12:50 dragon telnetd[30863]: ttloop: peer died: Not owner
Jan 17 09:12:51 dragon telnetd[6756]: ttloop: read: Connection reset by
peer
Jan 17 09:12:52 dragon telnetd[4941]: ttloop: read: Connection reset by
peer
Jan 17 09:12:52 dragon telnetd[27268]: ttloop: read: Connection reset by
peer
Jan 17 09:14:01 dragon telnetd[13052]: ttloop: peer died: Not owner
Jan 17 09:14:27 dragon telnetd[12466]: ttloop: read: Connection reset by
peer
Jan 17 09:15:06 dragon telnetd[12290]: ttloop: read: Connection reset by
peer
Jan 17 09:15:08 dragon telnetd[11650]: ttloop: read: Connection reset by
peer
And the following in the user.log
Jan 16 14:51:00 dragon syslog: libtt[27584]: _Tt_rpc_client::init():
fcntl(F_SET
FD): m
Jan 16 14:51:00 dragon syslog: libtt[27584]: ttdt_Xt_input_handler():
tttk_messa
ge_receive(): TT_ERR_NOMP^INo ttsession process is running, probably because
tt_
open() has not been called yet. If this code is returned from tt_open() it
means
ttsession could not be started, which generally means ToolTalk is not
installed
on this system.
Jan 16 18:24:58 dragon syslog: libtt[31861]: ttdt_Xt_input_handler():
tttk_messa
ge_receive(): TT_ERR_NOMP^INo ttsession process is running, probably because
tt_
open() has not been called yet. If this code is returned from tt_open() it
means
ttsession could not be started, which generally means ToolTalk is not
installed
on this system.
I have no idea what the ToolTalk stuff is... maybe they aren't related...
any help would be greatly appreciated.
Damon Goforth
Received on Thu Jan 17 2002 - 18:01:14 NZDT