Worth trying this:

In the client's record change the 'save command' attribute from blank to
'save -c A'

If that fixes it then its to do with the name resolution environment on
the client itself - eg; when it looks up its own IP it gets B and then
it refers to itself as B within the nsrexec protocol. This may indicate
that host B registered one of it's private ip addresses which matches
your host's address in DNS dynamically - something windows loves doing,
no matter how stupid it sounds that servers can register all their ip's
themselves dynamically in DNS.

Maybe you cant control what the windows people do - but you can
anticipate it...  They typically use 192.168 for private nets because
that's what the example in the manual says....    Would it be possible
to avoid using 192.168 for DMZs?   172.16-31 is the place I'd use for
DMZs for precisely the reason that 192.168 has such a lot of issues with
clashes.    

> -----Original Message-----
> From: EMC NetWorker discussion 
> [mailto:NETWORKER AT LISTSERV.TEMPLE DOT EDU] On Behalf Of Goslin, Paul
> Sent: Tuesday, 4 December 2007 7:34 AM
> To: NETWORKER AT LISTSERV.TEMPLE DOT EDU
> Subject: Re: [Networker] Client Names / Weird failures... / DNS ?
> 
> But I have checked both forward and reverse name resolution from the
> server and the hosts file on the server, neither of these 
> clients appear
> in the hosts file.... 
> 
> How do I query the DNS server for the 'cname' alias ?  If I can find
> evidence that DNS is the source of the problem, I can report 
> it to those
> who can fix it because I can't.... But I need 'evidence', as 
> in a reply
> from the DNS server showing the problem... 
> 
> -----Original Message-----
> From: Fazil.Saiyed AT anixter DOT com [mailto:Fazil.Saiyed AT anixter DOT 
> com] 
> Sent: Monday, December 03, 2007 3:28 PM
> To: EMC NetWorker discussion; Goslin, Paul
> Cc: NETWORKER AT LISTSERV.TEMPLE DOT EDU
> Subject: Re: [Networker] Client Names / Weird failures... / DNS ?
> 
> 
> Hello,
> Seen this problem all the time, if an cname alias added to 
> DNS  or host
> file on your server is misconfigured you will get the error, as i
> understand it when DNS is consulted & returns a different name for the
> client, you will generally see this error. 
> Resolve the names to make sure they are accurate and you 
> should be fine.
> 
> HTH 
> 
> 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
> 

NOTICE
This e-mail and any attachments are confidential and may contain copyright 
material of Macquarie Group Limited or third parties. If you are not the 
intended recipient of this email you should not read, print, re-transmit, store 
or act in reliance on this e-mail or any attachments, and should destroy all 
copies of them. Macquarie Group Limited does not guarantee the integrity of any 
emails or any attached files. The views or opinions expressed are the author's 
own and may not reflect the views or opinions of Macquarie Group Limited.

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