This post is more than 5 years old
18 Posts
0
12300
January 15th, 2013 23:00
failing to add client in the networker server 8.0
Dears,
I've installed the networker server on VM machine (with OS win 2008 64bits) and I want to do backup for an exchange server which is also installed on VM machine (OS win 2008 64 bits). I have installed on the exchange server the networker client software and the NMM2.4 (networker module for microsoft application). But the problem is that am failing to add the client (exchange server "WIN-V4K0EPASRA1.bec-ar.com" to the networker server "win-77avrrmq2o8.bec-ar.com"). I'm recieving the following error:
"unable to connect to host: please check Networker Security setting and daemon logs
on the networker client and console server for more details: Could not get session
key from win-77avrrmq2o8.bec-ar.com for GSS authentitcation with WIN-V4K0EPASRA1:
Authentication error; why= Server rejected credential".
Attached is the daemon file retieved from the client machine.
Appreciate your help
Regards
Bob


rochem1
23 Posts
0
January 16th, 2013 09:00
The daemon log contains (fairly exclusively) the following message:
Try placing the NetWorker server name win-77avrrmq2o8 .bec-ar.com
in the /nsr/res/servers (UNIX) or NetWorker_install_path\res\servers (Windows) file of
NetWorker client win-v4k0epasra1.bec-ar.com
Also verify that the NW client can reach the NW server. Ensure that the aliases for both NW client and server are populated with the short and FQDN.
bob525
18 Posts
0
January 17th, 2013 00:00
Dear Michael,
I have added the Networker server name in the Networker_install_path\res\servers file of the networker client and it is working fine
. Thanks a lot for your help.
But I have one question, do I have to do that for each client? I mean what was the issue, am not supposed to do that manually each time I want to add a client. Am I missing something in the configuration?
Best Regards
Bob
rochem1
23 Posts
0
January 17th, 2013 07:00
The addition of the server name in the NW client nsr/res/servers file provides a measure of security by restricting that client to the specified list of NW servers. This means you can restrict what NW server can backup that client.
It is not mandatory to do this for every NWclient, but it does mean that in an environment with multiple NW servers there is the possibility that client being backed up by multiple servers. For some customers this can be a security issue.
If the servers file is empty then the original issue should not have been seen. Was there NW server host entries in the servers files on the NW client, but not for the one you wanted?
chrisKerbaj
3 Posts
0
July 12th, 2015 11:00
hello,
I've done it, but the problem remains
The server can communicate with the client, and i am able to pass the client name Wizard,but after that i stuck with this error as shown below:
I tried to delete the peer information also, same error
Appreciate your help guys
crazyrov
6 Operator
•
1.3K Posts
0
July 12th, 2015 23:00
Hi Chris,
If this server is not yet been used for backups try renaming the nsrla folder after shutting down the nsrexecd on the client. Once done start the nsrexecd retry the configuration again.