Unsolved
This post is more than 5 years old
110 Posts
0
12091
client is not properly configured on the NetWorker Server
Hello
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.
Notes:
Ping works both ways
Nslookup works both ways with short name and FQDN
Rpcinfo -p works both ways
Client is configured with FQDN
Thank you
Regards
Eivind Antonsen
ble1
2 Intern
2 Intern
•
14.3K Posts
0
October 26th, 2011 12:00
Is that DHCP client? Next time it happens, go to client, and run:
savefs -s -vnp
This will give you exactly the reason what is missing (most likely some alias or IP).
lalexis
253 Posts
0
November 1st, 2011 05:00
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.
singhmridul
17 Posts
0
November 2nd, 2011 13:00
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.
jamesmcd
2 Posts
0
May 3rd, 2017 00:00
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.