Join GitHub today
GitHub is home to over 28 million developers working together to host and review code, manage projects, and build software together.Sign up
This page is meant to be a collection of common questions, odd quirks, and known issues that you may experience when using mRemoteNG.
If your question is not covered here, you can also check the following places:
Table of Contents
- I can't open more than X number of RDP sessions. New sessions fail with error code 3334
- RDP connections fail with error code 264
- ATI Tray Tools
- mRemoteNG crashes with the error "Class not registered" when trying to connect using RDP
- VNC connections fail with the error "The server is using an unsupported version of the RFB protocol. The server is using version 4.1 but only version 3.x is supported."
- Cannot click some UI elements in an RDP connection window
- SSH login fails when password contains extended ASCII characters
- RDP Reconnects whenever I resize the window
Other things you can do to help reduce the issue:
- On your RDP connections, set CacheBitmaps to False (this reduces the memory usage of each connection)
- Consider removing KB2830477 if you have it installed. This seems to increase the likelyhood of getting 3334 error codes.
This issue is often caused by trying to retrieve session information.
Try doing the following:
- Disable "Automatically get session information" (Tools -> Options -> Advanced)
mRemoteNG is not compatible with ATI Tray Tools. We are aware of the issue and hope to have it fixed in a future version. We recommend that you disable or uninstall ATI Tray Tools while using mRemoteNG.
You may also see a message like "System.Runtime.InteropServices.COMException (0x80040154)"
If you are running mRemoteNG on Windows 7 or Server 2008:
- You may be missing one or more required windows updates (see the page on Prerequisites).
- A common issue is that KB2574819 is either missing or has been installed after KB2592687. They must be installed in the correct order. If you do not have KB2574819, follow these instructions:
If you are running mRemoteNG on Windows 8/10 or Server 2012+:
- Try to repair the mRemoteNG installation using the installer or uninstall/reinstall. Receiving this error on these OS's is just an install fluke (or you've fiddled with your registry).
RFB version 4.0 and higher is a proprietary version owned by RealVNC Limited. Building support for newer versions will likely result in licensing fees. Therefore, it is unlikely that mRemoteNG will have support for version 4.0+ anytime soon.
It may seem like some elements are not clickable along the top and left sides of your RDP connection window. More information can be found in issue #210
This is likely due to non-standard (>100%) DPI scaling on your local machine.
To turn this off:
On Windows 7 / 8
- Start menu -> Control Panel -> Display
- Ensure the option
Smaller - 100% (default)is selected
On Windows 10
- Start menu -> Settings -> Display
- Ensure the slider under
Change the size of text, apps, and other itemsis all the way to the left (at 100%)
Initial login to SSH (or WinSCP) fails when the password contains extended ASCII characters (such as: €šœ£ÁØë). Typing the password into the SSH session directly works.
Investigation suggests that there is an issue in character encoding when mRemoteNG passes the value to the cmd line, which then invokes PuTTY. This was investigated in issue #186
The only resolution for this issue is to not use extended ASCII characters in passwords that will be sent to PuTTY or similar tools.
Your RDP connection reconnects after resizing mRemoteNG or the connection panel.
This will occur anytime the connection window changes size and the following connection options are set:
Fit to Panel
- Automatic Resize:
To prevent reconnecting, you can do one of several things:
- Change the resolution to
Smart Size. This will scale the original connection area when the view window size changes. This does not preserve aspect ratio.
- Turn off
Automatic Resize. When the view window size changes, you will see scroll bars or dead space.
There is no way to update the view window size without a reconnect. This is an RDP protocol limitation.