- Remove From My Forums
-
Question
-
I have a problem.
I can connect to server via MSTSC /v:, but I can’t connect via RDCM.
I receive error 3334.
I can connect to other servers in my network.
Version od RDCM is 2.2 build 2.426
-
Edited by
pTomic
Wednesday, May 28, 2014 5:31 AM
-
Edited by
Answers
-
-
Marked as answer by
pTomic
Thursday, May 29, 2014 6:34 AM
-
Marked as answer by
All replies
-
-
Marked as answer by
pTomic
Thursday, May 29, 2014 6:34 AM
-
Marked as answer by
-
I’ve got this error when I try to connect too many servers.
Maybe you have reached limit?
-
Thanks, this solved my problem on Win 8.1!
-
I also see this error after connecting to 5-10 servers (2012+2012R2) from my Windows 8.1. Closing the application and reopening it fixes the problem albeit only temporarily.
I hope that the limit problem will be fixed in a future version — if there will ever be one.
Version of RDCM is 2.2 build 2.426
Tore Østergaard
Oticon A/S, Denmark -
-
Proposed as answer by
matt_will_fix_it
Thursday, November 27, 2014 7:58 PM
-
Proposed as answer by
-
Didn’t help — still getting Error 3334 after running this. Can continue on using regular RDP, but not RDCM
-
In case it helps someone, I have a brand new dedicated server, windows 2012 R2.
Following the build I connected via RDP from my windows 8.1 desktop, no special settings and straight in.
118 windows updates needed to be installed and the server was rebooted.
I could then not connect back to the server using RDP on my windows 8.1 client. (mild panic and googling followed)
I resolved this on my windows 8.1 desktop by going to RDP > Advanced Settings > connect from anywhere > settings and changing the connection settings as follows;
from «Automatically detect RD gateway server settings»
to «do not use an RDP gateway server» -
It worked for me. Thanks.
-
This was the case for me, I logged off from a couple of servers and managed to log in.
-
This worked well for me thanks!
If you see Error 3334 when trying to connect to a remote server using Remote Desktop Connection Manager (RDCMan) then here is a fix you can try. This fix has been tested on Windows 8.1 64 bit machine running RDCMan 2.2. In some posts i read that by setting the No Authentication Required to Transaction Manager Communication you can get it work. But i am not very convinced with anything that opens any security loop holes.
[leaderad]
The Problem:
RDCMan is a 32-bit application so it has a limit of 2GB of address space. So as soon as it reaches that memory limit it starts throwing error 3334. To allow the RDCMan a larger address space we use the /LARGEADDRESSAWARE flag. The /LARGEADDRESSAWARE option tells the linker that the application can handle addresses larger than 2 gigabytes.
So what is this Large Address Aware?
Large Address Aware is an executable flag that tells Windows that a program can handle more than 2 GB of memory. Why this flag exists and it’s use is something that would take a lot of time to explain. But you can read all about LargeAddressAware at your pace.
The Solution: Here is how to apply the /LARGEADDRESSAWARE flag
1. You need Visual Studio installed to use the editbin command. You can download the free Visual Studio Express for Windows Desktop to get the editbin.exe binary.
2. Run the Visual Studio Native Tools Command Prompt as Administrator. Key here is to run as Administrator.
3. Execute this command editbin /LARGEADDRESSAWARE “C:Program Files (x86)Remote Desktop Connection ManagerRDCMan.exe”
Try running RDCMan and connecting to your servers. Let me know how it goes for you.
Few other references:
http://msdn.microsoft.com/en-us/library/wz223b1z.aspx
http://support2.microsoft.com/default.aspx?scid=889654
If you enjoyed this post, please consider sharing, leaving a comment or subscribing to the RSS feed to have future articles delivered to your feed reader.
Just for your information.
Using version 1.76.20.24615 from Windows 11 and connecting to Windows 10 Pro version 1909 (whilst trying to update) or higher, disconnects with an RDP error 3334, since a few days.
The problem is the version of AxInterop.MSTSCLib.dll and Interop.MSTSCLib.dll.
Using the ones from the nightly build solves the problem.
Download the portable version and unzip.
Put them in C:Program Files (x86)mRemoteNG.
You also need to install .NET 6.0 Desktop Runtime (v6.0.3) — Windows x64 to make it work.
- Remove From My Forums
-
Question
-
I have a problem.
I can connect to server via MSTSC /v:, but I can’t connect via RDCM.
I receive error 3334.
I can connect to other servers in my network.
Version od RDCM is 2.2 build 2.426
-
Edited by
pTomic
Wednesday, May 28, 2014 5:31 AM
-
Edited by
Answers
-
-
Marked as answer by
pTomic
Thursday, May 29, 2014 6:34 AM
-
Marked as answer by
All replies
-
-
Marked as answer by
pTomic
Thursday, May 29, 2014 6:34 AM
-
Marked as answer by
-
I’ve got this error when I try to connect too many servers.
Maybe you have reached limit?
-
Thanks, this solved my problem on Win 8.1!
-
I also see this error after connecting to 5-10 servers (2012+2012R2) from my Windows 8.1. Closing the application and reopening it fixes the problem albeit only temporarily.
I hope that the limit problem will be fixed in a future version — if there will ever be one.
Version of RDCM is 2.2 build 2.426
Tore Østergaard
Oticon A/S, Denmark -
-
Proposed as answer by
matt_will_fix_it
Thursday, November 27, 2014 7:58 PM
-
Proposed as answer by
-
Didn’t help — still getting Error 3334 after running this. Can continue on using regular RDP, but not RDCM
-
In case it helps someone, I have a brand new dedicated server, windows 2012 R2.
Following the build I connected via RDP from my windows 8.1 desktop, no special settings and straight in.
118 windows updates needed to be installed and the server was rebooted.
I could then not connect back to the server using RDP on my windows 8.1 client. (mild panic and googling followed)
I resolved this on my windows 8.1 desktop by going to RDP > Advanced Settings > connect from anywhere > settings and changing the connection settings as follows;
from «Automatically detect RD gateway server settings»
to «do not use an RDP gateway server» -
It worked for me. Thanks.
-
This was the case for me, I logged off from a couple of servers and managed to log in.
-
This worked well for me thanks!
Thread Rating:
- 0 Vote(s) — 0 Average
- 1
- 2
- 3
- 4
- 5
|
Error message 3334 using RDP connection |
|
Posts: 2 Reputation: 0
I’ve configured multiple connections to several servers. One of the connections returns an error while connecting: Protocol error 3334. The same software is installed on another computer, without any connection problems. Platform: Windows 7. Visionapp Remote Desktop. Anyone any idea?
Posts: 1,150 Reputation: 2 Hi, are you sure, that the error number is 3334, because web search returns is no result when searching for it?
Posts: 2 Reputation: 0
Thanks for your reaction. I had the same problem not finding any information about this one. If there’s any suggestion, please let me know.
Posts: 1,150 Reputation: 2 16-02-2010, 06:05 PM Hi Lennard, did you check if this problem also occurs, when using the RDP client itself? And is anything else reported in Windows eventlog?
Posts: 1 Reputation: 0 02-03-2010, 04:41 AM Hi Thomas, I am having the same issue, and can advise that on my PC (Win 7, 64bit), I also cannot connect using the built in RDP either. We connect to approx 60 Servers, and to date I have this issue on 2 of them. All the Servers we connect to are done via VPN. I’m sure that it is a Windows issue, rather than a VisionApp one, but it’s hard to know what is configured differently on these two problem servers. I’ve researched this a fair bit, and there is talk of changing some DLL’s to the Vista versions, but hell will freeze over before I go to those lengths! Cheers Steve
Posts: 1,150 Reputation: 2 Hi Steve, thanky a lot for your feedback. When you say, that you are not able to use RDP itself either, then indeed it is a Windows issue. But I have no clue, what it might be. Maybe some security restriction?
Posts: 1 Reputation: 0 G’day all, I am having the same issue as this. I can RDP fine into all of my servers, but when I try and take over a session of a user whilst RDP in it kicks me out with the same error 3334. I have tried Googleing it with no luck and thought I would post here as I am a customer of this product. It seems to only happen to sessions I take over from Wyse Thin Clients running RDP 5.2 (or is it 6? The latest version). I can take over sessions fine that come from Windows XP machines into the terminal servers. Running Windows 7 (but does the same on another Windows XP Pro machine) and Visionapp 2010 R2. Help! Thanks S
Posts: 1 Reputation: 0
I encountered this issue first time today. I’m running VisionApp remote desktop 2010 on a windows 7 client. The problem occurred when I tried to connect to a VMware virtual server after setting up the Remote app Role on Windows 2008 R2 (previously known as Terminal server).
Posts: 2 Reputation: 0
I have this problem too, sometimes several times a day.
Posts: 4 Reputation: 0 I have been dealing with this issue for quite a while, but my workaround is starting to become very inconvenient. This is not a Windows issue because:
This IS a VRD issue because:
My Workstation: Connecting to 8 (Windows 7) and 22 (Windows 8.1) virtual workstations hosted on 2 (Windows Server 2012) running Hyper-V Attached Files Thumbnail(s)
Posts: 1 Reputation: 0 This issue started appearing today for us and I have to agree that this is not a Windows issue as listed above by Jbenz: *There are no event log errors. My Workstation: Connecting to Windows Server 2012 R2 All Windows patches have been applied as of this date to all servers and workstation connecting via or from VisionApp We are running VisionApp 7.0.3265.0 with a SQL 2008R2 DB Attached Files Thumbnail(s)
Posts: 22 Reputation: 0 We are having the same issue. I notice this more when connecting to servers running Windows Serve 2012 R2. I can connect fine with RDP
Posts: 1 Reputation: 0 Yes I have this issue also, running 201 version 6.5.2806.0 Very annoying and definitely getting worse. Doesn’t seem to be a specific number of hosts before it starts rejecting. I have to exist sessions to be able to open new ones. Surprised/disappointed at no vendor input since this issue was a logged several years ago now Probably not worth of an upgrade unless support improves…
Posts: 458 Reputation: 0 25-02-2015, 01:45 PM I have the same error running vRD 2011 (7.0.3328.0). No problem with mstsc.exe — but with visionApp it seems I can only connect to three (3) W2K12R2 servers at a time. Connecting to any 4th W2K12R2 server throws the 3334 error. Logoff one of the W2K12R2 sessiosn and I can log on to the one that couldn’t logon before… And I can continously both before, during and after continue to log on to any number of W2K8 servers. Weird!!! And agree about the support. It used to be fast and great followed by fixes. After ASG took over (or around that time anyway) the forum support stopped, so after many unanswered posts I too stopped trying to get replies and just plain stopped visiting the forums. Don’t know if it has improved in other threads since then, but didn’t get this 3334 problem until now.
Posts: 9,875 Reputation: 154 I don’t know if the problem still exists with the latest version — but vRD 2011 is quite old, not the current RDP-protocol implemented so we can’t support such issues…
Regards/Gruss
Posts: 2 Reputation: 0 Hi DevOma We got tha same issue with 2012 Version: 7.2.3955.0 When the error occurs, we have to restart the whole application (ASG). Maybe after 2h you need another server…. Error 3334….. Normally I had to restart ASG 3-4 times a day! It’s definitly annoying..
Posts: 9,875 Reputation: 154 We have implemented a new setting in version 2015 that should solve this issue…
Regards/Gruss
Posts: 2 Reputation: 0 Hi DevOma Thank You for your fast reply. Greetings |
Users browsing this thread: 2 Guest(s)
CredSSP — CVE-2018-0886 — Authentication error¶
mRemoteNG uses the Microsoft Terminal Services Client (MSTSC) libraries
in order to make Remote Desktop connections.
Note
mRemoteNG has no control over the functionality changes implemented by Microsoft.
Please refer to Microsoft’s Documentation for full details regarding this problem.
Patched clients attempting to connect to Unpatched servers will fail with the following error:
The same error will occur with MSTSC directly on a patched
client attempting to connect to an unpatched server.
Per the MS documentation, the only way around this is to do the following:
- Patch the servers
- set the “Encryption Oracle Remediation” policy to “Vulnerable” — refer to the MS documentation above for details:
- Uninstall KB4103727
Log4net vulnerability CVE-2018-1285¶
Log4Net is an external library on which mRepoteNG application relies on. While the nightly builds are using the latest version of log4net that do not have the CVE-2018-1285 vulnerability, older releases require manual patching.
- Download latest version of log4net from apache.org — currently is v2.0.15
- Copy log4net.dll from net40 folder into mRemoteNG install folder (default C:Program Files (x86)mRemoteNG )
- Edit mRemoteNG.exe.config and add the following section under the assembly binding for
WeifenLuo.WinFormsUI.Docking
<assemblyBinding xmlns="urn:schemas-microsoft-com:asm.v1"> <dependentAssembly> <assemblyIdentity name="log4net" publicKeyToken="669e0ddf0bb1aa2a" culture="neutral"/> <bindingRedirect oldVersion="2.0.8.0-2.0.15.0" newVersion="2.0.15.0"/> </dependentAssembly> </assemblyBinding>
Make sure the newer log4net version in the
bindingRedirectsection of mRemoteNG.exe.config file matches the version of the log4net.dll copied over at step #2. Please refer to Microsoft documentation for more details related to assembly binding in .NET applications.
I can’t open more than X number of RDP sessions. New sessions fail with error code 3334¶
The issue here is likely the amount of resources available to the RDP component to open the connection. This was alleviated in MR-714 and MR-864
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.
RDP connections fail with error code 264¶
This issue is often caused by trying to retrieve session information.
Try doing the following:
- Disable “Automatically get session information” (Tools -> Options -> Advanced)
mRemoteNG crashes with the error “Class not registered” when trying to connect using RDP¶
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.
- 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:
— Uninstall KB2592687
— Install KB2574819
— (Re)Install KB2592687
— Reboot your machine
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).
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.”¶
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.
Unfortunately, the only way around this limitation is to use an open source
implementation of VNC server such as TightVNC
or UltraVNC
Cannot click some UI elements in an RDP connection window.¶
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 items is all the way to the left (at 100%)
SSH login fails when password contains extended ASCII characters¶
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.
RDP tries to reconnect whenever I resize the window¶
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:
- Resolution: Fit to Panel
- Automatic Resize: Yes
To prevent reconnecting, you can do one of several things:
- Change RDP Version to Rdc9 or higher. Rdc9 supports resolution changes without reconnecting.
- 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 in RDP Version lower than Rdc9.
This is an RDP protocol limitation.
AltGr key combinations stop working in other apps when connected to RDP¶
When connected to an RDP session AltGr, keyboard combinations sometimes stop working.
This is a known issue with The Microsoft RDP library that cannot be solved by mRemoteNG.
There are three known work arounds for this issue:
- Disconnect the RDP session which caused the issue. Since it can be difficult to determine which connection is to blame, you may need to disconnect all RDP sessions. Once you have confirmed AltGr combinations are working again, you may reconnect your RDP session(s).
- When the issue occurs, hold/press the Ctrl key. This is known to release the AltGr key from the RDP session.
- Use Ctrl + Alt instead of AltGr.
Step 1 – Solve Mstsc Error 3334
Is Mstsc Error 3334 appearing? Would you like to safely and quickly eliminate remote desktop connection which additionally can lead to a blue screen of death?
When you manually edit your Windows Registry trying to take away the invalid remote desktop connection manager v2.2 error 3334 keys you’re taking a authentic chance. Unless you’ve got been adequately trained and experienced you’re in danger of disabling your computer system from working at all. You could bring about irreversible injury to your whole operating system. As very little as just 1 misplaced comma can preserve your Pc from even booting every one of the way by!
Troubleshooting disconnected from server error 3334 Windows XP, Vista, 7, 8 & 10
Simply because this chance is so higher, we hugely suggest that you make use of a trusted registry cleaner plan like CCleaner (Microsoft Gold Partner Licensed). This system will scan and then fix any Mstsc Error 3334 complications.
Registry cleaners automate the entire procedure of finding invalid registry entries and missing file references (including the 3334 error) likewise as any broken hyperlinks inside of your registry.
Issue with remote desktop error 3334 server 2012
Backups are made immediately prior to each and every scan providing you with the choice of undoing any changes with just one click. This protects you against doable damaging your pc. Another advantage to these registry cleaners is that repaired registry errors will strengthen the speed and performance of one’s procedure drastically.
- http://www.coderewind.com/2014/10/solution-rdcman-error-3334-remote-desktop-manager/
- https://www.batchworks.de/fix-rdp-error-3334-in-mremoteng-and-others/
- http://www.keytosmart.com/problem-remote-desktop-connection-manager-error-3334/
- http://shawn.meunier.com/
Cautionary Note: Yet again, for those who are not an state-of-the-art consumer it’s very encouraged that you simply refrain from editing your Windows Registry manually. If you make even the smallest error within the Registry Editor it can result in you some serious issues that may even call for a brand new set up of Windows. Not all difficulties attributable to incorrect Registry Editor use are solvable.
Fixed: devolutions rdm
Symptoms of Mstsc Error 3334
“Mstsc Error 3334” appears and crashes the energetic method window.
Your Personal computer routinely crashes with Mstsc Error 3334 when running the exact same system.
“Mstsc Error 3334” is shown.
Windows operates sluggishly and responds little by little to mouse or keyboard input.
Your computer periodically “freezes” for the number of seconds in a time.
Will cause of Mstsc Error 3334
Corrupt obtain or incomplete set up of Windows Operating System software program.
Corruption in Windows registry from a new Windows Operating System-related application adjust (install or uninstall).
Virus or malware infection which has corrupted Windows method documents or Windows Operating System-related application data files.
Another method maliciously or mistakenly deleted Windows Operating System-related files.
Mistakes this sort of as “Mstsc Error 3334” can be brought about by several different elements, so it really is important that you troubleshoot every of the achievable brings about to forestall it from recurring.
Simply click the beginning button.
Variety “command” inside the lookup box… Will not hit ENTER nonetheless!
Although keeping CTRL-Shift in your keyboard, hit ENTER.
You’re going to be prompted that has a authorization dialog box.
Click on Of course.
A black box will open having a blinking cursor.
Variety “regedit” and hit ENTER.
Within the Registry Editor, choose the remote desktop connection manager v2.2 error 3334 connected key (eg. Windows Operating System) you wish to back again up.
Within the File menu, choose Export.
Inside the Preserve In list, pick out the folder in which you wish to save the Windows Operating System backup key.
Inside the File Title box, sort a reputation for the backup file, these types of as “Windows Operating System Backup”.
From the Export Vary box, ensure that “Selected branch” is selected.
Click on Help you save.
The file is then saved by using a .reg file extension.
You now use a backup within your disconnected from server error 3334 related registry entry.
Solution to your remote desktop connection manager download problem
There are actually some manual registry editing measures that can not be talked about in this article due to the high chance involved for your laptop or computer method. If you want to understand more then check out the links below.
Additional Measures:
One. Conduct a Thorough Malware Scan
There’s a probability the 3334 Error Mstsc error is relevant to some variety of walware infection. These infections are malicious and ready to corrupt or damage and possibly even delete your ActiveX Control Error files. Also, it’s attainable that your Mstsc Error 3334 is actually connected to some element of that malicious plan itself.
2. Clean mremoteng Disk Cleanup
The a lot more you employ your computer the extra it accumulates junk files. This comes from surfing, downloading packages, and any sort of usual computer system use. When you don’t clean the junk out occasionally and keep your program clean, it could turn into clogged and respond slowly. That is when you can encounter an Error error because of possible conflicts or from overloading your hard drive.
Once you clean up these types of files using Disk Cleanup it could not just remedy Mstsc Error 3334, but could also create a dramatic change in the computer’s efficiency.
Tip: While ‘Disk Cleanup’ is definitely an excellent built-in tool, it even now will not completely clean up Error 3334 discovered on your PC. There are numerous programs like Chrome, Firefox, Microsoft Office and more, that cannot be cleaned with ‘Disk Cleanup’.
Since the Disk Cleanup on Windows has its shortcomings it is extremely encouraged that you use a specialized sort of challenging drive cleanup and privacy safety application like CCleaner. This system can clean up your full pc. If you run this plan after each day (it could be set up to run instantly) you are able to be assured that your Pc is generally clean, often operating speedy, and always absolutely free of any 3334 error associated with your temporary files.
How Disk Cleanup can help visual studio express
1. Click your ‘Start’ Button.
2. Style ‘Command’ into your search box. (no ‘enter’ yet)
3. When holding down in your ‘CTRL-SHIFT’ important go ahead and hit ‘Enter’.
4. You will see a ‘permission dialogue’ box.
5. Click ‘Yes’
6. You will see a black box open up plus a blinking cursor.
7. Variety in ‘cleanmgr’. Hit ‘Enter’.
8. Now Disk Cleanup will start calculating the amount of occupied disk space you will be able to reclaim.
9. Now a ‘Disk Cleanup dialogue box’ seems. There will be a series of checkboxes for you personally to pick. Generally it will likely be the ‘Temporary Files’ that consider up the vast majority of your disk area.
10. Verify the boxes that you want cleaned. Click ‘OK’.
How to repair
3. System Restore can also be a worthwhile device if you ever get stuck and just desire to get back to a time when your computer system was working ideal. It will work without affecting your pics, paperwork, or other crucial information. You can discover this option with your User interface.
Error 3334
Manufacturer
Device
Operating System
Mstsc Error 3334
5 out of
5
based on
54 ratings.