The remote computer disconnected the session because of an error in the licensing protocol

Hello,

Do you encounter the same issue in external mode as well?

Best regards,

Hello,

Could you try the solution proposed in the link below

https://community.spiceworks.com/how_to/84081-the-remote-computer-disconnected-the-session-because-of-an-error-in-licensing-protocol

Best regards,

Guess it would have helped if I mentioned that I had indeed tried that very fix before posting here. I'm still attempting to contact the user in question with regard to your question on external vice tabbed connections and will pass the answer along as soon as I get it. As far as I know it's only affecting this one user at present.

Hello,

After the deletion of the registry key, did you open Microsoft RDP (mstsc.exe) with elevated privileges?

What version of Windows are you running?

Best regards,

Hi,
We are getting the exact same error with a single user. The error occurs only when the session type is "Embedded" regardless of the user privilege on the target machine, when using "External" session type, it works without problem.
We will try the proposed solution tomorrow and keep you informed about the results.
Regards

Okay. Finally able to get my client to test an external session and it worked just fine. So my next step will be to go there myself and run the fix, just in case they messed something up when they implemented it. I'll report back once I have run it and tested it myself.

Unfortunately, on our side the proposed solution is not working. I'll continue to do some investigation and report my findings if I get the issue resolved.

Regards

Could you verify if you have Network Level Authentication (NLA) check?

http://help.remotedesktopmanager.com/troubleshooting_automaticlogon.htm

On our side, the NLA option was not checked so I asked to check it and try again an embedded session type and the user is getting the exact same error message about licensing protocol.

Everyone in our team is using RDP Manager but this issue is hapening only for a single user and only for embedded session type.

I checked the applied GPOs on the target machine and nothing is configured to force explicit credential or NLA.

Sorry, I don't want to hijack this thread ... should I open a new one or I should continue to send updates on this one ?

Regards

Hello Sebastien,

Have you tried the solution proposed in this link?
https://community.spiceworks.com/how_to/84081-the-remote-computer-disconnected-the-session-because-of-an-error-in-licensing-protocol

After the deletion of the registry key, did you open Microsoft RDP (mstsc.exe) with elevated privileges?

Best regards,

Hi Jean-François,
Yes we we tried the proposed solution and tried to launch mstsc.exe with admin rights a single time but while reading another article proposing the same solution, I saw that a reboot is maybe required after the registry key deletion.

So I will try to find a timeframe on tomorrow morning to test that with the client and to test too if checking the "admin/console" mode helps to permit RDP in embedded session type.

Regards

Hello,

We've been having the same issue with multiple machines occasionally encountering the same issue here. All users are running Windows 7 with Admin rights removed from their EU accounts.

The pop up window with the "The remote computer disconnected the session because of an error in the licensing protocol. Please try connecting to the remote computer again or contact your server administrator." message is shown.

Our quick fix is to close the program, switch to the admin account, run Remote Desktop Manager from the admin (ensuring connections are made, which always are with no issues), log off, log back in to the user account, and run RDM which should at this point run fine. This quick fix will last a couple of weeks before needing to be repeated.

Any help would be greatly appreciated. Thanks.

Hello Tyrone,

Have you tried the solution proposed in this link?
https://community.spiceworks.com/how_to/84081-the-remote-computer-disconnected-the-session-because-of-an-error-in-licensing-protocol

Best regards,

Hello Mr. Jean-François, I will try the suggested registry edit and let you know how it goes. Thank you.

Hi Devolutions Support,
I have the same problem. But only if connect to a Terminalserver which have RDS Application mode active to host more than 2 admin session.

If I use external or direct mstsc I have no issues. If I start RDPManager with "Admin Rights" it works also fine. Only If I start it in user mode I get the License error. Can you help me with that?

I tried suggested link to renew RDP License but without success.

Thanks
Tom

@Tom

After several researches, it's look like there's 2 registry keys that needs to be deleted to resolve this licensing protocol issue:

HKEY_LOCAL_MACHINE\SOFTWARE\Microsoft\MSLicensing and HKEY_LOCAL_MACHINE\SOFTWARE\Wow6432Node\Microsoft\MSLicensing



Could you try to delete both keys and run Microsoft RDP (mstsc.exe) as an administrator to recreate them.



Best regards,

Not helped. I don't think that this help because external it works fine. But I tried and it dosn't help. Not sure why it works when I start RDPManager with Admin rights. But looks like that we have to focus at this direction.

Do you use RDM 32 or 64 bit?

32 bit

Could you give a try to RDM 64bit? It's installed by default and the executable is RemoteDesktopManager64.exe

Regards

Helped!

Thanks David :-)

You may should fix that at the 32bit version was really annoying.

Regards
Tom

It's the same code base but one is using the 64bit ActiveX from Microsoft. I suspect that an RDP is not correctly installed in 32bit

Regards

Hello,

I encounter the very same problem with the free version. However, I cannot find any RemoteDesktopManager64.exe alongside the 32bits version. How can I fix that?

Regards,
Py

Hi,
RDM free does not have 64bit version. You can enable the large memory aware:

http://help.remotedesktopmanager.com/troubleshooting_largememoryawa.htm

Regards

Hi,

Thanks for your answer. However, I asked about the 64-bits version because it appears to be the workaround about the licensing problems described in this thread, not at all because I need to allocate more memory to the program.

So the general question is: how do I solve this exact same licensing problem with the free version? Using the native windows client, it works nicely. Only inside of RDM does it fail.

Thanks in advance!
Py

Hello,

Have you tried to delete the appropriate registry key like proposed in this help topic?
http://help.remotedesktopmanager.com/troubleshooting_licensingprotocolerror.htm

Best regards,

Hello,

I did it once again, and this time it worked! What is strange is that it never stopped working with the native windows client, which is using the same registry key for it's licence. Weird.

Anyway, thanks for your help and excellent piece of software.

Best regards,
Py