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:
Michael I Yawn <[log in to unmask]>
Reply To:
Michael I Yawn <[log in to unmask]>
Date:
Fri, 3 Jan 1997 15:12:26 GMT
Content-Type:
text/plain
Parts/Attachments:
text/plain (36 lines)
[log in to unmask] wrote:
: Someone just asked me what the requirements are for setting up a remote DTC
: using the routable DTC protocols.  Can someone point me in the direction of
: where this stuff is documented?  Specifically what the requirements are for
: the "local" DTC (models that will work, required versions, etc.) and
: "remote" DTC (same things), and how you go about configuring it all.

: I've seearched HP's support web site, and the 5.5 LaserRom, but couldn't
: find anything obvious.

: Thanks!

: G.

It's in the 5.0 Communicator (article "DTC/TIO Enhancements in
MPE/iX 5.0".  Short version:

The DTC located on the same segment as the host ("front-end" DTC)
can be a DTC 72MX, DTC16MX, Telnet Express Box, or DTC16RX.

The Remote DTC(s) can be DTC 72MX, DTC 16MX, DTC 16RX, DTC16,
and (DTC 48 w/ date code >3110).

The IP address of the DTC's must be known to a Domain Name
Server to get everything routed correctly.  In nmmgr, ports
on the remote DTC's are configured the same as for local DTCs.

--
-----------------------------------------------------------------
Mike Yawn
Hewlett-Packard                      email       [log in to unmask]
Commercial Systems Division          Voice         (408) 447-4367
19447 Pruneridge Ave M/S 47UA        Fax           (408) 447-4441
Cupertino, CA  95014
-----------------------------------------------------------------

ATOM RSS1 RSS2