EDIT 2: Solved. I was sending uppercase characters when I would do the connection from MS RDP. My Pop OS login username has uppercase characters so I was just matching that. I got confused because the username defined in the Pop remote desktop settings is the same username, but spelled all lowercase. Once I altered the username I was sending from MS RDP to match exactly including casing, it worked.

As a side note, the default MS RDP app doesn’t handle the resolution properly. I switched to using RDCMan from the Sysinternals Suite and it handles the resolution perfectly and you can set scaling on it so you don’t have to worry about that. I’d recommend RDCMan if anyone else is running into the same issue.

EDIT: Error code image attached and extended details pasted here.

[Window Title]
Remote Desktop Connection

[Content]
An authentication error has occurred.
The token supplied to the function is invalid

Remote computer: [Redacted]

[^] Hide details  [OK]

[Expanded Information]
Error code: 0x0
Extended error code: 0x0
Timestamp (UTC): 08/05/25 01:32:11 PM
Activity ID: 2473cbfb-5b74-4229-8644-1cf6b0bb0100

Hey Everyone,

I was wondering if anyone can help troubleshoot an issue I’m having trying to RDP from my Windows 11 box to my Pop!_OS box.

I have Remote Desktop enabled in Pop and I’ve set the username and password.

When I try to connect from Windows using Microsoft’s RDP application, I get an invalid token error.

Is anyone able to tell me what I’m missing in the setup?

Thanks

  • just_another_person@lemmy.worldEnglish
    4·
    26 days ago

    Specific error messages would be helpful, or a screenshot.

    Just for funsies: make sure the time and time zone is correct on both machines. If either needs changing, reboot it, and try again.

    • ChocolateFrostedSugarBombs@lemmy.worldOPEnglish
      1·
      26 days ago

      You’re totally right, I forgot to add the picture and details when I posted. I updated the post with an image and expanded text. I did confirm that the time and timezone are consistent between the two devices.

      • just_another_person@lemmy.worldEnglish
        2·
        26 days ago

        Is this a stock RFP client, or is there some authentication information being passed? It sure seems like it’s passing something along and being rejected. I’d check your client and make sure it’s not using your logged in credentials or some domain info and passing that.

        I’d also check the logs on the PopOS machine to see: 1) If the connection is making it there 2) Why it’s being rejected.

        Work from there.

        • ChocolateFrostedSugarBombs@lemmy.worldOPEnglish
          2·
          26 days ago

          Figured it out…capitalization…always lol. The username defined on Pop was all lowercase and I was sending the username via MS RDP with a few upper case letters since that’s how it’s spelt for the actual Pop sign on user.

        • ChocolateFrostedSugarBombs@lemmy.worldOPEnglish
          1·
          26 days ago

          It’s the stock RDP settings built into Pop. I am passing authentication info from my Windows client to Pop which is the authentication info defined in Pop’s RDP settings (username and password). I’m manually defining the auth info on the Windows Client so it’s not passing in the default current login information.

          I’ll see if the logs mention anything. It doesn’t look like there’s an application specific log for the RDP function in Pop so maybe it’s just under syslog or journal?

  • folekaule@lemmy.worldEnglish
    2·
    26 days ago

    I would also like to set if there is a solution to this. I’m on Fedora with Wayland and I have the same problem.

    The best I can figure out so far is that Wayland support for rdp is limited right now and to use x11 if you really need remote desktop.

    • ChocolateFrostedSugarBombs@lemmy.worldOPEnglish
      3·
      26 days ago

      EDIT: Figured it out…the username I defined in the Pop settings was all lowercase. I was sending a few uppercase letters via MS since that’s how the actual Pop login username is spelt.

      Dang…ok thanks. I’ll keep working on it and I’ll update in case I find a solution.