Thread Rating:
  • 0 Vote(s) - 0 Average
  • 1
  • 2
  • 3
  • 4
  • 5
Error message 3334 using RDP connection
#1
I've configured multiple connections to several servers. One of the connections returns an error while connecting: Protocol error 3334.
After closing the messsage, also the RDP session is closed.

The same software is installed on another computer, without any connection problems.

Platform: Windows 7. Visionapp Remote Desktop.

Anyone any idea?
Reply
#2
Hi,

are you sure, that the error number is 3334, because web search returns is no result when searching for it?
Grüße/Regards

Thomas
Reply
#3
Thanks for your reaction. I had the same problem not finding any information about this one.
The exact message is: The remote computer "<servername>" returned an RDP protocol error (Return code: 3334). The only option is a button <OK>.

If there's any suggestion, please let me know.
Reply
#4
Hi Lennard,

did you check if this problem also occurs, when using the RDP client itself? And is anything else reported in Windows eventlog?
Grüße/Regards

Thomas
Reply
#5
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
Reply
#6
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?
Grüße/Regards

Thomas
Reply
#7
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
Reply
#8
drnick Wrote: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

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).
I can still connect through the Vmware Console view though.
Reply
#9
I have this problem too, sometimes several times a day.
Usually it appears out of sudden and affects connections to Server 2012/2012R2/Win8. It won't let me connect until I restart vRD.
This gets pretty annoying,
Reply
#10
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:
  • There are no event log errors.
  • The issue only occurs in VRD.
  • I Can Connect to ALL 30 of my virtual test environments through the windows RDP client without the error.

This IS a VRD issue because:
  • The error occurs when a maximum number of RDP connections is made through a single VRD window/process.
  • The number of connections that can be opened without this error in one VRD window/process has decreased over time for me from 8 to 3.
  • I can connect to all 30 of my virtual machines, BUT VRD requires that open a new VRD window/process for every 3 connections.

My Workstation:
Windows 7 SP 1 Enterprise
Processor: Intel ® Xeon® EPU E5-16500 0@ 3.20GHz 32.0 GHz
Installed memory (RAM): 16.0 GB
System Type: 64-bit Operating System

Connecting to 8 (Windows 7) and 22 (Windows 8.1) virtual workstations hosted on 2 (Windows Server 2012) running Hyper-V


Attached Files
.png   screenshot.png (Size: 10.44 KB / Downloads: 768)
Reply
#11
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.
*The issue only occurs in VRD.
*I Can Connect to ALL my virtual test environments through the windows RDP client without the error.


My Workstation:
Windows 8.1 Update 1 Enterprise
Processor: Intel ® Xeon® E5-2643 0@ 3.30GHz
Installed memory (RAM): 16.0 GB
System Type: 64-bit Operating System

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
.jpg   VisionApp Error.jpg (Size: 32.18 KB / Downloads: 743)
Reply
#12
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
Reply
#13
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 Sad

Probably not worth of an upgrade unless support improves...
Reply
#14
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.
Reply
#15
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
Oliver
Reply
#16
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).
After that, you have to reconnect to all your server you need..

Maybe after 2h you need another server.... Error 3334.....

Normally I had to restart ASG 3-4 times a day!

It's definitly annoying..
Reply
#17
We have implemented a new setting in version 2015 that should solve this issue...
Regards/Gruss
Oliver
Reply
#18
Hi DevOma

Thank You for your fast reply.
We will upgrade as soon as possible. Afterwards I will give a short feedback.

Greetings
Reply




Users browsing this thread: 2 Guest(s)