Argh! I'll get this message posted yet :-( Attempt no.3:

-----

Hi Ed,

How about running the following from the backup server:

nsradmin -s <client_name> -p 390113

This should connect through to the nsrexecd process running on your Tru64
server. Go into visual mode in the nsradmin session (if it connects
correctly!) which will show you the name and platform of the client you have
connected to *including* all the IP addresses that the client is known by.
This may point you in the right direction, either by getting a surprising
result for the client itself, or finding an IP address that you weren't
expecting that maybe causing routing problems.

If you fail to connect then maybe nsrexecd needs to be restarted on the
Tru64 side?

Cheers

Mark


>  Thanks.  Sadly, both server and client know who's who, and can talk to each
> other.

--
Note: To sign off this list, send a "signoff networker" command via email
to listserv AT listmail.temple DOT edu or visit the list's Web site at
http://listmail.temple.edu/archives/networker.html where you can
also view and post messages to the list.
=*=*=*=*=*=*=*=*=*=*=*=*=*=*=*=*=*=*=*=*=*=*=*=*=*=*=*=*=*=*=*=