ian@ukpoit.co.uk (Ian J Spare) (07/31/90)
I have observed a problem ( or quirk :-) ) with our WIN/TCP and I would like to know if others see it as well. We have WIN rel 4.0.0.2 and NCR Tower 400 and 500's under REL 3. Basically when an rlogin or telnet drops whether from line loss ( often caused by my Epsom PCe locking up ) or user request ( ie. on our annex terminal server) the remote processes on the host remain. On UNIX this means after a time a number of phantom users with entries in utmp showing up and a number of shells etc hanging around. From a sys adm point of view this is a nightmare, I can't tell if the users are logged in or where physically to look for the sessions. DO YOU SEE THIS ???? Have you any tips/insights ??? Thanks Ian ------------------------------------------------------------------------------ Ian Spare | iT | E-mail : ian@ukpoit.uucp Barker Lane | BANG-STYLE : ......!ukc!ukpoit!ian CHESTERFIELD S40 1DY | VOICE : +44 246 214274 Derbys, England | FAX : +44 246 214353 -------------------------------------------------------------------------------- iT - The Information Technology Business Of The Post Office ----------------------- In Tune With Technology -------------------------------
nigel@cnw01.storesys.coles.oz.au (Nigel Harwood) (08/03/90)
In article <1443@ukpoit.co.uk>, ian@ukpoit.co.uk (Ian J Spare) writes: > WIN TCP/IP rel 4.0.0.2 and NCR Tower 400 and 500's under REL 3. > When an rlogin or telnet drops [...] the remote processes on > the host remain. On UNIX this means after a time a > number of phantom users with entries in utmp showing up and a number of shells > etc hanging around. I have sometimes noticed this on our EXELAN TCP/IP running on NCR Tower 600 1.03 and Tower 650 2.01. -- <<<<<<<<<<<<<<<<<<<<<<<<< Nigel Harwood >>>>>>>>>>>>>>>>>>>>>>>>>>> << Post: Coles Myer Ltd, PO Box 2000 Tooronga 3146, Australia >> << Phone: +61 3 829 6090 E-mail: nigel@cnw01.storesys.coles.oz.au >> <<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>
ian@ukpoit.co.uk (Ian J Spare) (08/10/90)
In article <1035@cnw01.storesys.coles.oz.au> nigel@cnw01.storesys.coles.oz.au (Nigel Harwood) writes: >I have sometimes noticed this on our EXELAN TCP/IP running on NCR >Tower 600 1.03 and Tower 650 2.01. > OK !! Some confusion on my part , I have some new info !! While at a client site I saw the same problem with their PC's ( PCs on WIN and INET on DPX2 ) the problem must be related to the use of PC-XT's for Telnet. The silence and few e-mails I received refuting my observations CANNOT be correct, this is a general problem effecting use of XT's for TELNET. I cannot as replicate the problem using rlogin or 286 or 386 PC's. The finger of suspicion points firmly at the XT. Come on netters !!! Loads of people must be able to duplicate this !!! Somebody out there knows all about it !!! Ian Spare iT | E-mail : ian@ukpoit.uucp Barker Lane | BANG-STYLE : ......!ukc!ukpoit!ian CHESTERFIELD S40 1DY | VOICE : +44 246 214274 Derbys, England | FAX : +44 246 214353 -------------------------------------------------------------------------------- iT - The Information Technology Business Of The Post Office ----------------------- In Tune With Technology -------------------------------
fks@VAX.FTP.COM (Frances Selkirk) (08/10/90)
I thought this was the natural result of not properly ending a telnet session. It has happened with my 286. If I get bumped out of a telnet session, I always log back in and do a ps to see if there's anything that needs to be killed. Frances Kirk Selkirk info@ftp.com (617) 246-0900 FTP Software, Inc. 26 Princess Street, Wakefield, MA 01880