Share via

I am not able to connect to VM after changing password of Active directory.

vishal kumar 45 Reputation points
2026-03-13T14:54:00.0766667+00:00

I changed the password of active directory as an admin while trying to connect Microsoft Active directory syn by uninstalling and reinstalling it. on 11th March evening I start getting error of password incorrect then next day I am getting different error . Please see attackment in error.RemoteDPError.png

Microsoft Security | Microsoft Entra | Microsoft Entra External ID

1 answer

Sort by: Most helpful
Most helpful Newest Oldest
  1. VEMULA SRISAI 12,830 Reputation points Microsoft External Staff Moderator
    2026-03-18T06:15:29.8566667+00:00

    Hello vishal kumar,

    The error shown (RDP error code: 0x4615) indicates that the connection to the VM is failing before user authentication occurs. This means it is no longer related to an incorrect password.

    Since this issue started after the Active Directory password change and Azure AD Connect reinstallation, the most likely causes are RDP service, network connectivity, NLA, or domain communication issues on the VM.

    Please check the following:

    1. Ensure the VM is running and reachable
      • Verify the VM status is Running
      • Confirm port 3389 is allowed in the Network Security Group and VM firewall
    2. Validate domain connectivity
      • If the VM cannot reach the Domain Controller, RDP sessions will fail with this error
      • Ensure DNS settings are correctly pointing to the DC
    3. Check Network Level Authentication (NLA)
      • After AD changes, NLA can fail due to Kerberos or authentication issues
      • Temporarily disabling NLA and rebooting the VM often resolves this
    4. Confirm Remote Desktop Services are running
      • If possible, access the VM using Azure Serial Console / Run Command
      • Verify RDP services are enabled and running

    Since the error occurs before credentials are validated, resolving network/RDP/NLA or domain connectivity should restore access.

    If the issue persists, please confirm:

    • Whether the VM is domain-joined
    • Whether you can access it via Serial Console
    • Any recent NSG, firewall, or DNS changes

    This will help narrow down the root cause further.

    I kindly request you to please comment if this doesn’t fully address your issue or if you need any additional information. I’ll be happy to assist you further.

    Was this answer helpful?

    0 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.