General discussion

Locked

Veritas Backup Exec 8.6

By STURNER ·
Verita Backup Exec 8.6
I am in need of major assistance with Veritas Backup Exec 8.6. Here is the scenerio:

Two domains: 1. WIN2K 2. NT40

Back up device is located on WIN2K and remote agents have been installed on 4 of 6 servers in NT40 domian. When trying to install Remote agent on other two servers I get an error stating:

"Unable to connect to Windows NT/2000 system. You may have entered an invalid username or passsword, or you may already be logged in with a different username and password. Do you want to try again?"

The account I am using is valid and was used to install the other servers. There is also a validated two-way trust between the two domains. The only thing that is curious is that one of the servers is a PDC, but the other that will not load is a member...so?

I need any and all help to beat this. Please any ideas or thoughts could be helpful!


Thank you very much!!!

Stephen

This conversation is currently closed to new comments.

9 total posts (Page 1 of 1)  
| Thread display: Collapse - | Expand +

All Comments

Collapse -

Veritas Backup Exec 8.6

by LukeMc In reply to Veritas Backup Exec 8.6

Make sure service account for BackupExec has domain admins access, or at least in a group that has backup operators access on target servers.

Make sure the service account is unique to the domain containing the backup server, or has exactly thesame password as the same account in both domains.

Good Luck.

Collapse -

Veritas Backup Exec 8.6

by STURNER In reply to Veritas Backup Exec 8.6

I appreciate you attempt, I ahve already done this. The account created for use with back ups, is in both domain's "Domain Admin's" group. And the right to log on as a service and locally and as OS has been verified. What is baffiling here is the fact that I could install the remote agent on four servers in the NT domain without fail, but these two are preventing the install with the above error. They all use the same backup account!!

Collapse -

Veritas Backup Exec 8.6

by george In reply to Veritas Backup Exec 8.6

Have you tried to long on to those machines using the backup account? This will tell you if you are having trouble authenticating to the Domain from those machines.

George

Collapse -

Veritas Backup Exec 8.6

by STURNER In reply to Veritas Backup Exec 8.6

Yes I have already tried this. I Did for that exact reason. Thanks for trying to help!!

Collapse -

Veritas Backup Exec 8.6

by natecasp In reply to Veritas Backup Exec 8.6

You need to look for something that is different between these problem servers and the working ones. I am sure you have already called Veritas about this and they were no help. The only other thing I can offer you is trying to change the name of these servers and readd them to the domain. This is obviously a domain authentication problem and by removing the old server name and readding it may correct something that may be messed up.

Another thing I would try is providing the Administrator account and password when asked of the account you would like to use. This will difinitely rule out any problem with the backup account and confirm that it is a domain authentication problem.

Let me know what you find out.

Collapse -

Veritas Backup Exec 8.6

by STURNER In reply to Veritas Backup Exec 8.6

Poster rated this answer

Collapse -

Veritas Backup Exec 8.6

by /dev/null In reply to Veritas Backup Exec 8.6

I've encountered similar problems with Backup Exec 8.0 (a while ago). If I remember correctly, during the remote agent install it will ask for a username/password.

If you already have an authenticated connection (null connection (IPC$) or mappeddrive, printer connections may also cause this) to the target machine you might encounter this.

Before trying to install on the target machine, check 'net use' to verify you have NO connections to that machine. If you do have open connections for no apparent reason, do a 'net use * /d'. This will (at least try to) delete all open connections. Double-check the 'net use' results after this.

I've had to do this a couple times because of printer connections, mapped drives, and just plain browsing other servers.

Good luck.

Collapse -

Veritas Backup Exec 8.6

by STURNER In reply to Veritas Backup Exec 8.6

THANK YOU, THANK YOU and THANK YOU again!!!

This solved the issue!!!!!

Collapse -

Veritas Backup Exec 8.6

by STURNER In reply to Veritas Backup Exec 8.6

This question was closed by the author

Back to Windows Forum
9 total posts (Page 1 of 1)  

Related Discussions

Related Forums