Windows 10: Remmina "Could not access the RDP server. Account restricted."

Hi!

I cannot seem to find any documentation online to help me solve this issue. I am running Remmina on my Arch Linux machine. I upgraded my Windows 10 machine from Home edition to Pro with a non-valid key. Windows is not activated, but I can enable remote desktop in the settings. After following this guide, Remmina was telling me it "Could not find the server". I replaced the PC name with the IPv4. After this change, a credentials prompt would pop up, but no matter what username or password I entered, it wouldn't take, the prompt just kept reappearing. Finally, I decided to login to a local account on the Win 10 machine without a password. Now, when I try to connect, I get the "Account restricted" error.

Any thoughts? Thanks!

submitted by /u/SwankyBarbecue
[link] [comments]

:)

 

License remote access restrictions

Dear SarahKong!

As you see above license text say about "remote access".

By text it is not restricted to preistalled product (e.g. RDP), it can related to VNC too.

The server licence is an other thing.

We talk about desktop operating systems.

If I understand you well:

if I use dekstop pro operating system, then it has RDP client and server inculded, and then I can use both of them.

if I use dekstop home operating system, then it has RDP client inculded. I can use RDP clinet to connect, but I cant use RDP server beacuse it is not included.

But I still not understand restriction of MS OEM or Retial license,
2. d. (v). See text above.

Best regards,

 

weird problem with RDP to Windows 10 - blank screen after minimizing

Should not be as you can only legitimately log on one user at a time to consumer editions. There are hacks to enable multiple log-in but that is outside scope of the question really.

Unless MS broke something by fixing something else of course.

Everything else I tried (WebEx, TeamViewer et al) is much worse than RDP. If you are connecting from Linux to Windows Remmina is best of the bunch but it uses RDP anyway.

 

RDP restrictions in W10

Currently we have several users accessing several W7 pc's using RDP. The pc's have custom software on them, that cannot be launched via RDP. Therefore, I created a local account, set up autologin, and auto
launch custom software on login. Currently we have set up a local policy to only allow 1 RDP session. If a secondary user tries to log in while the session is in use they receive an error message "An internal error has occurred" This prompt shows before the
user is asked for credentials. This way the user knows someone else is using that session and they can try one of the other pc's.

I am working on replacing the W7 with W10. but when I set the policies, and log in via RDP, I am able to take over a session that is actively in use without issue. How do I prevent this in W10?

I have reviewed W10 RDP settings - no option to limit sessions, only users

I have set the "gpedit > Administrative Templates > Windows Components > Remote Desktop Session Host > Connections, and set the Limit number of connections"=1, and also "Restrict Remote Desktop Services
to a single Remote Desktop Service session" = enabled.

It doesn't limit a secondary session from kicking of the previous session. It doesn't even notify the original user.

I'm not sure what I'm missing or if we can even do this anymore in W10. The only info I can find is for w7 or windows server.

Has anyone seen this before? Any advice would be appreciated. Thanks in advance.

Currently we have several users accessing several W7 pc's using RDP. The pc's have custom software on them, that cannot be launched via RDP. Therefore, I created a local account, set up autologin, and auto
launch custom software on login. Currently we have set up a local policy to only allow 1 RDP session. If a secondary user tries to log in while the session is in use they receive an error message "An internal error has occurred" This prompt shows before the
user is asked for credentials. This way the user knows someone else is using that session and they can try one of the other pc's.

I am working on replacing the W7 with W10. but when I set the policies, and log in via RDP, I am able to take over a session that is actively in use without issue. How do I prevent this in W10?

I have reviewed W10 RDP settings - no option to limit sessions, only users

I have set the "gpedit > Administrative Templates > Windows Components > Remote Desktop Session Host > Connections, and set the Limit number of connections"=1, and also "Restrict Remote Desktop Services
to a single Remote Desktop Service session" = enabled.

It doesn't limit a secondary session from kicking of the previous session. It doesn't even notify the original user.

I'm not sure what I'm missing or if we can even do this anymore in W10. The only info I can find is for w7 or windows server.

Has anyone seen this before? Any advice would be appreciated. Thanks in advance.