Share via

RPD issue with domain and domain username

SSE@TUE 160 Reputation points
2025-09-02T07:29:50.0266667+00:00

Hi,

I have a issue with RDP. The user connect via RDP to many machines, it is working without any issue, but since some days, the RPD does not work, it is displaying wrong password, but the is not truth

after some searching, I have figure out, the domain is appearing with TLD.

it means, my domain is called: adamix.com

the user login with domain user via RDP as:

adamix\mmustermann

but it is appearing: adamix.com\mmustermann

That is wrong, I have no Idea why.

Can you help please?

Regards

Nick

Windows for business | Windows Client for IT Pros | User experience | Remote desktop clients
0 comments

1 answer

Sort by: Most helpful
Most helpful Newest Oldest
  1. Domic Vo 7,830 Reputation points Independent Advisor
    2025-09-02T10:12:43.75+00:00

    Dear Nick,

    Thank you for reaching out and providing details about the issue you're experiencing with Remote Desktop Protocol (RDP). We understand that users are now seeing the domain displayed as adamix.com\mmustermann instead of the expected adamix\mmustermann, resulting in failed login attempts with a "wrong password" message.

    This behavior typically occurs when the RDP client defaults to using the User Principal Name (UPN) format (******@domain.com) or the fully qualified domain name (FQDN) instead of the NetBIOS domain name (DOMAIN\user). While both formats are valid in Active Directory environments, some systems or configurations may not accept the FQDN format for authentication.

    Here are recommended Steps:

    1. Explicitly Specify the Domain Format In the RDP client, under the Advanced > Settings > Authentication tab, ensure the username is entered as adamix\mmustermann and not ******@adamix.com.
    2. Clear Cached Credentials Cached credentials may be causing the incorrect domain format to persist. You can clear them by: Opening Credential Manager (control /name Microsoft.CredentialManager) Removing any saved entries related to the affected machines
    3. Check Terminal Services Client Registry On the client machine, navigate to: HKEY_CURRENT_USER\Software\Microsoft\Terminal Server Client Review entries under Servers or Default to ensure no incorrect domain formats are cached.
    4. Verify Domain Configuration Confirm that the NetBIOS name (adamix) is correctly registered in Active Directory and DNS. You can use the Get-ADDomain PowerShell cmdlet to verify both the NetBIOS and FQDN values.

    Group Policy or RDP Host Settings If recent changes were made to Group Policy or the RDP host configuration, ensure no policies are enforcing UPN-only logins or overriding default domain behavior.

    I hope this helps. Just kindly tick Accept Answer that others in the community facing similar issues can easily find the solution. Your contribution is highly appreciated.

    Best regards,

    Domic Vo

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.