Share via

DC2025-SERVER

Spiros Boua 0 Reputation points
2026-06-23T12:13:46.7033333+00:00

Hello,

I have a Domain Controller windows server 2025 24H2 that when i try to log in with domain admin credentias it says password is wrong .Due to the fact that i have another 5 DC controller in different areas i can log in with the credentials in all servers and the domains with the same password. I create a new user admin account and i log in .

I can not reset the password due to the fact that a lot of services run with the password.

User's image

Windows for business | Windows Server | User experience | Other
0 comments No comments

2 answers

Sort by: Most helpful
  1. Spiros Boua 0 Reputation points
    2026-06-23T13:01:16.1033333+00:00

    Hello,

    What parametres i change ?

    User's image

    Was this answer helpful?

    0 comments No comments

  2. VPHAN 37,140 Reputation points Independent Advisor
    2026-06-23T12:50:12.2933333+00:00

    Hi Spiros Boua,

    Your previous diagnosis correctly identified that this is not an Active Directory replication issue, but rather an interoperability problem driven by Windows Server 2025's strict deprecation of legacy Kerberos encryption types. This cryptography protocol mismatch explains why your newly created account, which natively uses modern AES encryption, works flawlessly while your older admin account is rejected. Because you cannot reset the password without disrupting essential services, you must force the legacy account to utilize modern encryption standards to bridge this gap. Log into the 2025 Domain Controller using your functional temporary admin account and open Active Directory Users and Computers. Enable Advanced Features from the View menu, open the properties of your problematic primary admin account, and navigate to the Attribute Editor tab. Locate the msDS-SupportedEncryptionTypes attribute and change its value to 24, which explicitly instructs the system to use robust AES-128 and AES-256 encryption. If adjusting the attribute directly is not feasible, you can open the Registry Editor on the 2025 server and navigate to HKEY_LOCAL_MACHINE\System\CurrentControlSet\Services\Kdc to review and adjust the Key Distribution Center parameters to temporarily accommodate the legacy authentication request. This approach updates the cryptographic handshake without altering your actual password, preserving your running services while allowing the new server to successfully authenticate your credentials.

    Hope this answer has brought you some useful information. If it did, please hit “accept answer”. Should you have any questions, feel free to leave a comment.

    VPHAN

    Was this answer helpful?

    0 comments No comments

Your answer

Answers can be marked as 'Accepted' by the question author and 'Recommended' by moderators, which helps users know the answer solved the author's problem.