2 replies
by hal 9000
The reason for this is that 2003 really works better as a Domain Controller and not in a Workgroup as a lot of the network settings get lost in the mix.
You'll find that using 2003 as a Domain controller even if it is on another domain controlled by several different servers up line it will work much better and perform properly but if you keep it restricted to a Workgroup you'll constantly run into problems with things not working properly if at all.
Col
by winterfrost
I hate to completely disagree with HAL, but I haven't had any problems running Win2k3 in workgroup mode...
However, I don't think that has anything to do with the problem. It sounds to me like it's informing you that the Remote Agent is not installed on the other server you are trying to back up. Do you have a Remote Agent installed there?
If you do have the remote agent installed, the other possibility is simply an authentication problem. As a member server, your backup server must use a *local* account on the server it is backing up to authenticate (you can configure the authentication options in the backup job). I would guess that the problem is going away when you make the backup server a domain controller because the service account you are using for Backup Exec may be a Domain Admin account, which would have access to the remote server.
This discussion is closed to new replies.
Trending Windows Forum posts
Sort by Trending