UNSOLVED

raffy2

updated

13 years ago

R

raffy2

1 Rookie

14 Posts

2

78512

July 11th, 2013 20:00

Athentication error; why = Server rejected credential

Hi,

Currently having some issue in adding clients in Networker backup solution.

Unable to connect to server. Unable to authenticate with server "server name": Authentication error; why = Server rejected credential.

Note: Client Networker agent has been re-install to isolate the issue but no luck. Same error occurred .

  • TimQuan

    6 Operator

    1242 Posts

    25765

    4

    Posted July 11th, 2013 21:00

    First verify the Hosts file. Add networker server entry to the Hosts file of the client and add the client entry to the Hosts of the networker server. (both short name and long name need to be added)

    If issue still exists, delete 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

    if issues still persists, disable GSS strong auth:

    On the client:

    update auth methods:"0.0.0.0/0,oldauth"

    if still now work, add networker server name to the nsr/res/servers  file in the client. If the servers file does
    not exist under nsr/res, create it.

  • bingo.1

    1 Rookie

    2430 Posts

    25764

    0

    Posted July 11th, 2013 21:00

    If the server rejected the credentials, it is obvious that it could answer. So name resolution and servers file should be fine.

    I would recommend to

      - shutdown the NW listener on the client

      - delete the nsr/res/nsrladb directory path

      - restart the NW listener on the client

  • TimQuan

    6 Operator

    1242 Posts

    25765

    0

    Posted July 11th, 2013 22:00

    I agree with you, bingo. DNS resolution should be OK. Deleting peer information and disabling GSS strong auth worth trying.

  • raffy2

    1 Rookie

    14 Posts

    25765

    0

    Posted July 11th, 2013 23:00

    After deleting nsr/res/nsrladb another error occured.

    unable to connect to server: Failed to contact using UDP ping.

    Note: Host file for servers and client has been configure adding on both end.

  • raffy2

    1 Rookie

    14 Posts

    25765

    0

    Posted July 11th, 2013 23:00

    Sorry forgot with the shutdown the NW listener on the client.

    Is it in the services? where will i shutdown or stop the NW listener

  • TimQuan

    6 Operator

    1242 Posts

    25765

    0

    Posted July 12th, 2013 00:00

    networker services. Yes, they are in Services in Windows.

    Stop:

    net stop nsrexecd

    net stop gstd

    Start:

    net start nsrexecd

    net start gstd

  • RFreund1

    47 Posts

    25765

    0

    Posted July 12th, 2013 00:00

    If on Windows, yes, it is a service which you also can restart via the command line:

      net stop nsrexecd

      net start nsrexecd

    On UNIX/Linux you should run

      /etc/init.d/networker stop

      /etc/init.d/networker start

  • raffy2

    1 Rookie

    14 Posts

    18878

    0

    Posted July 13th, 2013 16:00

    Hi all,

    Same error..

    Athentication error; why = Server rejected credential

    After doing below procedures.

      - delete the nsr/res/nsrladb directory path

      - restart the NW listener on the client

              * net stop nsrexecd

              *net start nsrexecd

    Note: Host file for servers and client has been configure adding on both end.

             Clients Firewall has been for trouble shooting but no avail.

    Anyone can help me on this. It's been a week trying to connect the client on the Networker Server. Googling and no luck to found a solution for this. Appreciate all your comments here.

  • raffy2

    1 Rookie

    14 Posts

    13431

    0

    Posted July 13th, 2013 21:00

    Any one who knows Bobby Cogan. Seems he resolve same issue but the link he provided is no longer available.

    here's the link comments and conversation I've found

    https://community.emc.com/thread/164834?start=0&tstart=0

    here's the link from Bobby Cogan but no longer available.

    http://solutions.emc.com/EMCSolutionView.asp?id=esg77529&usertype=C

  • bingo.1

    1 Rookie

    2430 Posts

    5685

    0

    Posted July 14th, 2013 03:00

    I am pretty sure that the second link just also refers to the first one. In general points it points you to do these 2 things:

      - use the same authentication methods on client and server

      - Delete the nsr peer information on client and server.

    However, by deleting nsrladb, you just did that on the client. For the deletion on the server please use the method stated in the second post.

    Also do not forget that you should consider the Health Check Tool (HCT) to check the necessary prerequisites.