A
arp
Our Configuration is as follows
Windows 2000 domain
1 PDC at Head office
17 satellite offices connected by VPN
Issues
If the Satellite office loses the connect to the PDC, the users in the
satellite office are no longer able to log on, even though the DC in
their office is still fully operational.
I guess this will be DNS, but don't know which way to go. Please offer
any advice.
Event viewer Errors
No Windows NT or Windows 2000 Domain Controller is available for
domain X. The following error occurred:
There are currently no logon servers available to service the logon
request.
Data:
0000: 5e 00 00 c0 ^..À
Because of repeated network problems, the time service has not been
able to find a domain controller to synchronize with for a long time.
To reduce network traffic, the time service will wait 960 minutes
before trying again. No synchronization will take place during this
interval, even if network connectivity is restored. Accumulated time
errors may cause certain network operations to fail. To tell the time
service that network connectivity has been restored and that it should
resynchronize, execute "w32tm /s" from the command line.
Data:
0000: e5 03 00 00 å...
The Windows Time Service was not able to find a Domain Controller. A
time and date update was not possible.
Data:
0000: e5 03 00 00 å...
The SAM database was unable to lockout the account of ? due to a
resource error, such as a hard disk write failure (the specific error
code is in the error data) . Accounts are locked after a certain
number of bad passwords are provided so please consider resetting the
password of the account mentioned above.
Data:
0000: a5 02 00 c0 ¥..À
Windows 2000 domain
1 PDC at Head office
17 satellite offices connected by VPN
Issues
If the Satellite office loses the connect to the PDC, the users in the
satellite office are no longer able to log on, even though the DC in
their office is still fully operational.
I guess this will be DNS, but don't know which way to go. Please offer
any advice.
Event viewer Errors
No Windows NT or Windows 2000 Domain Controller is available for
domain X. The following error occurred:
There are currently no logon servers available to service the logon
request.
Data:
0000: 5e 00 00 c0 ^..À
Because of repeated network problems, the time service has not been
able to find a domain controller to synchronize with for a long time.
To reduce network traffic, the time service will wait 960 minutes
before trying again. No synchronization will take place during this
interval, even if network connectivity is restored. Accumulated time
errors may cause certain network operations to fail. To tell the time
service that network connectivity has been restored and that it should
resynchronize, execute "w32tm /s" from the command line.
Data:
0000: e5 03 00 00 å...
The Windows Time Service was not able to find a Domain Controller. A
time and date update was not possible.
Data:
0000: e5 03 00 00 å...
The SAM database was unable to lockout the account of ? due to a
resource error, such as a hard disk write failure (the specific error
code is in the error data) . Accounts are locked after a certain
number of bad passwords are provided so please consider resetting the
password of the account mentioned above.
Data:
0000: a5 02 00 c0 ¥..À