If Windows, do you have NMM installed on that client?
If NMM installed this is normal.
Do you have Windows Firewall enabled?
If enabled either disabled Firewall, configure manually the exceptions in Windows Firewall for NetWorker client or uninstall the software and reinstall it by selecting "Configure Windows Firewall".
Besides ensure name resolution is correct as Suraj pointed out.
Check the daemon.log in client and server to find out what is going on, in case none of the above applies.
Try adding a new instance for the client whose savesets u r not able to browse, also let me know what is the version of your Client and Server. Was there any recent change done in your environment that has caused this issue?
Following are the possible reason for which we get the mentioned error:
1. Either there is peer information mismatch
2. Communication failure between Client and Server.
3. Client-Server Version Mismatch.
There might be something that is not known to me yet....
Kindly delete the nsr peer information from the backup server, the client in question and the NMC server and the try to browse the file system. If you have firewall and restricted the ports, ensure that you have enough number of ports opened.
Just define it manually... the time and effort people spend on wizard problems does not stop to amaze me. You are way faster to define backup manually then using wizard (as it is really that simple... new client, save set, what group, what policy and click ok).
SurajPujari
155 Posts
1601
0
Posted June 11th, 2012 12:00
Try doing a DNS query with both client and server at both the ends, also hav a check of Host entries at client and server.