Skip to main content
  • Place orders quickly and easily
  • View orders and track your shipping status
  • Enjoy members-only rewards and discounts
  • Create and access a list of your products
  • Manage your Dell EMC sites, products, and product-level contacts using Company Administration.

Dell NetWorker 19.9 Administration Guide

Unable to connect to host: Please check Security setting and daemon logs on the NetWorker client and Console server for more information

This message can appear when you perform Client Configuration wizard tasks, Device Configuration wizard tasks, or when you browse save sets simultaneously while you add or modify a Client resource.

Check for one of the following scenarios when you receive this error.

  • Verify that the SSL key matches between the NMC Server and the NetWorker client host. The SSL key is in the NSR Peer Information attribute, which is located in each host’s nsrladb database. A mismatch can occur when the nsrladb on one host is corrupted.

    To resolve this issue, delete the Console Server’s NSR Peer Information from the NetWorker Client’s nsrladb, and delete the NetWorker Client’s NSR Peer Information from the Console Server’s nsrladb as following:

    • To delete the Console Server’s NSR Peer Information from the NetWorker Client’s nsrladb, on the client host, type:

      nsradmin –p nsrexec
      nsradmin> print type:NSR peer information

      NOTE:Identify the Console Server’s NSR Peer Information, and delete it.

      nsradmin> delete type: NSR peer information;name:<Console Server name>
      Delete? Yes

    • To delete the NetWorker Client’s NSR Peer Information from the Console Server’s nsrladb, on the Console Server host, type:

      nsradmin –p nsrexec
      nsradmin> print type:NSR peer information

      NOTE:Identify the NetWorker Client’s NSR Peer Information, and delete it.

      nsradmin> delete type: NSR peer information;name:<Client name>
      Delete? Yes

      After the deletion is complete, it is not mandatory to restart the NetWorker or Console services.

  • The Client cannot resolve hostname of NMC Server or NetWorker Server. Sometimes, NMC can resolve the client hostname, but, client cannot resolve the NMC or NetWorker Server hostname.

    To resolve this issue, ping the NetWorker Server and NMC server from the Client. If the ping fails, DNS is not resolving the hostname issue and add the hostname to the client hosts file.

  • Ensure NetWorker users have at least the “Operate NetWorker” privilege to launch the Client Wizard. To resolve this issue, add the user to the user_group in the NetWorker Server.
  • The NetWorker Server may not be present in the client's servers file. To resolve this issue, add the NetWorker Server to the client's servers file.
  • The NMC Server, NetWorker Server, and NetWorker client hosts must only use nsrauth authentication.

Rate this content

Accurate
Useful
Easy to understand
Was this article helpful?
0/3000 characters
  Please provide ratings (1-5 stars).
  Please provide ratings (1-5 stars).
  Please provide ratings (1-5 stars).
  Please select whether the article was helpful or not.
  Comments cannot contain these special characters: <>()\