Larry, et. al.,

This may be unrelated because I don't get a console message, but ...

I have had several instances when telnet and TCP/IP just "go away".  You
can't telnet in and printing to a network printer with ESPUL stops working.
 The usual event which preceeds this is that our router gets "hosed" and we
have to restart the router.  It also happens when we restart the router for
configuration changes.

I solve the problem by stopping ESPUL, killing jinetd, and stopping the
network, the restarting everything in the reverse order.

HTH.

Bruce.
----------------------------------------------------------------------
  Bruce J. Senn                               Phone:  (518) 388-6664
  Senior System Manager                       FAX:    (518) 388-6458
  Union College                              Email:  [log in to unmask]
  Schenectady, NY 12308           WWW:  http://www1.union.edu/~sennb
----------------------------------------------------------------------
At 08:36 AM 10/31/2000 -0700, Simonsen, Larry wrote:
>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.
>
>