Veritas-bu

[Veritas-bu] Remote Administration Console not connecting

2004-03-22 15:08:40
Subject: [Veritas-bu] Remote Administration Console not connecting
From: justin.lloyd AT mci DOT com (Justin C. Lloyd)
Date: Mon, 22 Mar 2004 15:08:40 -0500
Hmm, no....

Well, that didn't fix the problem.  Tried both short and fully-qualified 
hostname, too.  Good suggestion, though.

Justin


Greenberg, Katherine A wrote:

> Do you have a SERVER = <win XP host name> entry in the Master server's
> bp.conf file?
> 
> ~Kate
> 
> Katherine Greenberg
> Systems Engineer
> Mid-Range Storage Management
> Aetna, Inc.
> greenbergka AT aetna DOT com
> Work: 860.636.6724
> Pager: 860.366.0672
> 
> 
> 
> -----Original Message-----
> From: veritas-bu-admin AT mailman.eng.auburn DOT edu
> [mailto:veritas-bu-admin AT mailman.eng.auburn DOT edu] On Behalf Of Justin C.
> Lloyd
> Sent: Monday, March 22, 2004 2:37 PM
> To: veritas-bu AT mailman.eng.auburn DOT edu
> Subject: [Veritas-bu] Remote Administration Console not connecting
> 
> 
> Our NBU Master (4.5MP6) is running on a Solaris 9 server.  I have been
> 
> using my desktop Sun box to set the display back from the Sun server to
> 
> use the Admin Console.  That has been working fine.
> 
> Now, I have just installed the Admin Console (Server install off media,
> 
> just the Admin console) on my Windows XP box.  However, I cannot get it
> 
> to successfully connect to the Master (I do see the communication via
> 
> snoop).  In the Master Server Properties under Authentication, I've
> 
> opened it up to user *, domain/group *, host *, local/network network
> 
> and User must be an OS admin (which my account is).  The message I get
> 
> on the Windows box is this:
> 
> Neither the selected host "sts-dev" has NetBackup operating nor the
> 
> current user "Justin Lloyd" or host have NetBackup administrative
> 
> privileges on the host "sts-dev".
> 1. Make sure the user has privileges on the host.
> 2. Make sure the current host is listed in the destination host's server
> 
> list.
> 3. Make sure there is a valid network connection.
> 4. Check authentication.
> 5. Make sure all the services are running on the host.
> 
> I know 3 and 5 are ok.  2 and 4 are why I set the authentication entry
> 
> the way I described above.  At first, I specified "Justin Lloyd" as the
> 
> user, but it didn't like that username, and the Windows box is not on
> 
> any Windows domain.  I did try its DNS domain there, with the
> 
> unqualified hostname, but no luck.
> 
> Any suggestions?
> 
> Justin
> 
> --
> 
> Justin C. Lloyd
> Unix System Administrator
> MCI System Technology Solutions
> Office 703.886.3219 Vnet 806.3219
> 
> 
> _______________________________________________
> Veritas-bu maillist  -  Veritas-bu AT mailman.eng.auburn DOT edu
> http://mailman.eng.auburn.edu/mailman/listinfo/veritas-bu
> 
> 
> 
> This e-mail may contain confidential or privileged information.  If you
> think you have received this e-mail in error, please advise the sender by
> reply e-mail and then delete this e-mail immediately.  Thank you.  Aetna
> 

-- 
Justin C. Lloyd
Unix System Administrator
MCI System Technology Solutions
Office 703.886.3219 Vnet 806.3219