Only thing I can think of is that his host name is not resolving properly on
the master's side.

check the bpcd on his system and the bprd on the master, plus the bp.conf on
he master to check to make sure the host names match.

if they don't update the bp.conf on the master restart the NBU daemons and
see what happens.

Bob
----- Original Message -----
From: <benr AT cuddletech DOT com>
To: <Veritas-bu AT mailman.eng.auburn DOT edu>
Sent: Tuesday, October 16, 2001 1:20 PM
Subject: [Veritas-bu] NB Windows Admin GUI problems


> Here's the scoop.  My manager likes playing with the Netbackup windows
admin
> GUI (you know where you aren't a client, but you want to have control over
> several diffrent NB servers).
> He can connect to several of our 3.2GA servers and everything is fine, but
> when he connects to a 3.4 server he gets odd errors.  Whats really odd is
> that he can look at the activity monitor, he can get to the media manager.
> But if he pulls up the Policy Manager or the Device Manager he gets either
> an "Invalid Server" or "Unable to connect" error.  Both of which are
hogwash
> because the server is up (and often in use) with no problems, and he can
> definalately connect to it since he can view the jobs.
>
> Veritas support is NO help at all.  Any thoughs would help.
>
> Thanx
>
> benr AT cuddletech DOT com
>
>
> _______________________________________________
> Veritas-bu maillist  -  Veritas-bu AT mailman.eng.auburn DOT edu
> http://mailman.eng.auburn.edu/mailman/listinfo/veritas-bu
>