We are experiencing a similar problem on our network; We are W2K Workstations on a 2K domain. The users will login most of the way (they pull roaming profiles) and then hourglass in the taskbar until they either crash the machine or call one of us. Checking taskmanager will show no major CPU...
Is your NIC driver updated for the people getting locked out? And is it set for that lovely default setting (makes real sense on a network) to 'Allow the computer to shut down this device to save power'? the outdated NIC drivers causing this lockout problem is a known issue; as to losing...
have you run BEdiag and checked the results? If you haven't run this before, it is located in BE Device tab\properties of the server\system tab - click on 'run bediag'. This can give you a comprehensive list of configurations and issues for your backup.
Veritas recomends using Veritas drivers for the tape drive. Don't know about the SCSI card; you may wish to go to the knowledge base at www.veritas.com for that answer.
part of the problem with Veritas backup is terminology; what BUexec calls a failed job is very often what Arcserve would call an 'incomplete' job; it fails to back up all files and is therefore a 'failed' job - this does not mean you cannot restore most information from the backup job. As to the...
If you are in a mixed mode environment, 2K and NT4, with Active Directory, you can get the error message that the account is locked out; when you check the account you will find that the account itself is NOT locked out. This is a computer password issue not a user password issue. Every 30 days...
See if unchecking 'write checksums to media' in Veritas will resolve the spontaneous reboots and if it does; it's an issue of how checksums are handled and you may need to replace your motherboard.
This site uses cookies to help personalise content, tailor your experience and to keep you logged in if you register.
By continuing to use this site, you are consenting to our use of cookies.