My guess is the DTC is wherever somebody sticks it.
Although 99% are no doubt, on the inside of a firewall.
I'm not sure if this old Telnet card is protected against Ping-o'
Death. That, and sometimes the inside users are worse than outside
hackers, like some young engineer in your manufacturing Dept. running
ping from the DOS Window and walking away until the next day
because it is 5PM.
Tracy Johnson
MSI Schaevitz Sensors
-----Original Message-----
From: Dave Darnell [mailto:[log in to unmask]]
Sent: Tuesday, October 31, 2000 11:57 AM
To: [log in to unmask]
Subject: Re: jinetd
I didn't think the telnet implemented in the DTC was even the same source as
that on the OS.
Also, has been stable for a long time.
What network vulnerabilities? Isn't DTC behind the same firewall?
-Dave
> -----Original Message-----
> From: Johnson, Tracy [mailto:[log in to unmask]]
> Sent: Tuesday, October 31, 2000 9:35 AM
> To: [log in to unmask]
> Subject: Re: jinetd
>
>
> The Telnet cards although reliable, may
> not be have the latest bug fixes from HP
> that the O/S version has. Not sure HP
> is maintaining them. Network
> vulnerabilities come to mind.
>
> Tracy Johnson
> MSI Schaevitz Sensors
>
>
> -----Original Message-----
> From: Dave Darnell [mailto:[log in to unmask]]
> Sent: Tuesday, October 31, 2000 11:35 AM
> To: [log in to unmask]
> Subject: Re: jinetd
>
>
> What about putting a telnet card in your DTC? My exp. is
> that it's very
> reliable. Relieves processor of some overhead, doesn't need
> iNetD/JINETD.
>
> -dtd
>
> > -----Original Message-----
> > From: Johnson, Tracy [mailto:[log in to unmask]]
> > Sent: Tuesday, October 31, 2000 9:10 AM
> > To: [log in to unmask]
> > Subject: Re: jinetd
> >
> >
> > 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.
> >
>
|
