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 delete the client in NMC and recreate it.
The backups then run fine untill the next time the client is rebooted, when the error reappears.
Ping works both ways
Nslookup works both ways with short name and FQDN
Rpcinfo -p works both ways
Client is configured with FQDN
Is that DHCP client? Next time it happens, go to client, and run:
savefs -s <backup server name> -vnp
This will give you exactly the reason what is missing (most likely some alias or IP).
Have you checked the firewall on the client? Seems like I ran into an issue like that because someone turned on a security setting that was not supposed to be set.
Also, maybe the Networker service is not restarting on the reboot.
This error mainly is due to a missing alias or Ip as stated by Hrvoje. This could be happening if the client in question was having any other name or IP address in the past.
The easy fix is to update the alias list with the name of the client it is complaining for. The missing client ame can be found either by running a probe or backup in verbose mode and also by performing a recovery.
I recently had this issue and the problem was inability of the Networker server to reverse-lookup the client's IP address. Solved by adding the PTR record to DNS.