Greg:

I have seen where a momentary network outage caused FTP to stop working (on
MPE 6.0).  The JINETD $stdlist kept reporting some kind of error message for
FTP over and over whenever anyone attempted to connect to the HP3000 FTP
server.  The client kept getting "FTP connection refused by host".  The one
way we fixed it was to simply ABORTJOB the JINETD job and then restream
JINETD.  It got FTP working again without stopping NS or re-booting the
system.  If, in this case, TELNET was working and now it is not, check for
errors in JINETD and/or try killing JINETD and re-stream it before resorting
to a system re-boot.

Bill Titus

-----Original Message-----
From: Stigers, Greg [And] [mailto:[log in to unmask]]
Sent: Friday, October 27, 2000 1:33 PM
To: 'Titus, Bill (Indsys,Pwr Equip,IM)'; [log in to unmask]
Subject: RE: Telnet not working


X-no-Archive:yes
or inetd -k, preferably, right, d, Mark? Or Bill, are you suggesting that
inetd is so hosed, that its job has to be aborted?

greg stigers
http://www.cgiusa.com

-----Original Message-----
From: Titus, Bill (Indsys,Pwr Equip,IM)
[mailto:[log in to unmask]]
Sent: Friday, October 27, 2000 1:06 PM
To: [log in to unmask]
Subject: Re: Telnet not working

Steve:

Check the $STDLIST of the currently running JINETD job for errors.  I have
seen some of the services like FTP get hosed up with errors appearing in the
$STDLIST.  You may be able to cure it by doing an ABORTJOB of the currently
running JINETD JOB, then simply re-stream JINETD.

Regards,

Bill Titus

>  GE Industrial Systems
> ___________________________________
> William S. Titus
> Information Management
> GE Turbine Support Operation
> 6901 Elmwood Ave., Philadelphia, PA 19142 USA
> (215) 726-2026, Dial Comm: *245-2026
> Fax: (215) 726-2044, Dial Comm: *245-2044
> Internet Address:  [log in to unmask]