jabronicus
asked on
RDP session logging error in event log
The RDP protocol component X.224 detected an error in the protocol stream and has disconnected the client. This is an error listed with event id 50 in my system event log. I have had this before and reinstalled the os, xp pro and that helped the problem. It cropped up again this week however and all the knowledgebase articles are in relation to configuration and registry modifications on a terminal server. This is my home pc and is not part of any domain. It is a stand alone machine that I attempt to access from the field multiple times daily. It usually starts with a session disconnecting when I log off, then further reconnect attempts present me with a blank black screen, but no logon ever becomes available. When I got home the errors were logged.
I support multiple terminal servers and clients and have never seen this before. Has anyone ever come across this strange problem? I would rather not install the os again, and it is driving me crazy trying to find the fix. Any help most appreciated.
I support multiple terminal servers and clients and have never seen this before. Has anyone ever come across this strange problem? I would rather not install the os again, and it is driving me crazy trying to find the fix. Any help most appreciated.
ASKER
Thanks, but I have gone over this KB article several times and I am not so sure it is applicable. For starters I am running XP pro SP1, not 2000 SP3. Second I even get the problem when connecting using a similar machine, running same OS, same applications, same encryption level.
I am hesitant to install SP2 until the word is out that it is an improvement and not a headache. Thanks for the research tho. Also curious as to why thsi all starts after a period of 3 months or so, when previous functionality was flawless. The machine is new, built it myself. P4 3.06 with all the bells and whistles.
Strange stuff.
I am hesitant to install SP2 until the word is out that it is an improvement and not a headache. Thanks for the research tho. Also curious as to why thsi all starts after a period of 3 months or so, when previous functionality was flawless. The machine is new, built it myself. P4 3.06 with all the bells and whistles.
Strange stuff.
Have you heard more about this? I am having a similar problem on a client’s network.
What is happening is as follows:
When I connect to the user’s machine using RDP from my office network, via a secure VPN session, I can get in no problem. When he tries to connect, from the same VPN entrance from his home laptop, he gets a screen color change, it hangs, then comes back in a few seconds or a minute and fails to connect. The event logs show “The RDP protocol component X.224 detected an error in the protocol stream and has disconnected the client.” With event ID 50. Now, when I am trying from a machine within the network, it works fine, and I am sure when I get back to my office, it’ll work fine as well. But he’s on the phone, trying to connect in from home, and gets nothing.
Thoughts?
What is happening is as follows:
When I connect to the user’s machine using RDP from my office network, via a secure VPN session, I can get in no problem. When he tries to connect, from the same VPN entrance from his home laptop, he gets a screen color change, it hangs, then comes back in a few seconds or a minute and fails to connect. The event logs show “The RDP protocol component X.224 detected an error in the protocol stream and has disconnected the client.” With event ID 50. Now, when I am trying from a machine within the network, it works fine, and I am sure when I get back to my office, it’ll work fine as well. But he’s on the phone, trying to connect in from home, and gets nothing.
Thoughts?
ASKER
I have since installed SP2 and there seems to be a fix included for this problem as I am no longer having issues with my remote connection.
Hope this helps.
Hope this helps.
ASKER CERTIFIED SOLUTION
membership
This solution is only available to members.
To access this solution, you must be a member of Experts Exchange.
It descripbes your problem pretty well.
From what I understand, this problem occurs when you connect from one machine using one encryption level and then you try to connect from another and the encryption levels differ. My suggestion would be to update your xp machine to the latest service pack as well as any machines that you try to connect from.