Terminal services dropping connection with Event id 50 in Event log

[Guest Konda Ankireddyapalli]

Hello all,

 

Time to time in our environment we see RDP disconnects followed by the

events below in NT Event Log

 

Event Type: Error

Event Source: TermDD

Event Category: None

Event ID: 50

Date: 8/2/2007

Time: 5:40:05 AM

User: N/A

Computer: BLUE02

Description:

The RDP protocol component "DATA ENCRYPTION" 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 04 00 02 00 52 00 ......R.

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: 94 01 00 00 ”...

 

 

AND

 

 

Event Type: Error

Event Source: TermDD

Event Category: None

Event ID: 50

Date: 8/2/2007

Time: 5:14:46 AM

User: N/A

Computer: BLUE02

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 41 00 02 00 90 00 ..A...�.

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 3d .......=

0030: 02 f0 80 64 00 04 03 eb .ð€d...ë

0038: 70 80 2e 08 00 00 00 1c p€......

0040: cd 8f 6d 42 be b6 21 c6 Í�mB¾¶!Æ

0048: 8e 9f df 0d 5c d6 87 4d ŽŸß.\Ö‡M

0050: e6 39 00 2d 61 54 3e 7b æ9.-aT>{

0058: 5b 39 31 58 fb 07 16 ab [91Xû..«

0060: 7a 2a 93 28 2e 82 04 b7 z*“(.‚.·

0068: f8 ø

 

We followed the steps given in more information

link(http://support.microsoft.com/kb/323497/en-us) but that didn't help

resolve this issue. Can someone direct us to a resolution?

 

Here are details of our environment:

 

Terminal Server : Windows XP sp2

Terminal Services client : Custom client based on rdesktop port to windows.

Terminal Services client runs on the same machine as the server. i.e.,

client connects to server over localhost:3389

RDP protocol version we use: 5

Encryption strength: 128

 

Thanks in advance,

Konda

[Guest Helge Klein]

Re: Terminal services dropping connection with Event id 50 in Event log

 

Did I understand correctly that you are _not_ using the RDP client

from Microsoft? If that is the case I stronly suggest you try the MS

client to see if that fixes the problem.

 

I have not heard of this error before. At first I thought of

networking problems, but an incompatible client sounds like a much

better explanation.

 

I hope this helps.

 

Helge

 

==================

Please visit my blog:

http://it-from-inside.blogspot.com

==================

 

On 8 Aug., 19:45, "Konda Ankireddyapalli" <tdeb...@community.nospam>

wrote:

> Hello all,

>

> Time to time in our environment we see RDP disconnects followed by the

> events below in NT Event Log

>

> Event Type: Error

> Event Source: TermDD

> Event Category: None

> Event ID: 50

> Date: 8/2/2007

> Time: 5:40:05 AM

> User: N/A

> Computer: BLUE02

> Description:

> The RDP protocol component "DATA ENCRYPTION" detected an error in the

> protocol

> stream and has disconnected the client.

>

> For more information, see Help and Support Center athttp://go.microsoft.com/fwlink/events.asp.

> Data:

> 0000: 00 00 04 00 02 00 52 00 ......R.

> 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: 94 01 00 00 ”...

>

> AND

>

> Event Type: Error

> Event Source: TermDD

> Event Category: None

> Event ID: 50

> Date: 8/2/2007

> Time: 5:14:46 AM

> User: N/A

> Computer: BLUE02

> 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 athttp://go.microsoft.com/fwlink/events.asp.

> Data:

> 0000: 00 00 41 00 02 00 90 00 ..A... .

> 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 3d .......=

> 0030: 02 f0 80 64 00 04 03 eb .ð€d...ë

> 0038: 70 80 2e 08 00 00 00 1c p€......

> 0040: cd 8f 6d 42 be b6 21 c6 Í mB¾¶!Æ

> 0048: 8e 9f df 0d 5c d6 87 4d ŽŸß.\Ö‡M

> 0050: e6 39 00 2d 61 54 3e 7b æ9.-aT>{

> 0058: 5b 39 31 58 fb 07 16 ab [91Xû..«

> 0060: 7a 2a 93 28 2e 82 04 b7 z*“(.‚.·

> 0068: f8 ø

>

> We followed the steps given in more information

> link(http://support.microsoft.com/kb/323497/en-us) but that didn't help

> resolve this issue. Can someone direct us to a resolution?

>

> Here are details of our environment:

>

> Terminal Server : Windows XP sp2

> Terminal Services client : Custom client based on rdesktop port to windows.

> Terminal Services client runs on the same machine as the server. i.e.,

> client connects to server over localhost:3389

> RDP protocol version we use: 5

> Encryption strength: 128

>

> Thanks in advance,

> Konda

[Guest Vera Noest [MVP]]

Re: Terminal services dropping connection with Event id 50 in Event log

 

You cannot connect to localhost on XP, at least not with mstsc.

I doubt that it's possible with just another rdp client, since XP

only allows one session at a time, so I suspect that there's more

non-standard configuration done on this machine.

 

_________________________________________________________

Vera Noest

MCSE, CCEA, Microsoft MVP - Terminal Server

TS troubleshooting: http://ts.veranoest.net

___ please respond in newsgroup, NOT by private email ___

 

Helge Klein <Helge.Klein@googlemail.com> wrote on 08 aug 2007 in

microsoft.public.windows.terminal_services:

> Did I understand correctly that you are _not_ using the RDP

> client from Microsoft? If that is the case I stronly suggest you

> try the MS client to see if that fixes the problem.

>

> I have not heard of this error before. At first I thought of

> networking problems, but an incompatible client sounds like a

> much better explanation.

>

> I hope this helps.

>

> Helge

>

> =================Please visit my blog:

> http://it-from-inside.blogspot.com

> =================

> On 8 Aug., 19:45, "Konda Ankireddyapalli"

> <tdeb...@community.nospam> wrote:

>> Hello all,

>>

>> Time to time in our environment we see RDP disconnects

>> followed by the

>> events below in NT Event Log

>>

>> Event Type: Error

>> Event Source: TermDD

>> Event Category: None

>> Event ID: 50

>> Date: 8/2/2007

>> Time: 5:40:05 AM

>> User: N/A

>> Computer: BLUE02

>> Description:

>> The RDP protocol component "DATA ENCRYPTION" detected an error

>> in the protocol

>> stream and has disconnected the client.

>>

>> For more information, see Help and Support Center

>> athttp://go.microsoft.c

> om/fwlink/events.asp.

>> Data:

>> 0000: 00 00 04 00 02 00 52 00 ......R.

>> 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: 94 01 00 00 ”...

>>

>> AND

>>

>> Event Type: Error

>> Event Source: TermDD

>> Event Category: None

>> Event ID: 50

>> Date: 8/2/2007

>> Time: 5:14:46 AM

>> User: N/A

>> Computer: BLUE02

>> 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

>> athttp://go.microsoft.c

> om/fwlink/events.asp.

>> Data:

>> 0000: 00 00 41 00 02 00 90 00 ..A... .

>> 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 3d .......

>> 0030: 02 f0 80 64 00 04 03 eb .ð€d...ë

>> 0038: 70 80 2e 08 00 00 00 1c p€......

>> 0040: cd 8f 6d 42 be b6 21 c6 Í mB¾¶!Æ

>> 0048: 8e 9f df 0d 5c d6 87 4d ŽŸß.\Ö‡M

>> 0050: e6 39 00 2d 61 54 3e 7b æ9.-aT>{

>> 0058: 5b 39 31 58 fb 07 16 ab [91Xû..«

>> 0060: 7a 2a 93 28 2e 82 04 b7 z*“(.‚.·

>> 0068: f8 ø

>>

>> We followed the steps given in more information

>> link(http://support.microsoft.com/kb/323497/en-us) but that

>> didn't help resolve this issue. Can someone direct us to a

>> resolution?

>>

>> Here are details of our environment:

>>

>> Terminal Server : Windows XP sp2

>> Terminal Services client : Custom client based on rdesktop port

>> to window

> s.

>> Terminal Services client runs on the same machine as the

>> server. i.e., client connects to server over localhost:3389

>> RDP protocol version we use: 5

>> Encryption strength: 128

>>

>> Thanks in advance,

>> Konda

[Guest Konda Ankireddyapalli]

Re: Terminal services dropping connection with Event id 50 in Event log

 

We are using a custom RDP client, which is windows port of rdesktop. The

client connects to localhost. It works flawlessly but at times its

connection to MSTS gets lost. Is there a way to get more information on this

error? Does MSTS have any 'verbose' logging mode that we can turn on to get

more information?

 

 

"Vera Noest [MVP]" <vera.noest@remove-this.hem.utfors.se> wrote in message

news:Xns9986ED2FD6084veranoesthemutforsse@207.46.248.16...

> You cannot connect to localhost on XP, at least not with mstsc.

> I doubt that it's possible with just another rdp client, since XP

> only allows one session at a time, so I suspect that there's more

> non-standard configuration done on this machine.

>

> _________________________________________________________

> Vera Noest

> MCSE, CCEA, Microsoft MVP - Terminal Server

> TS troubleshooting: http://ts.veranoest.net

> ___ please respond in newsgroup, NOT by private email ___

>

> Helge Klein <Helge.Klein@googlemail.com> wrote on 08 aug 2007 in

> microsoft.public.windows.terminal_services:

>

>> Did I understand correctly that you are _not_ using the RDP

>> client from Microsoft? If that is the case I stronly suggest you

>> try the MS client to see if that fixes the problem.

>>

>> I have not heard of this error before. At first I thought of

>> networking problems, but an incompatible client sounds like a

>> much better explanation.

>>

>> I hope this helps.

>>

>> Helge

>>

>> =================Please visit my blog:

>> http://it-from-inside.blogspot.com

>> =================

>> On 8 Aug., 19:45, "Konda Ankireddyapalli"

>> <tdeb...@community.nospam> wrote:

>>> Hello all,

>>>

>>> Time to time in our environment we see RDP disconnects

>>> followed by the

>>> events below in NT Event Log

>>>

>>> Event Type: Error

>>> Event Source: TermDD

>>> Event Category: None

>>> Event ID: 50

>>> Date: 8/2/2007

>>> Time: 5:40:05 AM

>>> User: N/A

>>> Computer: BLUE02

>>> Description:

>>> The RDP protocol component "DATA ENCRYPTION" detected an error

>>> in the protocol

>>> stream and has disconnected the client.

>>>

>>> For more information, see Help and Support Center

>>> athttp://go.microsoft.c

>> om/fwlink/events.asp.

>>> Data:

>>> 0000: 00 00 04 00 02 00 52 00 ......R.

>>> 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: 94 01 00 00 â?�...

>>>

>>> AND

>>>

>>> Event Type: Error

>>> Event Source: TermDD

>>> Event Category: None

>>> Event ID: 50

>>> Date: 8/2/2007

>>> Time: 5:14:46 AM

>>> User: N/A

>>> Computer: BLUE02

>>> 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

>>> athttp://go.microsoft.c

>> om/fwlink/events.asp.

>>> Data:

>>> 0000: 00 00 41 00 02 00 90 00 ..A... .

>>> 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 3d .......

>>> 0030: 02 f0 80 64 00 04 03 eb .ðâ,¬d...ë

>>> 0038: 70 80 2e 08 00 00 00 1c pâ,¬......

>>> 0040: cd 8f 6d 42 be b6 21 c6 � mB¾¶!�

>>> 0048: 8e 9f df 0d 5c d6 87 4d ŽŸÃY.\Ã-â?¡M

>>> 0050: e6 39 00 2d 61 54 3e 7b æ9.-aT>{

>>> 0058: 5b 39 31 58 fb 07 16 ab [91Xû..«

>>> 0060: 7a 2a 93 28 2e 82 04 b7 z*â?o(.â?s.·

>>> 0068: f8 ø

>>>

>>> We followed the steps given in more information

>>> link(http://support.microsoft.com/kb/323497/en-us) but that

>>> didn't help resolve this issue. Can someone direct us to a

>>> resolution?

>>>

>>> Here are details of our environment:

>>>

>>> Terminal Server : Windows XP sp2

>>> Terminal Services client : Custom client based on rdesktop port

>>> to window

>> s.

>>> Terminal Services client runs on the same machine as the

>>> server. i.e., client connects to server over localhost:3389

>>> RDP protocol version we use: 5

>>> Encryption strength: 128

>>>

>>> Thanks in advance,

>>> Konda

[Guest Vera Noest [MVP]]

Re: Terminal services dropping connection with Event id 50 in Event log

 

Not that I know of.

And again, your setup is not supposed to work.

_________________________________________________________

Vera Noest

MCSE, CCEA, Microsoft MVP - Terminal Server

TS troubleshooting: http://ts.veranoest.net

___ please respond in newsgroup, NOT by private email ___

 

"Konda Ankireddyapalli" <tdebber@community.nospam> wrote on 09 aug

2007 in microsoft.public.windows.terminal_services:

> We are using a custom RDP client, which is windows port of

> rdesktop. The client connects to localhost. It works flawlessly

> but at times its connection to MSTS gets lost. Is there a way to

> get more information on this error? Does MSTS have any 'verbose'

> logging mode that we can turn on to get more information?

>

>

> "Vera Noest [MVP]" <vera.noest@remove-this.hem.utfors.se> wrote

> in message

> news:Xns9986ED2FD6084veranoesthemutforsse@207.46.248.16...

>> You cannot connect to localhost on XP, at least not with mstsc.

>> I doubt that it's possible with just another rdp client, since

>> XP only allows one session at a time, so I suspect that there's

>> more non-standard configuration done on this machine.

>>

>> _________________________________________________________

>> Vera Noest

>> MCSE, CCEA, Microsoft MVP - Terminal Server

>> TS troubleshooting: http://ts.veranoest.net

>> ___ please respond in newsgroup, NOT by private email ___

>>

>> Helge Klein <Helge.Klein@googlemail.com> wrote on 08 aug 2007

>> in microsoft.public.windows.terminal_services:

>>

>>> Did I understand correctly that you are _not_ using the RDP

>>> client from Microsoft? If that is the case I stronly suggest

>>> you try the MS client to see if that fixes the problem.

>>>

>>> I have not heard of this error before. At first I thought of

>>> networking problems, but an incompatible client sounds like a

>>> much better explanation.

>>>

>>> I hope this helps.

>>>

>>> Helge

>>>

>>> =================Please visit my blog:

>>> http://it-from-inside.blogspot.com

>>> =================

>>> On 8 Aug., 19:45, "Konda Ankireddyapalli"

>>> <tdeb...@community.nospam> wrote:

>>>> Hello all,

>>>>

>>>> Time to time in our environment we see RDP disconnects

>>>> followed by the

>>>> events below in NT Event Log

>>>>

>>>> Event Type: Error

>>>> Event Source: TermDD

>>>> Event Category: None

>>>> Event ID: 50

>>>> Date: 8/2/2007

>>>> Time: 5:40:05 AM

>>>> User: N/A

>>>> Computer: BLUE02

>>>> Description:

>>>> The RDP protocol component "DATA ENCRYPTION" detected an

>>>> error in the protocol

>>>> stream and has disconnected the client.

>>>>

>>>> For more information, see Help and Support Center

>>>> athttp://go.microsoft.c

>>> om/fwlink/events.asp.

>>>> Data:

>>>> 0000: 00 00 04 00 02 00 52 00 ......R.

>>>> 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: 94 01 00 00 â?�...

>>>>

>>>> AND

>>>>

>>>> Event Type: Error

>>>> Event Source: TermDD

>>>> Event Category: None

>>>> Event ID: 50

>>>> Date: 8/2/2007

>>>> Time: 5:14:46 AM

>>>> User: N/A

>>>> Computer: BLUE02

>>>> 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

>>>> athttp://go.microsoft.c

>>> om/fwlink/events.asp.

>>>> Data:

>>>> 0000: 00 00 41 00 02 00 90 00 ..A... .

>>>> 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 3d .......

>>>> 0030: 02 f0 80 64 00 04 03 eb .ðâ,¬d...ë

>>>> 0038: 70 80 2e 08 00 00 00 1c pâ,¬......

>>>> 0040: cd 8f 6d 42 be b6 21 c6 � mB¾¶!�

>>>> 0048: 8e 9f df 0d 5c d6 87 4d ŽŸÃY.\Ã-â?¡M

>>>> 0050: e6 39 00 2d 61 54 3e 7b æ9.-aT>{

>>>> 0058: 5b 39 31 58 fb 07 16 ab [91Xû..«

>>>> 0060: 7a 2a 93 28 2e 82 04 b7 z*â?o(.â?s.·

>>>> 0068: f8 ø

>>>>

>>>> We followed the steps given in more information

>>>> link(http://support.microsoft.com/kb/323497/en-us) but that

>>>> didn't help resolve this issue. Can someone direct us to a

>>>> resolution?

>>>>

>>>> Here are details of our environment:

>>>>

>>>> Terminal Server : Windows XP sp2

>>>> Terminal Services client : Custom client based on rdesktop

>>>> port to window

>>> s.

>>>> Terminal Services client runs on the same machine as the

>>>> server. i.e., client connects to server over localhost:3389

>>>> RDP protocol version we use: 5

>>>> Encryption strength: 128

>>>>

>>>> Thanks in advance,

>>>> Konda