hhhmmm.  Even though we have 3 other Windows clients that were added to the 
domain at the same time and they're not having any problems?

Also, the client in question still has the same hostname as before, it's just 
been given an additional alias (host.domain.com & host.domain.domain.com)

-Matt

On Mon, 13 Oct 2003 11:36:48 -0500
"Aldrich David S" <AldrichDavidS AT JohnDeere DOT com> wrote:

> Matt,
>
> You need to follow "How to Rename a NetWorker Client (UNIX)" publication 
> (bulletin #138).
>
> Basically you need to:
> 1. Obtain the Client ID using mminfo -av -r clientid,client  | uniq | grep 
> your-client-name
> 2. Delete the client
> 3. Stop Networker daemons
> 4. Move /nsr/index/old-client-name /nsr/index/new-client-name
> 5. Start Networker daemons
> 6. Create the new-client-name using the Client ID obtained from step 1.  <== 
> Important
> 7. Add old-client-name to the alias
> 8. Stop Networker daemons again
> 9. Start Networker daemons.
>
> Dave
>
> -----Original Message-----
> From: Legato NetWorker discussion
> [mailto:NETWORKER AT LISTMAIL.TEMPLE DOT EDU]On Behalf Of Matt Hemingway
> Sent: Monday, October 13, 2003 11:14 AM
> To: NETWORKER AT LISTMAIL.TEMPLE DOT EDU
> Subject: [Networker] Windows Client Access Problem
>
>
> Hey All.
>
> We added a Windows client to an Active Directory domain.  This gives the 
> client another hostname which we put in as an alias into the Networker server 
> Client Setup page (this client was getting backed up successfully before we 
> added it to the domain).
>
> The server is a Solaris 8 box.  Ever since then, backups have been failing 
> with the following error message:
>
> * host.domain.com:All 1 retry attempted
> * host.domain.com:All Connection refused
> * host.domain.com:All aborted due to inactivity
>
> On the client, host.domain.com, I see the following error message in the 
> daemon.log file:
>
> 10/13/03 01:32:43 AM nsrexecd: Access violation - unknown host:
>
> On our other Solaris and Linux boxes, under Client Setup and in the Remote 
> Access field, we've put root AT server.domain DOT com and that seems to fix 
> the problem for those platforms when this problem as arrose.  Is this what I 
> should do to the Windows client properties?
>
> Any help would be greatly appreciated.
>
> Thanks!
>
> -Matt
>
> --
> 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.
> =*=*=*=*=*=*=*=*=*=*=*=*=*=*=*=*=*=*=*=*=*=*=*=*=*=*=*=*=*=*=*=
>
>
>

--
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.
=*=*=*=*=*=*=*=*=*=*=*=*=*=*=*=*=*=*=*=*=*=*=*=*=*=*=*=*=*=*=*=