Browse Community
Help
Log In
Responses(4)
Solutions(0)
DavidHampson-rY
294 Posts
0
July 30th, 2012 07:00
Just to add this seems to be fairly random and a client may complete several savesets okay then throw up this message.
Panwar
79 Posts
July 30th, 2012 08:00
Hi David,
Please check the name resolution for storage node. Make sure that both forward and Reverse lookup should work for the storage node.
Also DNS entries and Hosts file should be updated properly.
Regards
July 31st, 2012 00:00
I thought you might say that! We suspect that is the case but at present that is something we have very little influence over!
pn1lDbv3G612259
105 Posts
July 31st, 2012 01:00
I got to see the same error while troubleshooting an issue for a client configured with Networker server.
I have performed the following steps which solved the issue in my case:
Made a copy of the client id
Deleted the client
Stopped the NW services
Renamed nsrladb and tmp folders
Started the NW server services
Readded the client back to NW server
Thanks
Shivakiran
Dell Support Resources
View All
Top
DavidHampson-rY
294 Posts
0
July 30th, 2012 07:00
Just to add this seems to be fairly random and a client may complete several savesets okay then throw up this message.
Panwar
79 Posts
0
July 30th, 2012 08:00
Hi David,
Please check the name resolution for storage node. Make sure that both forward and Reverse lookup should work for the storage node.
Also DNS entries and Hosts file should be updated properly.
Regards
Panwar
DavidHampson-rY
294 Posts
0
July 31st, 2012 00:00
I thought you might say that! We suspect that is the case but at present that is something we have very little influence over!
pn1lDbv3G612259
105 Posts
0
July 31st, 2012 01:00
Hi David,
I got to see the same error while troubleshooting an issue for a client configured with Networker server.
I have performed the following steps which solved the issue in my case:
Made a copy of the client id
Deleted the client
Stopped the NW services
Renamed nsrladb and tmp folders
Started the NW server services
Readded the client back to NW server
Thanks
Shivakiran