I'm not a Windows heavy, but I believe the "read for everyone" doesn't help you because by default the scheduler service runs under the SYSTEM account, which isn't logged in to the NT domain, and therefore can't be authenticated to read a network drive.
Try it once with a valid id with domain rights, that should prove whether or not it's the problem. And yes, we don't have a good way to do it because even if you set it up with a domain account, once the password changes, you're dead. So we just don't do it, we put a TSM client on every system we want to back up. It's Windoze, there are lots of things not to like! (BTW, like your tag line!) -----Original Message----- From: William Boyer To: [EMAIL PROTECTED] Sent: 11/30/01 11:08 AM Subject: Scheduler service logon account Normally this is set up as using the local admin account, but I've recently gotten a server that needs to backup a remote PC's share point. It keeps failing with ANS1228E Sending of object '\\ntpc1676\sx65db' failed ANS1063E Invalid path specification After searching the archives, it seems that my problem here is security on the remote share. I believe it is set up as Read for Everyone. Does this not include my TSM node's local account? What do most of you do in this case. I'm reluctant to user a domain userid for this. I've had experience where if this userid gets locked or someone just changes the password then all my backups crash. TIA, Bill Boyer "There's no place like ~ There's no place like ~" - ???
