Unsolved

This post is more than 5 years old

1 Rookie

 • 

1 Message

805

December 8th, 2015 05:00

'system' is not a registered client?

Morning,

So this is coming up on about 95% of every client that I have. Currently I'm getting 750+ failures with this message. We're currently running 8.2.1.6 on Windows and RHEL environments. The biggest difference that I'm noticing is that the system entered is in caps, the system that it's saying is not a registered client is in lower case, but the actual system name is indeed in caps. Example below:

Client entry - QWERTY1234

Error name - qwerty1234

Actual name - QWERTY1234

I could manually go through and enter in each computer name with lower case but we're talking 750+ computers. Right now, nothing is backing up at all. Any help or suggestions would be greatly appreciated, thanks!

-Mick

2.4K Posts

December 8th, 2015 07:00

If this was a working environment (I suppose so), then it is most likely impossible that NW forgot about the resources for all these clients.

If the configuration database is not corrupt, then it is most likely due to a DNS problem.

See what the outcome is when you try to reach a client from the server:

   nsradmin -p nsrexec -s

I guess, it cannot find the host. Now check the DNS with nslookup.

0 events found

No Events found!

Top