Anonymous User

updated

7 years ago

AU

Anonymous User

1 Rookie

13 Posts

1

29180

March 2nd, 2014 10:00

Problems with connect to client Networker

Hi, I install EMC Networker to Server, but one moment when I was installing client to HOST X, I cancelled installation.

And today I want install client Networker to HOST X, but I have problem!!!! It isn't very clear, because yesterday I could Connect to HOST X and yesterday this error wasn't! I re-install client Networker to HOST X, but error remained. Please help!!

Безымянный.jpg

  • Anonymous User

    1 Rookie

    13 Posts

    22651

    0

    Posted March 4th, 2014 03:00

    Thank guys!!! We did this problem!

    I did this:

    Run the following commands on both NetWorker Server and the problematic client:

    C:\>nsradmin -p nsrexec
    NetWorker administration program.
    Use the "help" command for help.
    nsradmin> . type: nsrla
    Current query set
    nsradmin> show auth methods
    nsradmin> print

    Does it show as below on both NetWorker Server and the problematic client?

    auth methods: "0.0.0.0/0,nsrauth/oldauth"; 

    If not, run:

    update auth methods:"0.0.0.0/0, nsrauth/oldauth "

    2. Update peer information:

    On the client:

    nsradmin -p nsrexec
    print type: nsr peer information; name:
    delete

    On the networker server:

    nsradmin -p nsrexec
    print type: nsr peer information; name:
    delete


    My problem disappeared!!!

  • ble1

    6 Operator

    14354 Posts

    56186 Points

    20180

    0

    Posted March 2nd, 2014 12:00

    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.

  • TimQuan

    6 Operator

    1242 Posts

    20180

    0

    Posted March 2nd, 2014 18:00

    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

  • Anonymous User

    1 Rookie

    13 Posts

    20180

    0

    Posted March 3rd, 2014 00:00

    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?

  • crazyrov

    6 Operator

    1319 Posts

    20180

    0

    Posted March 3rd, 2014 00:00

    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.

  • Anonymous User

    1 Rookie

    13 Posts

    20179

    0

    Posted March 3rd, 2014 01:00

    I try this, but my DNS server work good!

  • crazyrov

    6 Operator

    1319 Posts

    20179

    0

    Posted March 3rd, 2014 01:00

    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.

  • Anonymous User

    1 Rookie

    13 Posts

    20179

    0

    Posted March 3rd, 2014 01:00

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

  • bingo.1

    1 Rookie

    2430 Posts

    20179

    0

    Posted March 3rd, 2014 02:00

    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

  • Anonymous User

    1 Rookie

    13 Posts

    20246

    0

    Posted March 3rd, 2014 03:00

    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...