I see this problem whenever another CNAME is added to a client's DNS entry 
after the client resource is added to NetWorker. An easy way to deal with that 
problem is to simply add the new alias name onto the aliases list of the 
relevant client entry. Deleting and creating the client entry solves the 
problem because it then picks up the additional CNAME alias from DNS, but it is 
overkill in my opinion.

On 10 26, 2011, at 8:04 AM, Eivind Antonsen wrote:

> Hello all
> 
> Experiencing strange behaviour on one Windows 2008 client.
> 
> NWserver/client  version 7.6.2
> 
> If the client is restarted the backups start to fail with "client is not 
> properly configured on the NetWorker Server"
> 
> We then have to delte the client in NMC and recreate it.
> The backups then run fine untill the next time the client is rebooted, when 
> the error reappears.
> 
> Notes:
> Ping works both ways
> Nslookup works both ways with short name and FQDN
> Rpcinfo -p works both ways
> Client is configured with FQDN
> 
> 
> Thanks you
> Regards
> Eivind
> 
> 
> To sign off this list, send email to listserv AT listserv.temple DOT edu and 
> type "signoff networker" in the body of the email. Please write to 
> networker-request AT listserv.temple DOT edu if you have any problems with 
> this list. You can access the archives at 
> http://listserv.temple.edu/archives/networker.html or
> via RSS at http://listserv.temple.edu/cgi-bin/wa?RSS&L=NETWORKER

To sign off this list, send email to listserv AT listserv.temple DOT edu and 
type "signoff networker" in the body of the email. Please write to 
networker-request AT listserv.temple DOT edu if you have any problems with this 
list. You can access the archives at 
http://listserv.temple.edu/archives/networker.html or
via RSS at http://listserv.temple.edu/cgi-bin/wa?RSS&L=NETWORKER