If you do have unavailable ports (ususally they are owned by SYS #1) then do an
abortio on each port.  Sometimes that will clear them.

"Johnson, Tracy" wrote:

> Do a SHOWDEV on all your devices.
>
> If some of your Network LDEVs show as UNAVAIL SYS,
> and won't budge.  That may be an indicator of
> something bad (System Table going corrupt?)
> and it may get progressive.
>
> We've had our latest Telnet patch in for about 3
> weeks and haven't seen this problem again.  It hit
> is for about 4 months in a row ... monthly.
>
> User's that network back in and unluckily hit those
> LDEVs again probably WON'T get a colon prompt.
>
> Tracy Johnson
> MSI Schaevitz Sensors
>
> -----Original Message-----
> From: Simonsen, Larry [mailto:[log in to unmask]]
> Sent: Tuesday, October 31, 2000 10:36 AM
> To: [log in to unmask]
> Subject: jinetd
>
> We have several users which connect to the system via telnet.  Both
> yesterday and today about the same time.  The network froze.  I looked at
> the console and there were 2 messages from the jinetd job.  The messages
> were
> Could not initialize data path with TCP.
> I aborted the jinetd job and everything is back functioning but no new
> telnet connections can be made.  (I'm sure that they will be when I start
> the job.
> I looked in the installing and managing arpa services manual and there is no
> mention of this error.
>
> Does anyone have any ideas of what the cause of this might be?
>
> -------------------------------------------------
> Larry Simonsen                Phone: 801-489-2450
> Flowserve Corporation     Fax: 801-491-1750
> PO Box 2200                    http://www.Flowserve.com
> Springville, UT 84663      e-mail: [log in to unmask]
> -------------------------------------------------
> All opinions expressed herein are my own and reflect, in no way, those of my
> employer.

--
Larry Barnes
Director of I.T.
Mitek Corp.
602-438-4545 x1366
Phoenix, AZ 85040

Check Us Out !
http://www.mitekcorp.com