Tek-Tips is the largest IT community on the Internet today!

Members share and learn making Tek-Tips Forums the best source of peer-reviewed technical information on the Internet!

  • Congratulations strongm on being selected by the Tek-Tips community for having the most helpful posts in the forums last week. Way to Go!

Windows 20003 client does not connect "Contacting Client"

Status
Not open for further replies.

mr7clean

IS-IT--Management
Sep 12, 2003
5
US
Have found a problem with Widnows 2003 clients. They back up fine for a while then stop backing up and the groups that they are in never finish. When I check the details of the groups they say under Command "Contacting Client". Clients are pingable, In DNS correctly (Can do reverse lookup), networker services are started. I have found that a reboot fixes this problem 9 out of 10 times. I would like to know why it is happening and if there is a patch or fix.

Regards,
Mr7Clean
 
What versions are you running on client and networker server? Is it only on Windows 2003 clients and no other OS?
 
Running Netoworker 7.3.2 and have not noticed a problems with my Win2k clients, but only have a couple of 2k servers.
 
This problem should have been resolved in 7.3.2_jumbo_build11. Try downloading that from powerlink and see if that solves your problem.

Good luck!
 
We are running nw_7_3_2_jumbo.Build.386 (which was the update 1 released a few weeks back because of staging problems from disk to tape). The "contacting client" problem happened before that patch as well when running build 11. This happens on a daily basis at our site - are you'all removing /tmp or just rebooting daily. Help!
 
Problem solved. There were some Save.exe process hung on the client. Steps used to fix problem. 1. Restart server to clear hung Save.exe processes. 2. Stop Networker services and rename the \legato\nsr\TMP directory. 3. Start Networker services. 4 From backup server run command "nsrck -L6 clientname" to check client resource. 5. Test manual "User" backup from client.
 
this happens on a daily basis. I don't think I should have to reboot my master server, stop the services, remove /tmp every single day to get backups to complete successfully. What a bad product! Also, if you remove /tmp, you don't have a restart option! So you're starting over, or moving clients that did not backup into separate rerun groups. Also, clients that did backup successfuly don't get their backup log. We also back up hundreds of clients and I don't want to run nsrck -L6 for every client in a group. There has to be a patch or something in the very NEAR FUTURE!
 
Status
Not open for further replies.

Part and Inventory Search

Sponsor

Back
Top