Hi
I finally solved this
The customer had a really messy DNS, they had deleted a client and given the hostname to a new client with new ip and kept the old host in the DNS, among other things.
Thanks for pointing me in the correct direction
regards
Eivind
-----Original Message-----
From: Francis Swasey [mailto:Frank.Swasey < at > uvm.edu]
Sent: 26. oktober 2011 14:10
To: EMC NetWorker discussion; Eivind Antonsen
Cc: NETWORKER < at > LISTSERV.TEMPLE.EDU
Subject: Re: [Networker] client is not properly configured on the NetWorker Server
Wow!
That sounds remarkably like a problem I have been chasing with EMC for a year now.
If it is the same problem, you will find that if you just go into NMC and remove the aliases for the client (let NMC repopulate them), the client will remarkably start working again.
Though, in my case, I have 4-6 clients that I have to do this for every time I restart the NetWorker server (and have had ever since I upgraded a year ago to 7.5.4.3) - It has persisted against all the best EMC support people who are completely baffled about what is corrupted deep down in the recesses someplace. I am currently running 7.6.2.5 on the server and the clients and it still persists for this same set of clients every time I restart the server.
Frank
Sent from a medium size mobile device
On Oct 26, 2011, at 8:04, Eivind Antonsen <ean < at > EXELLO.NO> 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.
via RSS at http://listserv.temple.edu/cgi-bin/wa?RSS&L=NETWORKER
