Yo,

Ive seen some similar erros before and it has always either been some
permission / hostname resolution problem (i.e. make sure the account the
services run under has full access (which it probably does) and that all
name resolution (both forward and reverse) works from both clients.

Secondly, it sometime, for reasons that I cannot explain needed a re-install
on the client side (this is fortunately only a 2 minute job).

I'm assuming that you are running 613 ? (Ive had some "unexplicable" errors
lately which was solved as well by going to latest level) ...

Just a thought.

Riaan

-----Original Message-----
From: Matt Hemingway [mailto:matt.hemingway AT PCNALERT DOT COM]
Sent: Tuesday, October 14, 2003 5:46 PM
To: NETWORKER AT LISTMAIL.TEMPLE DOT EDU
Subject: [Networker] Windows SYSTEM STATE Failure


Yo.

I've got a couple Windows clients whose SYSTEM STATE backups fail.  Backing
of all drives on these clients work fine, but when it comes to backing up
the SYSTEM STATE, I get the following error message:

* client.domain.com:SYSTEM STATE:\ 1 retry attempted
* client.domain.com:SYSTEM STATE:\ 10/14/03 01:40:38 nsrexec: Attempting a
kill on remote save
* client.domain.com:SYSTEM STATE:\ aborted due to inactivity

I've got another Windows client whose SYSTEM DB doesn't get backed up.  It's
the same error message as the above one (just swap STATE with DB).

Ideas?

-Matt

--
Note: To sign off this list, send a "signoff networker" command via email
to listserv AT listmail.temple DOT edu or visit the list's Web site at
http://listmail.temple.edu/archives/networker.html where you can
also view and post messages to the list.
=*=*=*=*=*=*=*=*=*=*=*=*=*=*=*=*=*=*=*=*=*=*=*=*=*=*=*=*=*=*=*=

--
Note: To sign off this list, send a "signoff networker" command via email
to listserv AT listmail.temple DOT edu or visit the list's Web site at
http://listmail.temple.edu/archives/networker.html where you can
also view and post messages to the list.
=*=*=*=*=*=*=*=*=*=*=*=*=*=*=*=*=*=*=*=*=*=*=*=*=*=*=*=*=*=*=*=