Unable to connect to host - Networker 7.5 SP3 problems

Hi Osk,

     Just check if windows firewall service is disabled. Normally after deleting the nsr peer information this issue used to get resolved.

Arun

Osk,

please check :

Unable to connect to host. Please check networker security settings

ID: esg104522 Use Count: 47 Date Created: 04/08/2009 Date Modified: 07/09/2010 Product(s): NetWorker Server for Linux, NetWorker Server for Unix, NetWorker Server for Windows Category(ies): Configuration Status: Approved Related Bugs:

SOLUTION

Symptoms unable to expand the savesets under the client configuration. Error: Unable to connect to host. Please check networker security settings Cause NetWorker peer information private key on client side is either corrupted or changed Resolution Open up a client prompt, nsradmin -p nsrexec nsradmin> show auth methods nsradmin> print type: nsrla auth methods: "0.0.0.0/0,nsrauth/oldauth"; (make sure nsrauth is on) nsradmin> show nsradmin> delete type: nsr peer information :::::: -----END CERTIFICATE-----"; Delete? y nsradmin> quit restart NetWorker client services d type: nsr peer information

Hello Osk,

Please follow the steps below to fix the problem:

1   - in Backup client affected, stop the services of Networker and  change  the folder name \res\nsrla to \res\nsrla.orig (if more than  one,  do all simultaneously).

2 - in Networker Server delete the client machine (if it is in the list of clients) and run the following commands ( as an example the client name is called BEBO ):

C:\>echo del type: nsr peer information > BEBO
C:\>nsradmin -i BEBO -p nsrexec

3 - Start the services in the Networker backup client and confirm that a new folder \ res\nsrla was created.

4 - Make the process of installing the client on the Networker Server (Wizard mode) and confirm the creation of it.

If the problem persists, check dns.

Ping-a server IP (by client)
Ping-a client IP (by server)

nslookup server name (by client)
nslookup client name (by server)

Check  if both resolve the name. If  not, stop the service at the client,  change the host file - adding a  line with the name and ip of the backup  server - saving the  configuration and start the service.

Thanks,

Ahmed Bahaa

Hello osk,

Yes the host file is enough.

Please ensure that the client's host file has entries for the NetWorker server and itself and the NetWorker server has host entries for the client and itself.

Also please clear the DNS cache on both host (just incase).

Check/validate the aliases in the Client configuration and if multiple NICs, please ensure that the communication is happening both ways on the correct NIC.

Thanks.

Hi

The firewall is not an issue because i have already checked and it's disabled.

One question, is it enough to use hosts file definitions or networker

must use DNS server information for resolving names?

I will try again the method of deleting peer information

Please let me know

Greetings

Oskar

Hi

I tried the delete peer solution but i only get this:

echo del type: nsr peer information > XXX

nsradmin -i XXX -p nsrexec

no resources to delete!

I still can't add the client through the client wizard...

i have already cleared DNS cache in both server and client.

Any ideas?

Greetings

Oskar.

Hello

Update: I got it working by recreating nsrauth auth method using nsradmin -p nsrexec on the client, and restarting both

nsrexecd daemons on the client and networker server.

Greetings

Oskar.