I too have seen this and at first glance it appears to be a WINNs issue. I am not certain whether it is a WINNs issue but we have found this workaround, editing the LMHOSTS file on the client.
(I have taken comments directly from the LMHOSTS file itself that describe what this file does.)...
We are running several Win NT 4.0 servers all running SP6a.
This morning one of the servers had it's internal clock mysteriously changed to 02/22/2036. This caused several scheduled jobs to kick off at once (Backup Exec., NAV)due to the future date . The scheduled jobs began competing for...
As we have performed additional troubleshooting here it appears that the unusual behavior has stemmed from an OS level. All system event logs indicate a shift in date/time that correlates to Backup Exec.s internal clock. We are now investigating the possibility of a system board problem...
We have several servers running different versions of Veritas Backup Exec, single server editions as well as cross system backups. The strange date/time change occurred on a system running Seagate Backup Exec Vsn 7.0 REV719. This morning it was noted that backup exec had a job mysteriously...
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.