Hi all !

The company I was previously working for were using that kind of setup.
They replaced all DTCs with DTC16RX.  Those were managed from ONE HP9000
using rdtcmgr.  Then, using a "Front-End DTC" installed on same subnet as
the HP3000 was encapsulating/de-encapsulating AFCP to/from remote DTCs.  It
also required DNS service.  the front-end DTC was not dedicated and can also
be used as a "standard" dtc locally.

At the time it was setup, we used DNS service from Windows NT 4.0.  As far
as I know now, DNS is available on HP3000...

Hope it helps.
--
==================================================
Denis St-Amand (Remove "removeit." from email address)
==================================================
"Gavin Scott" <[log in to unmask]> wrote in message
news:8sfdvf016mh@enews2.newsguy.com...
> Steve asks:
> > Has anyone heard of a product called SoftDTC?
>
> I've never heard this name before, but there is a solution from HP for
> routing DTC traffic which involves encapsulating it in IP.  This requires
an
> OpenView DTC Manager workstation on both the 3000's network segment and
each
> segment that has a "remote" DTC.  It also requires an additional DTC on
the
> 3000's segment.  The encapsulation actually happens between the remote DTC
> and this extra DTC next to the 3000 rather than all the way to the 3000
> itself.  The "local" DTC by the 3000 disencapsulates the AFCP packets and
> forwards them to the 3000 which then thinks that all the DTCs are actually
> local.
>
> It's a bit of a pain to set up, and there aren't too many people doing it,
> but people say it works.
>
> These days I'd seriously look at switching to VT or Telnet plus network
> printing rather than go through all this, but if you must have terminals
or
> terminal-like devices or serial printer devices which are not compatible
> with things like JetDirect boxes then you may be stuck.
>
> G.
>