phone 983-651-5611
Home > Event Id > Event Id 50 Termdd X.224

Event Id 50 Termdd X.224

Does not tell me the root cause of the issue but at least it is working now. You can take the full course on Experts Exchange at I already have Wireshark on the machine, so I will give that a shot. –Jack Jan 21 '11 at 15:52 I let Wireshark run for a time, and it share|improve this answer answered Jan 21 '11 at 7:38 Evan Anderson 128k13146290 I am the only person using RDP, and I typically leave the Remote Desktop window open to

It is exposed to the outside world, but only port 80 is open to it. This is documented in ME323497. Event ID: 50 Source: TermDD Source: TermDD Type: Error Description:The RDP protocol component detected an error in the protocol stream and has disconnected the client. See WITP77335 for details on solving this problem.

Follow Us You can follow us on these social networks: Contact Us Axon IT, Guildford House, Heather Close, Lyme Green Business Park, Macclesfield, Cheshire, SK11 0LR. Thanks Angelo Event Type:Error Event Source:TermDD Event Category:None Event ID:50 Date:4/27/2012 Time:11:09:07 AM User:N/A Computer:DC1 Description: The RDP protocol component X.224 detected an error in the protocol stream and has disconnected Let me know. See if any of the conditions apply to your situation: 0 Message Author Comment by:jared52 ID: 216576002008-05-27 Yep, I tried every fix on that page and after each one

Because of a security error, the client could not connect to the remote computer. This is a known problem. x 52 EventID.Net - Component: "DATA ENCRYPTION" - As per Microsoft: "Microsoft has added the FIPS Compliantsetting to the options for Terminal Services encryption levels in Windows Server 2003. Custom search for *****: Google - Bing - Microsoft - Yahoo Feedback: Send comments or solutions - Notify me when updated Printer friendly Subscribe Subscribe to EventID.Net now!Already a subscriber?

Any help if finding out what this error means and hopefully getting a resolution would be great. TS on this machine is used frequently by admins to administer the system but mostly RDP is OK, at least from my experience. The only problem we has sometimes is usually caused because we are using IPSec for RDP. You will use cases for the value-added capabilities of Veeam®, including combining backup and replication for VMware disaster recovery and using replication for data center migration.

Join Now For immediate help use Live now! Get 1:1 Help Now Advertise Here Enjoyed your answer? x 88 Anonymous In my case, I was not able to connect remotely into an Windows XP machine. Increase in steps of 50 each until the connection brokes.

Thanks AngeloAngelo Monday, April 30, 2012 8:59 PM Reply | Quote 0 Sign in to vote Hi Angelo, Based on what you have written I would ignore the error. i've the same problem!! In the meantime I have locked down every other port and watching the router logs to see if the new port is discovered until the new firewall is installed. 0 more stack exchange communities company blog Stack Exchange Inbox Reputation and Badges sign up log in tour help Tour Start here for a quick overview of the site Help Center Detailed

A more likely cause to this error is due to a low-bandwidth situation, and decryption is not happening correctly. Encryption levels defined on the RDP-TCP connection (or ICA, if appropriate), are set too high for the client to successfully negotiate. Login By creating an account, you're agreeing to our Terms of Use and our Privacy Policy © Copyright 2006-2016 Spiceworks Inc. There's no problem with Remote Desktop, it works normally, and is actually how I interact with these machines, there are no disconnections going on.

If you don't make any headway with those suggestions, sniff the traffic on the box for a day w/ a capture filter set to only record RDP traffic and see what If you are experiencing a similar issue, please ask a related question Suggested Solutions Title # Comments Views Activity Can’t delete Windows.old in Windows 10 11 81 72d Inserting a column last update installed was on June 16. Subscribe to our monthly newsletter for tech news and trends Membership How it Works Gigs Live Careers Plans and Pricing For Business Become an Expert Resource Center About Us Who We

Join the community Back I agree Powerful tools you need, all for free. Bowers - Component: "DATA ENCRYPTION". Hopefully someone with personal experience with the error will be along. --Rob 0 Message Author Comment by:jared52 ID: 216690832008-05-29 I still don't have a solution.

PRTG is easy to set up &use.

Thank you for searching on this message; your search helps us identify those areas for which we need to provide more information. Join the community of 500,000 technology professionals and ask your questions. There is a hotfix for this error produced by Microsoft. Event Xml: 50 2 0 0x80000000000000

See example of private comment Search: Google - Bing - Microsoft - Yahoo - EventID.Net Queue (0) - More links... None of the websites I've found (, Technet, this site, etc.) have a solution for my problem. Comments: Anonymous This error can be caused by having Hamachi software installed and enabled. this contact form Also see ME232514 for more information about Terminal Services security.

For example, a client set to Low encryption would be unable to connect to a server with High (or now, FIPS compliant) encryption levels defined. Turned it off again, and attachments worked perfectly. In 9 out of 10 cases this resolves the issue. 3. x 35 Anonymous - Component: "X.224" - Updating the network card driver is what ultimately fixed this problem for me.

Great for personal to-do lists, project milestones, team priorities and launch plans. - Combine task lists, docs, spreadsheets, and chat in one - View and edit from mobile/offline - Cut down x 44 Anonymous For us overwriting a few files with SP3 original solved the issue: copyc:\windows\ServicePackFiles\i386\lhmstsc.chmc:\windows\Help\mstsc.chm copyc:\windows\ServicePackFiles\i386\lhmstsc.exec:\windows\system32\mstsc.exe copyc:\windows\ServicePackFiles\i386\lhmstsc.exec:\windows\system32\dllcache\mstsc.exe copyc:\windows\ServicePackFiles\i386\lhmstsc.muic:\windows\system32\en-US\mstsc.exe.mui copyc:\windows\ServicePackFiles\i386\lhmstscx.dllc:\windows\system32\mstscax.dll copyc:\windows\ServicePackFiles\i386\lhmstscx.dllc:\windows\system32\dllcache\mstscax.dll copyc:\windows\ServicePackFiles\i386\lhmstscx.muic:\windows\system32\en-US\mstscax.dll.mui x 32 EventID.Net Reported protocol components: - X.224 - x 38 B-rad - Component: "DATA ENCRYPTION". All rights reserved.