Error: The username or password is incorrect - Domain Controller 2008 r2 sp 1

Hello,
when I'm trying to logon locally to DC  server I'm getting "Username or password is incorrect"

When I stop KDC service then I can logon.
netdom resetpwd didn't help.
dcdiag /fix also didn't help.

In eventlog i have this entry:

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\winlogon.exe

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

Best Regards
FooKy
LVL 11
f_o_o_k_yAsked:
Who is Participating?
 
f_o_o_k_yAuthor Commented:
Hello,
finally we managed to find solution.
On all machines we needed to set
KEY: HKEY_LOCAL_MACHINE\SOFTWARE\Microsoft\Windows\CurrentVersion\Policies\System\kerberos\parameters\supportederncyptiontypes
VALUE: 7fffffff
Thanks for your time.
Best Regards
FooKy
0
 
AwinishCommented:
0
 
f_o_o_k_yAuthor Commented:
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
0
 
f_o_o_k_yAuthor Commented:
We solved this using Microsoft Support
0
Question has a verified solution.

Are you are experiencing a similar issue? Get a personalized answer when you ask a related question.

Have a better answer? Share it in a comment.

All Courses

From novice to tech pro — start learning today.