After setting up Duo for RDP, I enter my credentials when connecting, then see another Windows login screen asking for them again. The Duo prompt appears after that. Why are there two password prompts?
Why does RDP ask for my password twice after setting up Duo?
Answers
Check whether Network Level Authentication is enabled on the session host. With Duo for Windows Logon and NLA, the first prompt can authenticate the connection, while the second is for the interactive Windows logon that Duo protects. The MFA prompt then follows that second login.
I wouldn't turn off NLA just to get rid of the extra prompt. If the login flow needs to change, look into an MFA setup at an RD Gateway instead of the session host, and check the security implications before changing anything.
Reply to this answer
Are you using an RD Gateway? That can introduce a separate gateway authentication step as well as authentication to the destination computer. In the RDP client's advanced gateway settings, look for the option to use the gateway credentials for the remote computer and save the connection. That may help when the same credentials work for both.
Reply to this answer
Another thing to check is whether any other login or password management software is installed on the host. Multiple products modifying the Windows sign-in flow can interfere with each other. If there are other credential providers in play, review their compatibility and configuration rather than assuming Duo is the only part involved.
Reply to this answer
Device registration is worth checking if the prompts seem specific to one machine. Run dsregcmd /status on that machine and review the Device State and Device Details sections, including DeviceAuthStatus. A stale or orphaned device registration can be a clue, though it doesn't prove that's the cause here.
Reply to this answer
If the host has been through several Duo configuration or deployment changes, I'd open a support ticket with Duo. Give them the exact prompt sequence and whether NLA or an RD Gateway is in use. That should help separate an expected login flow from a configuration issue.
Reply to this answer
Add your answer
Answers are reviewed before publication.
_j73~clampbadge.6:
That only applies if the connection actually goes through a gateway. Check the saved connection settings before assuming that's the cause.