Can't log on locally to domain controller.
Hello,
I have active directory forest level native 2003.
I have 3 windows 2003 Domain controllers and 3 windows 2008 r2 sp1 domain controllers
Few days ago I've restarted DC (win 2008) with PDC role.
After the restart I couldn't log on locally to DC.
If I stop KDC service then I can logon.
After resetting computer password
netdom resetpwd
and after restart I can log in to DC only one time. Next logon attempt is without success.
In event log I can only find:
Event ID: 4
Source: Kerbeors
Type: Error
"The kerberos client received a KRB_AP_ERR_MODIFIED error from the server host/myserver.domain.com. This indicates that the password used to encrypt the kerberos service ticket is different than that on the target server. Commonly, this is due to identically named machine accounts in the target realm (domain.com), and the client realm. Please contact your system administrator."
Does anyone have any idea what is going on?
One more thing I've installed totally new windows 2008 r2 and added DC role to it.
After restart I have the same problem on my new DC.
I also tried dcdiag -fix.
Any help would be greatly appreciated.
Best Regards
FooKy
I have active directory forest level native 2003.
I have 3 windows 2003 Domain controllers and 3 windows 2008 r2 sp1 domain controllers
Few days ago I've restarted DC (win 2008) with PDC role.
After the restart I couldn't log on locally to DC.
If I stop KDC service then I can logon.
After resetting computer password
netdom resetpwd
and after restart I can log in to DC only one time. Next logon attempt is without success.
In event log I can only find:
Event ID: 4
Source: Kerbeors
Type: Error
"The kerberos client received a KRB_AP_ERR_MODIFIED error from the server host/myserver.domain.com. This indicates that the password used to encrypt the kerberos service ticket is different than that on the target server. Commonly, this is due to identically named machine accounts in the target realm (domain.com), and the client realm. Please contact your system administrator."
Does anyone have any idea what is going on?
One more thing I've installed totally new windows 2008 r2 and added DC role to it.
After restart I have the same problem on my new DC.
I also tried dcdiag -fix.
Any help would be greatly appreciated.
Best Regards
FooKy
Systech Admin
What error did you get while login?
ASKER
Wrong username or password.
Best Regards
Fooky
Best Regards
Fooky
ASKER
I found new event log entry:
this is during logon attempt.
Failure Information:
Failure Reason: An Error occured during Logon.
Status: 0xc000006d
Sub Status: 0x0
An account failed to log on.
Subject:
Security ID: SYSTEM
Account Name: KHAT$
Account Domain: PJWSTK
Logon ID: 0x3e7
Logon Type: 10
Account For Which Logon Failed:
Security ID: NULL SID
Account Name: droot
Account Domain: PJWSTK.EDU.PL
Failure Information:
Failure Reason: An Error occured during Logon.
Status: 0xc000006d
Sub Status: 0x0
Process Information:
Caller Process ID: 0x1028
Caller Process Name: C:\Windows\System32\winlog
Network Information:
Workstation Name: KHAT
Source Network Address: 10.2.2.24
Source Port: 3820
Detailed Authentication Information:
Logon Process: User32
Authentication Package: Negotiate
Transited Services: -
Package Name (NTLM only): -
Key Length: 0
This event is generated when a logon request fails. It is generated on the computer where access was attempted.
The Subject fields indicate the account on the local system which requested the logon. This is most commonly a service such as the Server service, or a local process such as Winlogon.exe or Services.exe.
The Logon Type field indicates the kind of logon that was requested. The most common types are 2 (interactive) and 3 (network).
The Process Information fields indicate which account and process on the system requested the logon.
The Network Information fields indicate where a remote logon request originated. Workstation name is not always available and may be left blank in some cases.
The authentication information fields provide detailed information about this specific logon request.
- Transited services indicate which intermediate services have participated in this logon request.
- Package name indicates which sub-protocol was used among the NTLM protocols.
- Key length indicates the length of the generated session key. This will be 0 if no session key was requested.
Event ID 4625 source Windows security auditing
this is during logon attempt.
Failure Information:
Failure Reason: An Error occured during Logon.
Status: 0xc000006d
Sub Status: 0x0
An account failed to log on.
Subject:
Security ID: SYSTEM
Account Name: KHAT$
Account Domain: PJWSTK
Logon ID: 0x3e7
Logon Type: 10
Account For Which Logon Failed:
Security ID: NULL SID
Account Name: droot
Account Domain: PJWSTK.EDU.PL
Failure Information:
Failure Reason: An Error occured during Logon.
Status: 0xc000006d
Sub Status: 0x0
Process Information:
Caller Process ID: 0x1028
Caller Process Name: C:\Windows\System32\winlog
Network Information:
Workstation Name: KHAT
Source Network Address: 10.2.2.24
Source Port: 3820
Detailed Authentication Information:
Logon Process: User32
Authentication Package: Negotiate
Transited Services: -
Package Name (NTLM only): -
Key Length: 0
This event is generated when a logon request fails. It is generated on the computer where access was attempted.
The Subject fields indicate the account on the local system which requested the logon. This is most commonly a service such as the Server service, or a local process such as Winlogon.exe or Services.exe.
The Logon Type field indicates the kind of logon that was requested. The most common types are 2 (interactive) and 3 (network).
The Process Information fields indicate which account and process on the system requested the logon.
The Network Information fields indicate where a remote logon request originated. Workstation name is not always available and may be left blank in some cases.
The authentication information fields provide detailed information about this specific logon request.
- Transited services indicate which intermediate services have participated in this logon request.
- Package name indicates which sub-protocol was used among the NTLM protocols.
- Key length indicates the length of the generated session key. This will be 0 if no session key was requested.
Event ID 4625 source Windows security auditing
Did you configure the DC using snpashot/cloning or image, it looks to be there is duplicate SPN issue.
http://technet.microsoft.com/en-us/library/cc733987%28WS.10%29.aspx
It can be due to replication issue or AD database corruption.
http://blogs.technet.com/b/askds/archive/2008/05/14/troubleshooting-kerberos-authentication-problems-name-resolution-issues.aspx
http://technet.microsoft.com/en-us/library/cc738673%28WS.10%29.aspx
Purge the kerberos ticket using KerbTray tool.
http://technet.microsoft.com/en-us/library/cc733987%28WS.10%29.aspx
It can be due to replication issue or AD database corruption.
http://blogs.technet.com/b/askds/archive/2008/05/14/troubleshooting-kerberos-authentication-problems-name-resolution-issues.aspx
http://technet.microsoft.com/en-us/library/cc738673%28WS.10%29.aspx
Purge the kerberos ticket using KerbTray tool.
ASKER
Nothing helped.
I'm thinking it might be something wrong with SPN's or DNS but I verified all and nothing.
We are waiting for Microsoft support now its on Premier level.
I'll be back when something new will come up.
Best Regards
FooKy
I'm thinking it might be something wrong with SPN's or DNS but I verified all and nothing.
We are waiting for Microsoft support now its on Premier level.
I'll be back when something new will come up.
Best Regards
FooKy
ASKER CERTIFIED SOLUTION
membership
This solution is only available to members.
To access this solution, you must be a member of Experts Exchange.
ASKER
We solved this with Microsoft Support