Client won't connect/RD service failure

  • Thread starter Thread starter Guest
  • Start date Start date
G

Guest

Hello, hope somebody knows a solution to this. Been running RDP on XP Professional for a while and worked great, clients being 2000. Lately I've been having this problem - every once in a while the client would prompt for login credentials and after they are entered the screen goes black and after a while it times out and the client window gets killed. The only way to fix this is restart the XP (what's up with that, Microsoft, why not just restart the service?!) but then it would work for awhile and do the same. This happens with client 5.1 and 5.2. The log on XP shows an error mesage described in 329896: "Because of a Security Error, the Client Could Not Connect to the Terminal Server". The actual error is

Event ID: (not sure what's here
Event Source: TermD
Event Description: The RDP protocol component WD detected an error in the protocol stream and has disconnected the clien

I did what this article recommends but alas. Can anyone suggest anything

Thanks.
 
Any change to the network connecting the clients to your machine?

Router?
firmware?
 
No, no changes in the network configuration at all... Just restarted the computer and same thing happened again. Checked the log, turned out besides TermDD-WD component error there is also TermDD-X.224 component error, too. Of course, I've tried cleaning up the registry for the clients as per MSKB advisory with no luck, though.
 
It'd help to have full text of the error log messages
You can type in the event id and the source , and the text is cut and
pastable--control v to copy to the clipboard/
 
Here are the original error messages (scroll down for the
second one):

Event Type: Error
Event Source: TermDD
Event Category: None
Event ID: 50
Date: 1/13/2004
Time: 12:42:37 AM
User: N/A
Computer: EON
Description:
The RDP protocol component WD detected an error in the
protocol stream and has disconnected the client.

For more information, see Help and Support Center at
http://go.microsoft.com/fwlink/events.asp.
Data:
0000: 00 00 2a 00 02 00 78 00 ..*...x.
0008: 00 00 00 00 32 00 0a c0 ....2..À
0010: 00 00 00 00 32 00 0a c0 ....2..À
0018: 00 00 00 00 00 00 00 00 ........
0020: 00 00 00 00 00 00 00 00 ........
0028: cb 00 00 00 37 00 20 00 Ë...7. .
0030: 32 00 31 00 20 00 32 00 2.1. .2.
0038: 00 00 00 00 02 e8 b2 e2 .....è²â
0040: 66 71 e8 87 00 00 00 00 fqè‡....
0048: 1d 00 00 00 62 71 e8 87 ....bqè‡
0050: 58 e5 Xå


Event Type: Error
Event Source: TermDD
Event Category: None
Event ID: 50
Date: 1/13/2004
Time: 12:42:37 AM
User: N/A
Computer: EON
Description:
The RDP protocol component X.224 detected an error in the
protocol stream and has disconnected the client.

For more information, see Help and Support Center at
http://go.microsoft.com/fwlink/events.asp.
Data:
0000: 00 00 3c 00 02 00 8a 00 ..<...Š.
0008: 00 00 00 00 32 00 0a c0 ....2..À
0010: 00 00 00 00 32 00 0a c0 ....2..À
0018: 00 00 00 00 00 00 00 00 ........
0020: 00 00 00 00 00 00 00 00 ........
0028: 09 00 00 00 03 00 00 38 .......8
0030: 02 f0 80 64 00 06 03 eb .ð€d...ë
0038: 70 2a 08 00 85 7e bc c8 p*..…~¼È
0040: 32 70 d3 a7 44 43 1e 00 2pÓ§DC..
0048: 17 00 ef 03 ea 03 01 00 ..ï.ê...
0050: 00 01 0c 00 21 00 00 00 ....!...
0058: 01 00 00 00 00 01 01 00 ........
0060: ff 02 13 00 ÿ...
 
Thank you, Huei. Unfortunately this didn't help, from the
articles it seems that it applies to W2K while I am using
XPpro.
 
I've done some more searching on this one without much luck.

There's a post from a Microsoft staffer in this group which suggests that
this error can be caused by a Cisco Aironet configuration utility, I
think--so you might consider working with MSCONFIG to eliminate any bits of
networking stuff you could do without temporarily for troubleshooting.

Here are the original error messages (scroll down for the
second one):

Event Type: Error
Event Source: TermDD
Event Category: None
Event ID: 50
Date: 1/13/2004
Time: 12:42:37 AM
User: N/A
Computer: EON
Description:
The RDP protocol component WD detected an error in the
protocol stream and has disconnected the client.

For more information, see Help and Support Center at
http://go.microsoft.com/fwlink/events.asp.
Data:
0000: 00 00 2a 00 02 00 78 00 ..*...x.
0008: 00 00 00 00 32 00 0a c0 ....2..À
0010: 00 00 00 00 32 00 0a c0 ....2..À
0018: 00 00 00 00 00 00 00 00 ........
0020: 00 00 00 00 00 00 00 00 ........
0028: cb 00 00 00 37 00 20 00 Ë...7. .
0030: 32 00 31 00 20 00 32 00 2.1. .2.
0038: 00 00 00 00 02 e8 b2 e2 .....è²â
0040: 66 71 e8 87 00 00 00 00 fqè‡....
0048: 1d 00 00 00 62 71 e8 87 ....bqè‡
0050: 58 e5 Xå


Event Type: Error
Event Source: TermDD
Event Category: None
Event ID: 50
Date: 1/13/2004
Time: 12:42:37 AM
User: N/A
Computer: EON
Description:
The RDP protocol component X.224 detected an error in the
protocol stream and has disconnected the client.

For more information, see Help and Support Center at
http://go.microsoft.com/fwlink/events.asp.
Data:
0000: 00 00 3c 00 02 00 8a 00 ..<...Š.
0008: 00 00 00 00 32 00 0a c0 ....2..À
0010: 00 00 00 00 32 00 0a c0 ....2..À
0018: 00 00 00 00 00 00 00 00 ........
0020: 00 00 00 00 00 00 00 00 ........
0028: 09 00 00 00 03 00 00 38 .......8
0030: 02 f0 80 64 00 06 03 eb .ð€d...ë
0038: 70 2a 08 00 85 7e bc c8 p*..…~¼È
0040: 32 70 d3 a7 44 43 1e 00 2pÓ§DC..
0048: 17 00 ef 03 ea 03 01 00 ..ï.ê...
0050: 00 01 0c 00 21 00 00 00 ....!...
0058: 01 00 00 00 00 01 01 00 ........
0060: ff 02 13 00 ÿ...
 
Back
Top