Veritas-bu

[Veritas-bu] Remote Administration Console not connecting

2004-03-22 16:12:46
Subject: [Veritas-bu] Remote Administration Console not connecting
From: justin.lloyd AT mci DOT com (Justin C. Lloyd)
Date: Mon, 22 Mar 2004 16:12:46 -0500
We have a winner!  Not silly at all.

Hmm, I'll have to go back to do some testing with snoop to see what I 
missed before.  Thanks!!!

Justin

Jim Horalek wrote:

> May seem silly but it is xp.
> You don't have xp's firewall turned on?
> 
> 
> 
> -----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 12:47 PM
> To: veritas-bu AT mailman.eng.auburn DOT edu
> Subject: Re: [Veritas-bu] Remote Administration Console not connecting
> 
> 
> So far, I've tried adding a SERVER entry to my bp.conf (which was needed
> anyway) but have not yet gotten it working.  I've confirmed reverse DNS
> entries for the server and Windows boxes and I'm even looking at the
> files in /usr/openv/var/auth.
> 
> Thanks for all suggestions so far.  Keep 'em coming.  ;)
> 
> Justin
> 
> Justin C. Lloyd wrote:
> 
> 
>>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

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