"James Pratt" <jpratt AT norwich DOT edu> wrote on 03/09/2010 08:53:04 AM:

> I think he is saying to change the service account on the target R2
> server to run nsrexecd service as a different user, however, my testing
> last week of a full backup and recover of an R2 server (in a 2003 domain
> I should add) gave me the same error using a Domain account from the NW
> side - I ended up just using the R2 server's local administrator account
> in the NW client config instead, and that took care of it, was able to
> do a full backup and recover etc - (We do not change service account
> users unless we have to - it's come back to haunt us too many times, but
> that's just us). 

Really. In the client config, did you use just "administrator" and the 
local machine administrator password? Or did you need to do "machine 
name\administrator", and then the local password? At the moment, I am 
using a domain account that is a domain admin, in the "Remote Access" 
section of the client config.

(this would be a Win2008 R2 server in a Win2003 domain, as well)

I can sympathize with changing service accounts, and their passwords - 
just had to do the same thing myself. 

If I was to change the service account, I presume I would need to use a 
domain account that was set as local administrator?

Thanks

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