> The reason is that DTCs are not native TCP/IP equipments. They use an HP
> proprietary protocol, AFCP, which is not routable by default. AFCP can be
> routed (i.e. AFCP frames encapsulated into TCP/IP frames), but that
> requires PC-based management, an Openview station at the remote site, and
> a
> "mirror" (well, not exactly mirror, but you've sort of got the idea) DTC
> on
> the local (i.e. system) side, to depack the TCP/IP frames and send them to
> the system in their original AFCP form.
>
        A quick note:  IIRC, the DTC72MX model is TCP/IP routable without
bridging, other models (not MX) are AFCP and would require the bridge.  I'm
no network guru so I  could easily be wrong, but it's worth checking.

        And Shareplex (Quest Software's NetBase) shadows from a Master to a
Shadow.  To update a single instance of a file on both machines locally
you'll need to add NFA (network file access, I think) to NetBase.