I'm trying to add a new Linux client to our Networker. I can connect both ways via nsradmin and can ping and resolve both ways. However when I try to add the client it gives me a message that it cannot get the session key from the Networker server for GSS authentication. When I check the daemon.log from the client it says that the hostname provided for the Networker server is not valid. The thing is, the name it gives is not the name of the Networker server.
Where is the Networker client getting the server name from? How do I get the client to connect properly?
On the Linux server check /etc/hosts. Make sure all of the names for the localhost in /etc/hosts are in the aliases list of the client's Global 1 of 2.
Make sure the FQDN is there too. If the client is presenting the wrong name, it means there is either a naming conflict or a dns conflict.
It might be a name resolution issue on the client end. Please try and reverse loopup for the NetWorker server on the client side, also if possible make a host file entry for the backup server and test the backups.
Check the servers file on client machine (NetWorker installation path\res\servers). If you have wrong entry in the file correct it. If you don't servers file, create one and add your NetWorker server name in it. Rerun backup see if it works.
I've added the appropriate servers to the hosts file on the client and now I can go through with adding the client to Networker. We'll see how it goes from here. Thanks for the assistance so far.
Davidtgnome
1 Rookie
•
66 Posts
8045
0
Posted August 10th, 2015 06:00
On the Linux server check /etc/hosts. Make sure all of the names for the localhost in /etc/hosts are in the aliases list of the client's Global 1 of 2.
Make sure the FQDN is there too. If the client is presenting the wrong name, it means there is either a naming conflict or a dns conflict.