Sign in with
Sign up | Sign in
Your question

Reconnecting Remote Desktop on XP Pro

Last response: in Windows XP
Share
Anonymous
July 24, 2004 4:43:17 AM

Archived from groups: microsoft.public.windowsxp.work_remotely (More info?)

I had the same problem as I see posted here occasionally that I never
saw a definitive solution for. Is there a good Remote Desktop FAQ? I
am using a Windows CE box to connect to XP Pro running Remote Desktop.
Everything works fine, if I log off when I am done. But, if the
connection is dropped, or I close the connection staying logged on, I
am unable to log back in. You can see the errors logged below. The
simplest fix was this:

Don't automatically send a password!

When I ran the RD client application and logged in manually, it worked
fine.

The other fix was to go to the system console and log in (and
sometimes back out) to get the remote going.

The other fix, which I've seen mentioned, is to reboot, which is
hardly elegant.


Source: TermDD
Category: None
Type: Error
Event ID: 50
User: N/A
Description:
The RDP protocol component X.224 detected an error in the protocol
stream and has disconnected the client.

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 03 03 eb .ð€d...ë
0038: 70 2a 08 00 70 2e 2e ee p*..p..î
0040: 4f 38 b2 5f 1c 07 1e 00 O8²_....
0048: 17 00 ec 03 ea 03 01 00 ..ì.ê...
0050: 00 01 0c 00 21 00 00 00 ....!...
0058: 01 00 00 00 00 00 00 00 ........
0060: 7f 02 da 01 .Ú.


Source: TermDD
Category: None
Event ID: 50
User: N/A

The RDP protocol component WD detected an error in the protocol stream
and has disconnected the client.

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 18 2d e3 ......-ã
0040: 1e 73 e4 fc 00 00 00 00 .säü....
0048: 09 00 00 00 1a 73 e4 fc .....säü
0050: 58 15 X.

Here are things that it is NOT:

Encryption is not the culprit here, as suggested in other articles.

Another suggested the MTU size on the network. Not that either.

Not Q312313, not Q311371, not Q257894, not Q232514, nor any other
Microsoft article I could find.

I hope this helps some other poor soul.

- Keith Glidewell
Anonymous
July 24, 2004 9:22:13 AM

Archived from groups: microsoft.public.windowsxp.work_remotely (More info?)

What "Windows CE box" are you using?

With the new Windows Mobile 2003 OS there is a reconnect bug in the built-in TSC...

http://support.microsoft.com/default.aspx?scid=kb;en-us;555061&Product=pockpc

....that some manufacturers, including HP, have corrected via a workaround... Here is the link to the
HP workaround Softpaq...

http://h18000.www1.hp.com/support/files/handheldiPAQ/us...

--
Al Jarvi (MS-MVP Windows Networking)

Please post *ALL* questions and replies to the news group for the mutual benefit of all of us...
The MS-MVP Program - http://mvp.support.microsoft.com
This posting is provided "AS IS" with no warranties, and confers no rights...

"Keith Glidewell" <glidewell@nc.rr.com> wrote in message
news:b8a4291f.0407232343.59c46a7@posting.google.com...
>I had the same problem as I see posted here occasionally that I never
> saw a definitive solution for. Is there a good Remote Desktop FAQ? I
> am using a Windows CE box to connect to XP Pro running Remote Desktop.
> Everything works fine, if I log off when I am done. But, if the
> connection is dropped, or I close the connection staying logged on, I
> am unable to log back in. You can see the errors logged below. The
> simplest fix was this:
>
> Don't automatically send a password!
>
> When I ran the RD client application and logged in manually, it worked
> fine.
>
> The other fix was to go to the system console and log in (and
> sometimes back out) to get the remote going.
>
> The other fix, which I've seen mentioned, is to reboot, which is
> hardly elegant.
>
>
> Source: TermDD
> Category: None
> Type: Error
> Event ID: 50
> User: N/A
> Description:
> The RDP protocol component X.224 detected an error in the protocol
> stream and has disconnected the client.
>
> 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 03 03 eb .ð€d...ë
> 0038: 70 2a 08 00 70 2e 2e ee p*..p..î
> 0040: 4f 38 b2 5f 1c 07 1e 00 O8²_....
> 0048: 17 00 ec 03 ea 03 01 00 ..ì.ê...
> 0050: 00 01 0c 00 21 00 00 00 ....!...
> 0058: 01 00 00 00 00 00 00 00 ........
> 0060: 7f 02 da 01 .Ú.
>
>
> Source: TermDD
> Category: None
> Event ID: 50
> User: N/A
>
> The RDP protocol component WD detected an error in the protocol stream
> and has disconnected the client.
>
> 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 18 2d e3 ......-ã
> 0040: 1e 73 e4 fc 00 00 00 00 .säü....
> 0048: 09 00 00 00 1a 73 e4 fc .....säü
> 0050: 58 15 X.
>
> Here are things that it is NOT:
>
> Encryption is not the culprit here, as suggested in other articles.
>
> Another suggested the MTU size on the network. Not that either.
>
> Not Q312313, not Q311371, not Q257894, not Q232514, nor any other
> Microsoft article I could find.
>
> I hope this helps some other poor soul.
>
> - Keith Glidewell
!