My company has been using Backup Exec 8.6 for Windows NT/2000, loaded on a Windows NT 4.0 sp6a machine.
We haven't had any problems using the system for the entire year that I've been with the company; we must have run out of luck.
We had a server crash yesterday; another NT4 sp6a. I was unable to repair some OS corruption, and reloaded the server.
I went to restore the server from the last backup, and BE keeps failing the job because it cannot connect to the c$ share on the rebuilt server.
I've opened the server up to basically allow everyone access as an admin (something I normally would never do, except in this instance I intended to change everything again right away), but BE still won't restore. It keeps giving me the "unable to connect" error message, after I start the restore.
I've applied every Veritas Hotfix appropriate for this installation, in the proper order- by the book, and I still can't restore the server.
Beyond the poor Veritas support, indicating a similar problem associated with Exchange servers (which this server is not), I have found nothing to indicate my problem is common.
Does anyone have any ideas of what my problem might be?
Please help!
We haven't had any problems using the system for the entire year that I've been with the company; we must have run out of luck.
We had a server crash yesterday; another NT4 sp6a. I was unable to repair some OS corruption, and reloaded the server.
I went to restore the server from the last backup, and BE keeps failing the job because it cannot connect to the c$ share on the rebuilt server.
I've opened the server up to basically allow everyone access as an admin (something I normally would never do, except in this instance I intended to change everything again right away), but BE still won't restore. It keeps giving me the "unable to connect" error message, after I start the restore.
I've applied every Veritas Hotfix appropriate for this installation, in the proper order- by the book, and I still can't restore the server.
Beyond the poor Veritas support, indicating a similar problem associated with Exchange servers (which this server is not), I have found nothing to indicate my problem is common.
Does anyone have any ideas of what my problem might be?
Please help!