Remote desktop connection protocol error 0x112f

When I try to connect to Windows 2012 Server using Remote Desktop Connection, I'm connected for about 1 sec. and then disconnected with following error:

> Because of a protocol error (code: 0x112f), the remote session will be disconnected.

Until yesterday, connection was working fine with no error, no server changes. I never saw this error before. I tried to lower visual appearance settings in Experience panel (found as possible solution to similar error), but with no result.

This error may be triggered by insufficient memory on RDP server.

After few tries with this error, RDP managed to get a connection to the server and I was able to stop a bogus service consuming too much memory. This can be done also with sysinternals or sc.

Might not be a solution for all but I found that if I reduced the screen resolution of the RDP session, I was able to get in. The server was at 95% capacity I went from 3 high res monitors to 1 800x600 window.

Server restart helped, I'm able to connect to server again.

If the server accessible with RPC (basically, if you can access a shared folder on it), you could free some memory and thus let the RDP service work properly. The following windows native commands can be used:

To get the list of memory consuming tasks:

tasklist /S <remote_server> /V /FI "MEMUSAGE gt 10000"

To kill a task by its name:

taskkill /S <remote_server> /IM <process_image_name> /F

To show the list of desktop sessions:

qwinsta.exe /SERVER:<remote_server>

To close an old abandoned desktop session:

logoff <session_id> /SERVER:<remote_server> 

After some memory is freed, the RDP should start working.

A simple thing. Disable the vsphere options 3D for the virtual maschine . It works perfect. When you want, reinstall the vm-tools for the virtual maschine.

Resized VM with more memory fixed this issue.

I got the same error recently. I think McX is right it was caused by insufficient memory on RDP server. Here is the solution that works for us.

1. use sc cmd to get running services on the remote server. Make sure you can use windows explorer to access the remote server \\remote_server. > sc \\<remote_server> query

2. find out the service you can stop. > sc \\<remote_server> stop <service_name>

After stopping one service, the remote desktop works again.

If anyone comes to this thread and has this issue when you remote to a VMware VM with windows 10 1903, disabling 3d in the graphics card worked for me.

There may be a problem with the video adapter. At least that's what I had. I picked up problems immediately after updating Windows 10 to the 2004 version. Disabling hardware graphics — solved the problem.

https://www.reddit.com/r/sysadmin/comments/gz6chp/rdp_issues_on_2004_update/