These are then available for re-use by down-level RDP clients. No errors pop up in the eventlog on the old Citrix server tho. I have not received an RDP error connecting to any of my TS sessions created by Wyse thin clients. If I do the same on the Server 2003 users all works fine. navigate here
sysWOW64 (Windows 32bit On Windows 64bit) is where the 32 files are found. I therefore hypothesize that it seems to be a problem in the client (or the accessing of the client by Citrix as it offers the app up for the users) itself The hotfixhttp://support.microsoft.com/kb/2523307works great for windows 2008, but _not_ for 2008 R2. So it looks like I need to tweak a policy to get this working...
Have you tested it? Client is fine. I can connect normally to a Windows 2003 non-Citrix machine.
Not 100% solved yet, but looks like we're closing in on 100% rapidly :) 1317-315687-1690548 Back to top Pavan nannapaneni Members #11 Pavan nannapaneni 1,041 posts Posted 20 November 2012 - Tuesday, August 09, 2011 1:03 PM Reply | Quote 0 Sign in to vote I believe you need to have Server 2008 SP2 loaded on the server side - not just In our case the Citrix machines that the user launches the Remote Desktop application on. Because Of A Protocol Error This Session Will Be Disconnected Windows 10 Since we're using an image, these keys are inherently empty, and should be filled with the appropriate license as logons occur.
What's weird tho, is that a connection was made, but nothing was placed under the MSLicensing keys, and no permission alterations were made.So I then tried connecting as the user to Remote Desktop Protocol Error 0x112f And I'm happy to report that it looks like success has been achieved. Wednesday, August 11, 2010 7:47 AM Reply | Quote 0 Sign in to vote Hi, Wyse has a KB document that says to upgrade thin client OS firmware to at least http://help.remotedesktopmanager.com/troubleshooting_protocolerror.htm I use Win 7 64 Bit Pro - I have updated this to SP1 My issue is that before loading SP1 on the Win 7 PC I had the protocol error
Windows Server 2008 R2 1. Because Of A Protocol Error This Session Will Be Disconnected Server 2008 R2 Connect from a PC using Remote Desktop Client version 6.0.6001 or 6.0.6002 to the server, logon as the test user8. Set this using GP. van Doornik 17 posts Posted 06 November 2012 - 08:17 AM Nobody having any ideas here? :( 1317-315687-1686397 Back to top Bogdan Stanciu Members #4 Bogdan Stanciu 21 posts Posted 09
I tried this with using the RD Gateway server set to Automatic and set to Do not use. Please could anyone help. Because Of A Protocol Error This Session Will Be Disconnected Windows 7 Thursday, March 10, 2011 11:37 PM Reply | Quote 0 Sign in to vote I'm in the exact same boat as flyingkiwi. Because Of A Protocol Error Detected At The Client (code 0x1104) This Session Will Be Disconnected please try connecting to remote computer again Hi, When i remote desktop to a terminal server from windows 7 RC and run terminal services manager and remote control a terminal server
Tech Journey Follow @TechJourneyNet Subscribe to Blog via Email Enter your email address to subscribe to this blog and receive notifications of new posts by email. http://supercgis.com/protocol-error/remote-control-protocol-error-terminal-server.html share|improve this answer answered Mar 4 '11 at 19:11 Regent 418179 Thank you! Windows Forum Windows 7 Forums > Windows 7 Help and Support > Home Forum Archives About Subscribe Network Steve Technology Tips and News because of a protocol error this session will Below are instructions for making the change to the local group policy; if preferred you can use a domain group policy instead.Windows Server 2008 R21. Because Of A Protocol Error The Client Could Not Connect To The Remote Computer
I would like to know if microsoft is aware and looking into fixing this issue. I should get back to this issue before the workday is done :) 1317-315687-1690556 Back to top Pavan nannapaneni Members #16 Pavan nannapaneni 1,041 posts Posted 20 November 2012 - 01:31 Thursday, May 13, 2010 6:13 PM Reply | Quote 0 Sign in to vote same here : disable every experience checkboxes and it works fine. (on servers TSE 2K3, 2K8 & his comment is here I also disabled all domain-level startup scripts.
Logon to the Terminal Services computer as an administrator2. Because Of A Protocol Error This Session Will Be Disconnected Windows 8 When uninstalled all my issues go away.Just a pain that i have had to block what is potentiallly a useful update and that microsoft have yet to roll out a fix So if the user does not try to run a remote desktop session the permissions remain as-is.
So I'm only looking at two fixes that are not included in the Service Pack which may or may not have an impact on this:http://support.microsoft.com/kb/2571388/http://support.microsoft.com/kb/2661001The first indicates a resolvement of an Choose Allow connections from computers running any version of Remote Desktop (less secure), click OK4. Heber Gonzalez Consultor en Infraestructura y Mensajería Microsoft www.xelcon.com.ar http://ar.linkedin.com/in/hebergonzalez Monday, March 26, 2012 2:14 PM Reply | Quote 0 Sign in to vote Thanks Heber, However this applies to Server Protocol Error Remote Desktop Connection One problem is that there are some critical applications running under the session (I know, let's not discuss the idiocy of that), so we cannot reset the session in any way
If ANYONE has any thoughts or insight on this, please help. Thanks. -TP Thursday, August 26, 2010 6:51 PM Reply | Quote Moderator 0 Sign in to vote Hi, What is the KB number you are referring to? This is outrageous!!! weblink still a bug.
Changing local policy as decribed DOES NOTHING Thursday, January 19, 2012 4:17 PM Reply | Quote 1 Sign in to vote Installed hotfix on the two 2008 64 machines....Windows6.0-KB976110-x64.msu Choose Allow connections from computers running any version of Remote Desktop (less secure), click OK4. Your last suggestion about redirecting the XA server to a different licensing server isn't really an option, since we have one licensing server, and connections to and from servers on Windows Tuesday, February 23, 2010 8:18 PM Reply | Quote 0 Sign in to vote Does anyone knows if microsoft already fixed this problem ?
When I Install Windows 8 release 9200 ALL PROBLEMS WERE RESOLVED. Disable firewall, including Windows or third-party firewall. Now I can remote control RDP user sessions of Win XP, Win 7 and Win 8 Client from Win 8 RDP session on terminal server. The amount of fixes combined mean I'm not going to activate that image prior to monday tho, provided I get around to creating the image this week still.
Has anyone been able to get around this?