Running NW 7.2.2 on Win2003 Server, client is also Windows Server (7.2
client version also).

 We've backed this client up before (but only once a week). Yesterday,
it failed as though it was not up, but it was. The machine resolves to
two different IP addresses due to its dual port NIC, which I think has
teaming configured... Could this be the problem ??

 See errors from probe done a few minutes ago below.

I hate that Networker is so dependent on DNS, another thing that must be
put back in place following a disaster before you can begin restoring
data... Data recovery systems should not depend on anything external,
period ! It's poor design IMHO.


07/07/08 14:08:35 savegrp: command 'savefs -s buserver.domain.com -c
clientx -g Groupx -p -l full -R -v ' for client clientx exited with
return code 1.
07/07/08 14:08:35 savegrp: clientx:probe succeeded.
* clientx:All rcmd clientx, user root: `savefs -s buserver.domain.com -c
clientx -g Groupx -p -l full -R -v'
* clientx:All 07/07/08 14:07:58 nsrexec: nsrexecd on clientx is
unavailable.  Using rsh instead.
  clientx: Connection refused
* clientx:All 07/07/08 14:08:35 nsrexec: SYSTEM error: Connection
refused

Regards,

Paul 

To sign off this list, send email to listserv AT listserv.temple DOT edu and 
type "signoff networker" in the body of the email. Please write to 
networker-request AT listserv.temple DOT edu if you have any problems with this 
list. You can access the archives at 
http://listserv.temple.edu/archives/networker.html or
via RSS at http://listserv.temple.edu/cgi-bin/wa?RSS&L=NETWORKER