Problems with connect to client Networker

Do you have any error message in daemon.raw?  Something about peer information?  That could be one reason not to have this working (or nsrauth disabled).  You can try to defined it manually without wizard use and that should work just fine.

Authentication errors can occur for multiple reasons and  may be indicative of   multiple issues that need to be addressed. In order to  provide the most accurate fix, review each of the following  resolutions as one or more may apply to the environment:

1. On the client machine, ensure that nsrexecd process is available.   
2. Update the client's /nsr/res/servers (UNIX) or C:\Program Files\Legato\nsr\res\servers (Windows) file with all known aliases for the NetWorker server.   
3. Verify that name resolution between backup server and client is working correctly.  This includes all NIC's on the NetWorker client are resolvable by the backup server (Include reverse name lookup).

If the issue persists, disablethe use of GSS strong auth from NMC or using nsradmin.

nsradmin -p nsrexec

. type:NSRLA

show auth methods

print

update auth methods= "0.0.0.0/0,oldauth”

y

print

Hi friend,  today I try do all that is described above, but problem remained.

But on Host Y today I install client Networker and it worked!!!

What else can I try?

I assume you are still referring to the same Host X as Host Y !!

On Both the server and the respective client machine make a host entry for one another. i.e on the Client machine make a hosts entry for the server IP/hostname and on the server make a hosts entry for the client machine's IP/Hostname.

I try this, but my DNS server work good!

Have you tried renaming the /nsr/res/nsrladb and /nsr/tmp on the client machine to get rid of any corrupt or unwanted entries? If not please give that a try too.

Also, does your NetWorker server have more than one IP address ? If yes, define all the IP's in the client machines Hosts file too.

Nothing! Nothing work! Host X and Host Y ping to DNS Name, but I don't connect from Server Networker to Host X....

On the NW server, run "nsradmin -p nsrexec -s ".

  - If the client does respond the connection itself is fine. However the client may still reject the request due to a wrong permission.

    In this case - on the NW client:

       - Stop the NW client daemon

       - Add/correct the NW server to ../nsr/res/servers

       - restart the NW client daemon to reread the file

  - However, if the client does not respond, it is most likely that the ports have not been opened (7937 & 7938)

You also should look here: http://solutions.emc.com/EMCSolutionView.asp?id=esg77529&usertype=C

I wrote to Host file to HOST X & Server NW, all it IP, but didn't work. I check all. I don;t understand how one HOST Y install NW client and I connect to this HOST Y from NW Server and I don't connect to HOST X...

I check connect form Server NW to client by means of nsradmin -p nsrexec -s HOST X.

And I did this:

Stop the NW client daemon

       - Add/correct the NW server to ../nsr/res/servers

       - restart the NW client daemon to reread the file

But problem remained.

Hello,

Make sure you have ports opened between NW server and Host X.

Also, look at firewall settings. I have observed such issue on Windows clients caused by firewall settings.

Regards,

Pawan

Hello all,

I don't think that disabling GSS authentication will help here, as for NW 8.x nsrauth is required in order to work with client wizard (and other features).

I think this is more related to certificates (peer information) as pointed already, so please, make sure you delete the peer information of server on client, and of client on server.

Also make sure that DNS and/or hosts file is configured correctly, and also check if on the client side there is any firewall (if Windows then OS firewall could be an issue. Also make sure UAC is disabled, at least for testing purposes).

Thank you,

Carlos

Hi,

1. Check the Client auth methods & make sure that nsrauth is enabled.

on Client run "nsradmin -p nsrexec"

nsradmin > p type : NSRLA

You should see similar as "auth methods= "0.0.0.0/0,nsrauth/oldauth”

2. Check for any nsr peer information Conflicts error for the same host on the networker server daemon log files.

EX: Conflicting Peer info for host "XXX"

3. From the Error message that the networker server has rejected the authmethods , I would first make sure that the nsrauth is set @ client side.

4. You can shutdown networker services on client & rename nsrladb on client & restart the services ,

Note : To Perform the above activity , you need to delete the existing Peer info of the client "XXX".

On Networker Server

run

nsradmin -p nsrexec

nsradmin> p type : NSR Peer information ; name : XXX (FQDN name)

nsradmin> d

nsradmin> p type : NSR Peer information ; name : XXX (Shortname)

nsradmin> d

Same activity has to be performed on SN's as well , if you are backing up the clients to a different SN other than Networker Server.

Once these steps are performed we can restart the services by renaming the nsrladb ( This will clear the peer info / authmethods / Port ranges set on the Client) - Port range has to verified if you are using restricted port range on networker datazone.

HTH

Hari Prakash.