HP3000-L Archives

January 1997, Week 2

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:
Tue, 7 Jan 1997 19:04:18 -0500
Content-Type:
text/plain
Parts/Attachments:
text/plain (29 lines)
Steve Dirickson b894 WestWin wrote:
> Looking back over this thread I realized that we've been talking about
> two different things in answering the question...

> That's because there are two different ways to use a TAC:
> 1) Telnet to the IP address assigned to the DTC (not the TAC)
> 2) Telnet to one of the IP "alias" addresses of the supported hosts

[DTC interface versus host direct connect snipped]

Steve is correct.  If you telnet to the DTC, you get the DTC user
interface (and subsequently any hosts accessible to it).  Or in the TAC
configuration, you can "alias" an IP address to a host entry (for 3000
hosts, this is the *PROBE* name of the machine, not DNS name).

For anyone doing firewall connections or address filtering, be certain
that you filter the *DTC* address as though it had automatic access to
the most secure host accessible via the DTC interface.  This is easy to
overlook if you presume that the IP "aliases" of the various hosts are
the only way to establish a connection.

Note further that with Telnet Server/iX on 5.5, if you use the DNS name
of the host with the IP address alias, you may very well end up doing a
'telnet' session to the host, not a translated AFCP connection at all.
You must connect to the probe name to insure an AFCP translated link.
If the two names are the same, well, your mileage may vary :-)

Jeff Kell <[log in to unmask]>

ATOM RSS1 RSS2