HP3000-L Archives

July 2000, Week 3

HP3000-L@RAVEN.UTC.EDU

Options: Use Monospaced Font
Show Text Part by Default
Show All Mail Headers

Message: [<< First] [< Prev] [Next >] [Last >>]
Topic: [<< First] [< Prev] [Next >] [Last >>]
Author: [<< First] [< Prev] [Next >] [Last >>]

Print Reply
Subject:
From:
Jeff Kell <[log in to unmask]>
Reply To:
Jeff Kell <[log in to unmask]>
Date:
Thu, 20 Jul 2000 23:35:03 -0400
Content-Type:
text/plain
Parts/Attachments:
text/plain (19 lines)
Barry Lake wrote:

> >The above will not work if your users connect through a DTC using
> >the 'telnet access' card .

But you can identify them by being in your "non-nailed LDEV" pool; i.e.,
they will be coming from an LDEV number but it won't match any real
DTC.  If your DTC connections are all nailed, this is easy to identify
(as is our case); but if you use non-nailed ldevs for your real DTC
connections it is a moot point.

A long-standing gripe of mine was that the 3000 is unaware of the origin
IP address of a TAC connection, while DTC manager can query this quite
easily.  The information is there and accessible.  But since DTCs are a
dying breed, I'm sure asking for this enhancement at this point in time
would be talking to a tree :-) more so that it was in the past.

Jeff Kell <[log in to unmask]>

ATOM RSS1 RSS2