Joni
09-06-2011, 11:46
Привет всем!
Сбилось время на одном из контроллеров домена (((
Что делать? Доступа к нему нет, работает только терминалка. репликацию не проходит.
на команду w32tm /resync
отвечает The computer did not resync because the required time change was too big
Пробовал останавливать сервер, перезагружал, бес толку.
в реестре прописан ntp.mobatime.ru фаерволами для него все открыто.
Раньше все работало!!!! СЕЛА БАТАРЕЙКА М.....еЁ. Пришлось заменить. и пипец.
Windows cannot query for the list of Group Policy objects. Check the event log for possible messages previously logged by the policy engine that describes the reason for this.
The time service has detected that the system time needs to be changed by -10281592 seconds. The time service will not change the system time by more than -3600 seconds. Verify that your time and time zone are correct, and that the time source ntp.mobatime.ru (ntp.m|0x1|192.168.1.240:123->85.114.26.194:123) is working properly.
The Security System detected an authentication error for the server cifs/DC1. The failure code from authentication protocol Kerberos was "The time at the Primary Domain Controller is different than the time at the Backup Domain Controller or member server by too large an amount.
(0xc0000133)".
The kerberos client received a KRB_AP_ERR_TKT_NYV error from the server host/DC2.domain.ru. This indicates that the ticket used against that server is not yet valid (in relationship to that server time). Contact your system administrator to make sure the client and server times are in sync, and that the KDC in realm domain.RU is in sync with the KDC in the client realm.
The Security System detected an authentication error for the server LDAP/DC1.domain.ru/domain.ru@domain.RU. The failure code from authentication protocol Kerberos was "The time at the Primary Domain Controller is different than the time at the Backup Domain Controller or member server by too large an amount.
(0xc0000133)".
The Windows NT 4.0 or earlier replication checkpoint with the PDC emulator master was unsuccessful.
A full synchronization of the security accounts manager (SAM) database to domain controllers running Windows NT 4.0 and earlier might take place if the PDC emulator master role is transferred to the local domain controller before the next successful checkpoint.
The checkpoint process will be tried again in four hours.
Additional Data
Error value:
5 Access is denied.
The File Replication Service is having trouble enabling replication from DC2 to DC1 for c:\windows\sysvol\domain using the DNS name DC2.domain.ru. FRS will keep retrying.
Following are some of the reasons you would see this warning.
[1] FRS can not correctly resolve the DNS name DC2.domain.ru from this computer.
[2] FRS is not running on DC2.domain.ru.
[3] The topology information in the Active Directory for this replica has not yet replicated to all the Domain Controllers.
This event log message will appear once per connection, After the problem is fixed you will see another event log message indicating that the connection has been established.
For more information, see Help and Support Center at
Сбилось время на одном из контроллеров домена (((
Что делать? Доступа к нему нет, работает только терминалка. репликацию не проходит.
на команду w32tm /resync
отвечает The computer did not resync because the required time change was too big
Пробовал останавливать сервер, перезагружал, бес толку.
в реестре прописан ntp.mobatime.ru фаерволами для него все открыто.
Раньше все работало!!!! СЕЛА БАТАРЕЙКА М.....еЁ. Пришлось заменить. и пипец.
Windows cannot query for the list of Group Policy objects. Check the event log for possible messages previously logged by the policy engine that describes the reason for this.
The time service has detected that the system time needs to be changed by -10281592 seconds. The time service will not change the system time by more than -3600 seconds. Verify that your time and time zone are correct, and that the time source ntp.mobatime.ru (ntp.m|0x1|192.168.1.240:123->85.114.26.194:123) is working properly.
The Security System detected an authentication error for the server cifs/DC1. The failure code from authentication protocol Kerberos was "The time at the Primary Domain Controller is different than the time at the Backup Domain Controller or member server by too large an amount.
(0xc0000133)".
The kerberos client received a KRB_AP_ERR_TKT_NYV error from the server host/DC2.domain.ru. This indicates that the ticket used against that server is not yet valid (in relationship to that server time). Contact your system administrator to make sure the client and server times are in sync, and that the KDC in realm domain.RU is in sync with the KDC in the client realm.
The Security System detected an authentication error for the server LDAP/DC1.domain.ru/domain.ru@domain.RU. The failure code from authentication protocol Kerberos was "The time at the Primary Domain Controller is different than the time at the Backup Domain Controller or member server by too large an amount.
(0xc0000133)".
The Windows NT 4.0 or earlier replication checkpoint with the PDC emulator master was unsuccessful.
A full synchronization of the security accounts manager (SAM) database to domain controllers running Windows NT 4.0 and earlier might take place if the PDC emulator master role is transferred to the local domain controller before the next successful checkpoint.
The checkpoint process will be tried again in four hours.
Additional Data
Error value:
5 Access is denied.
The File Replication Service is having trouble enabling replication from DC2 to DC1 for c:\windows\sysvol\domain using the DNS name DC2.domain.ru. FRS will keep retrying.
Following are some of the reasons you would see this warning.
[1] FRS can not correctly resolve the DNS name DC2.domain.ru from this computer.
[2] FRS is not running on DC2.domain.ru.
[3] The topology information in the Active Directory for this replica has not yet replicated to all the Domain Controllers.
This event log message will appear once per connection, After the problem is fixed you will see another event log message indicating that the connection has been established.
For more information, see Help and Support Center at