Did you add the name of the W2K3 server to
the “other” servers list on the Master?
By default Netbackup does not talk to
strangers.
So you have to put the server with the
console on the list of friends he is allowed to talk to.
This is a security feature to stop just
anybody from being able to run a console.
From:
veritas-bu-bounces AT mailman.eng.auburn DOT edu
[mailto:veritas-bu-bounces AT mailman.eng.auburn DOT edu] On Behalf Of Cornely, David
Sent: Thursday, June 11, 2009 1:03
PM
To:
veritas-bu AT mailman.eng.auburn DOT edu
Subject: [Veritas-bu] Windows
Admin Console
So
I’ve tried tracking down the process for doing this but have come up
empty in both the admin guides and Symantec knowledge base. I’ve
opened a case with Symantec but it’s a 6 hour callback so I figured maybe
someone here has this info or can refer me to a specific procedure in one of
the guides that I’ve missed.
Environment:
NBU
v6.5.3 on master server running Oracle Enterprise Linux (really just a
useless version of RHEL).
Specifically,
I’m trying to configure the remote Windows admin console on a 64- bit
W2K3 server to be used by a non-admin user with relying on Active Directory for
authorization. Oh yeah, this is behind a firewall too.
The
authorization configuration on the master server is rather cryptic and there
just isn’t a clear step-by-step process on how to do this (from the
packages I need installed on the master to the firewall ports to open to the
actual config on the master). I would have used the Java console instead
but discovered there isn’t one for 64-bit Windows until 6.5.4 is
realease.
TIA,
-Dave
