On a XP SP2 machine. There is no Terminal Server and Remote desktop is not
being used very much at all.

But I get a bunch of these logged. 17 over a 4 minute period and no one was
using the machine or being remoted into.

"The RDP protocol component X.224 detected an error in the protocol stream
and has disconnected the client."

Any advise?

Purtech,

Please take a look at this document which does describe your error &
solution:

http://support.microsoft.com/?kbid=323497
http://support.microsoft.com/?kbid=329896

--
Newbie Coder
(It's just a name)


"Purtech" <mikek(remove)@hlit.net> wrote in message
news:(E-Mail Removed)...
> On a XP SP2 machine. There is no Terminal Server and Remote desktop is not
> being used very much at all.
>
> But I get a bunch of these logged. 17 over a 4 minute period and no one
was
> using the machine or being remoted into.
>
> "The RDP protocol component X.224 detected an error in the protocol stream
> and has disconnected the client."
>
> Any advise?
>
>

TermDD is termdd.sys, Terminal Device Driver. Which is used with Terminal
Server and Remote Desktop, maybe other services. Termdd.sys: The Remote
Desktop Protocol (RDP), which listens for RDP client connections on a TCP
port.

TermDD service...
HKEY_LOCAL_MACHINE\SYSTEM\CurrentControlSet\Services\TermDD

The TermDD service is enabled on both of my machines. I assume just in case
I want to enable some Remote blah blah service, which I do not want to do.

ID: 50
Source: TermDD
http://www.microsoft.com/technet/sup...rmDD&LCID=1033

"The RDP Protocol Component "DATA ENCRYPTION" Detected an Error..." error
message
http://support.microsoft.com/kb/323497

MS01-052: Invalid RDP data can cause Terminal Services failure
http://support.microsoft.com/kb/307454

Remote Assistance connection to Windows Server 2003 with FIPS encryption
does not work
http://support.microsoft.com/kb/811770

No need to subscribe to eventid.net, all the links to the articles are
included below.

Event ID: 50
Source TermDD
http://www.eventid.net/display.asp?e...TermDD&phase=1

JSI Tip 6031
6031 » When you upgrade a Windows NT 4.0 domain to Windows 2000, Terminal
Services clients receive 'Because of a security error, the client could not
connect to the Terminal server'? 03-Dec-02
http://www.jsifaq.com/SF/Tips/Tip.aspx?id=6031

An incorrect X.224 protocol error message is logged
http://support.microsoft.com/kb/312313

Terminal Services Sessions Are Disconnected Because of a Decryption Error
http://support.microsoft.com/kb/311371

Terminal Services Client Cannot Connect to a Server Running 128-bit
Encryption
http://support.microsoft.com/kb/257894

Securing Terminal Server Communications Between Client and Server
http://support.microsoft.com/kb/232514

Because of a security error, the client could not connect to the Terminal
Server
http://support.microsoft.com/kb/329896

--
Hope this helps. Let us know.

Wes
MS-MVP Windows Shell/User

In news:(E-Mail Removed),
Purtech <mikek(remove)@hlit.net> hunted and pecked:
> On a XP SP2 machine. There is no Terminal Server and Remote desktop is not
> being used very much at all.
>
> But I get a bunch of these logged. 17 over a 4 minute period and no one
> was using the machine or being remoted into.
>
> "The RDP protocol component X.224 detected an error in the protocol stream
> and has disconnected the client."
>
> Any advise?