I need to remote desktop connect to a windows PC on a local network. This works flawlessly when done from my windows PC but I’m having issues on Linux Mint.

I’m using Remmina since it was the most common answer to a linux RDP client. I imported the RDP file from windows but I also created a connection with manually filled info.

First issue is that linux can’t connect to the machine by its name - on windows ping MYPC-321 works, on linux mint it throws an error. However, ping MYPC-321.local does work, but if I try to use that as the address in Remmina, it fails again. Is there a way to connect using just name since I dont want to have to recheck the IP address every day?

But let’s say this is for now resolved if I just use the local IP address. The second, main problem, is authentication. No matter what I put into the username and domain fields of Remmina’s authentication GUI, it always instantly fails and Remmina reloads the screen without giving me any error. The credentials are the same as when connecting from the windows PC (although I dont have to specify the domain there) so I have no idea what could be the problem here.

Is there something else I’m missing, something fundamentally different about how this works on linux? I wasn’t expecting for such a simple and straightforward thing to instantly cause issues.

  • CynoOP
    1·
    2 months ago

    I can’t access my router due to ISP policy. Some tools do allow connecting to the name.local format (Vinagre did for example, but that one has other bugs so I gave up on it) so I’m starting to think that’s actually just a problem with Remmina, not a general Linux issue.

    Not sure what you mean by the domain question, I do have a domain specified if i check the windows machine pc properties so I’m guessing I am actually in one?

    • ArbiterXero@lemmy.world
      2·
      2 months ago

      What is that domain? Is it the pc name?

      If you don’t know, then you’re not in a domain.

      Go to your windows machine and look at your ip settings.

      The router will be giving you an ip address like 192.168.1.X

      odds are good that the router has a section in the low range of x that is still accessible but not under dhcp (don’t use 1 !!!)

      You can set yourself a static ip in that range.

      As for your login, use a period as your domain.

      .\myusername

      • CynoOP
        2·
        2 months ago

        I’ll give it a try, thanks. Maybe I was just messing around with domains too much, could be that part is more strictly defined here compared to win