RDP Sessions fail after opening like 8 or 10 sessions. have to close MRemoteNG in order to be able to connect again

[ptfxnz]

I am using the PREVIEW version 1.77.1.27713 and i noticed that after i have opened around 8 to 10 RDP sessions, if i try to open another RDP session, it fails. in order to be able to connect using RDP again i have to close MRemoteNG and then RDP starts to work again.

Thank you.

Expected Behavior

Current Behavior

Possible Solution

Steps to Reproduce (for bugs)

1. Start 10 RDP sessions
2. Try to start another RDP session
3. RDP session fails
4. Close MRemoteNG and start again and resume RDP sessions and it works again; open too many and have to close and restart again

Context

Your Environment

• Version used:
• Operating System and version (e.g. Windows 10 1709 x64):

Windows version 21H2 build 22000.376

[Kvarkas]

hi, yes known issue, its limitation of rdp protocol for some reasons, we will have a look soon if its possible to fix from our end

[ptfxnz]

Dimitrij

Thank you for the update

Regards P

17/12/2021 23:16:58 Dimitrij @.***>:

hi, yes known issue, its limitation of rdp protocol for some reasons, we will have a look soon if its possible to fix from our end

— Reply to this email directly, view it on GitHub[https://github.com/mRemoteNG/mRemoteNG/issues/2090#issuecomment-996601499], or unsubscribe[https://github.com/notifications/unsubscribe-auth/AW6OH2YT765DFAFBFIGMSIDURMEZVANCNFSM5KHJC7RQ]. Triage notifications on the go with GitHub Mobile for iOS[https://apps.apple.com/app/apple-store/id1477376905?ct=notification-email&mt=8&pt=524675] or Android[https://play.google.com/store/apps/details?id=com.github.android&referrer=utm_campaign%3Dnotification-email%26utm_medium%3Demail%26utm_source%3Dgithub]. You are receiving this because you authored the thread. [data:image/png;base64,iVBORw0KGgoAAAANSUhEUgAAACoAAAAqCAYAAADFw8lbAAAAAXNSR0IArs4c6QAAAARzQklUCAgICHwIZIgAAAAeSURBVFiF7cExAQAAAMKg9U9tDB+gAAAAAAAAgL8BG7oAAVIlbSwAAAAASUVORK5CYII=###24x24:true###][Tracking image][https://github.com/notifications/beacon/AW6OH2524JINL7M7A3QK2X3URMEZVA5CNFSM5KHJC7R2YY3PNVWWK3TUL52HS4DFVREXG43VMVBW63LNMVXHJKTDN5WW2ZLOORPWSZGOHNTO5GY.gif]

[darkpixel]

I just ran into this with 1.77.1.27654. I'm going to try downgrading to the previous stable release.

[darkpixel]

I tested using the stable version and ran into the same issue. I then upgraded to the nightly build and it seems to work. I'm not sure why some of our users are suddenly affected by it while others aren't. They all run the same desktop hardware and software, and we haven't made any changes to our server environments. If I had to guess, it's a Windows Update lurking somewhere that broke things for some Windows 10 workstations.

[simonai1254]

Are you running into a memory limitation?

[darkpixel]

There is plenty of free memory on the servers, and my test workstation has 128 GB RAM. ;)

One of our techs while troubleshooting mentioned a message in mRemote about memory but when checking the workstation there was plenty free.

The issue started this morning after a round of Windows Updates were deployed last night, so I'm suspecting Microsoft messed something up....regardless, the mRemote nightly build doesn't seem to suffer from the issue...but I will admit we haven't done a lot of testing in the last ~30 minutes. We're deploying it to one affected user in about 30 minutes and will report back.

[darkpixel]

The nightly build fixed the issue for the user that was having problems.

[simonai1254]

mRemoteNG versions before 1.77.2 were 32bit (x86), which limits the usable memory to 4 GB. Depending on the screen resolution you used the RDP sessions consumed all memory available and you could not start additional sessions. (Run into a similar issue though with a higher number of connections).

I assume this is the same thing as with issue #1715, #854, #864 and #910, which all got solved with the x64 Build of this Software (see #915).