Unable to connect to host: Please check NetWorker security settings and daemon.log on the NetWorker client and Console server for more details

Hi ,

         This might be issue with nsrladb ,  follow the following steps

1)Stop NetWorker.
2)Rename the nsrladb directory to nsrladb.org.
3)Start the Backup configuration wizard again with new nsrladb directory.

NOTE:nsrladb will be recreated automatically at the start-up of NetWorker.

I already done these changes, but still not work...

Sarah,

Deleting nsr peer information may help you. Follow the below steps.

Log in to client, 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

You should be aware also that the Client Configuration Wizard will not work if nsrauth on your NetWorker server.  This is enabled by default so if you don't know what this is, then this probably isn't your issue but if you have disabled it, you will need to use the older method to create a client.  Configuration - Clients - Right Click - New (and not Client Backup Configuration).  Either way, you should test this and see if you can create a client this way.

-Bobby

I've followed  all the steps as you can see the screens below.

But  still could not add this client. Other clients  have already been added normally, I'm having problems only with that  client.

Any suggestions?

Check that the nsrexecd service is running on the client machine.  You should also check the connection between the two machines with the following command:

From the server: nsradmin –s -p 390113
From the client: nsradmin –s
From the client: nsradmin –s -p 390113

If this gets through to the nsradmin prompt, then the connection is ok, otherwise it is not.  If you do  not get the
nsradmin prompt, it means you have a connection problem and you will have to ensure that the name resolution is
correct between the two machines. Ensure that the FQDN,shortname and IP Address are present in the hosts file
on both sides and that Reverse DNS lookup works for all names and the IP.

-Bobby

There's something wrong.

Is the second xp client that i install, and returns this error message.

- XP Firewall are disable

- Anti-virus software are disable

- All the machine are in the same network, and i  get the reply when I ping by name of machine. -

I've  tried everything..but i still have the same problem.

Hi Sarah,

did you provide any backup server during installation to the wizard?

May be there is a typo?

Please check servers in the servers file on your xp client. Location: \res\servers.

If the name of your backup server is written wrong, correct it an restart the service.

May be, you will have to provide both, not only hostname but also fqn.

Peter

Hi Sarah,

In addtion to prajith said, Delete the peer information of the client from the server end as well.

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> p type : NSR peer information ; name : CLIENT_NAME

::::::

-----END CERTIFICATE-----";

nsradmin> delete
Delete? y
nsradmin> quit

restart NetWorker client  & server services once.

HTH.

Hari

What messages do you see in the daemon.raw and in the gstd.raw? Which account are you using to login to NMC?

i have also same problem i tried everything which is mentioned above still not working. any have any idea?

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 \ orignsrla (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:

C:\>echo del type: nsr peer information > delpeer.nas
C:\>nsradmin -i delpeer.nas -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)

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.

To solve my problem, I stopped the services and added in both host files (server and client) their ips.

I hope I have helped....

Thanks for all these tips.

But i solved this problem by adding in the "host" file (both server and client) their addresses ip.

From where - backup server or NMC server????