Re: rrxcap-app13:C:\ 39078:save: SYSTEM error: client `client name' is not properly configured on the NetWorker Server

Try to put the hostnames of server and client in the local hosts files, this will tell you if the problem is indeed DNS related(it will go away) or maybe related to client name or identifcation.

Also, from the server try the following:

nsradmin -p nsrexec -s rrxcap-app13.ml.wpafb.af.mil [enter]

nsradmin> p type:nsrla [enter]

(output)

nsradmin>q [enter]

What you want is what it says under "name:" this is the name the client uses to identify itself with towards the server. This must be the same as configured on the server or at least a known alias on the server.

Re: rrxcap-app13:C:\ 39078:save: SYSTEM error: client `client name' is not properly configured on the NetWorker Server

Surely it is better to troubleshoot the problem than workaround it like this... The error usually refers to an issue with name resolution - check aliases configured for this client, verify nslookups for hostname, all aliases and IP is consistent on both client and server, ensure HOSTS files do not have any incorrect entries...

Re: rrxcap-app13:C:\ 39078:save: SYSTEM error: client `client name' is not properly configured on the NetWorker Server

dman1977 wrote:

I've been getting this error now for the last two-weeks and everything I try doesn't work.

rrxcap-app13:C:\ 39078:save: SYSTEM error: client `rrxcap-app13.ml.wpafb.af.mil' is not properly configured on the NetWorker Server

It's funny because it worked fine for 11 days with no error then suddenly for no reason It fails. I checked and rechecked all the DNS and networker settings. Nothing has change.

Has anyone seen this and know the fix.

Thanks,

Doug

This is typical message when you backup client <hostname> and alias for for that client in NW resources is missing mentioned entry which is <hostname>.<domain>. (perhaps unrelated, once I had customer who had also problem like this and at first sight they had alias field set correctly to learn after closer inspection that issue started after they created copy of client and during that process NMC crashed - that created corrupted alias field which you could only see with cat -vet against actual resource located inside nsrdb - removing whole alias field, saving it, and then adding it back did the trick).