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.

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

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

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.

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

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

Stop:

net stop nsrexecd

net stop gstd

Start:

net start nsrexecd

net start gstd

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

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.

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

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.

Hi Bingo,

Same result. Here are the procedures made.

Deleting peer information on client side

Stop services  > net stop nsrexecd and deleting nsr/res/nsrladb directory path.

1. Type the command:
     nsradmin -p nsrexec
     print type:nsr peer information
     delete

          y

Start services > net start nsrexecd > new nsrladb was created.

Deleting peer information on server side

Stop Services > net stop nsrd and deleting nsr/res/nsrladb directory path.

Type the command: 

     nsradmin -p nsrexec

     print type:nsr peer information; name:client_name

     delete

     y

Start services >net start nsrd but no nsrladb folder was created after re-starting the services.

try to add client on the networker server but no avail. Same error.

Copy back up folder of nsrladb on the same path but same issue occur.

Check auth method and same auth methods is in place.

Wondering that other client had been successfully connected on the networker except on this  server that generates the error mentioned above.

Hi Tim,

How to disable GSS? Is it applicable in Win2k8.?

Not pretty sure what happen here. I try to uninstall then rename and rejoin server to our domain. Successfully rejoin and re-installed networker client. Checking on the peer information and auth methods and it successfully in.

Thanks all for the comments here. :-)

Hi,

For your info, the article I referred to that you were looking for is here:

http://support.emc.com/kb/151529

-Bobby

disable GSS on the client:

nsradmin -p nsrexec
update auth methods:"0.0.0.0/0,oldauth"