Re: The RDP protocol component X.224 detected an error in the protocol stream and has disconnected the client.
- From: "Vera Noest [MVP]" <Vera.Noest@xxxxxxxxxxxxxxxxxxxxxxxxx>
- Date: Wed, 23 Nov 2005 06:54:13 -0800
You should check this one instead. Deleteing the certificate keys
from the registry of the server usually solves it.
329896 - Error Message: Because of a Security Error, the Client Could
Not Connect to the Terminal Server
http://support.microsoft.com/?kbid=329896
_________________________________________________________
Vera Noest
MCSE, CCEA, Microsoft MVP - Terminal Server
TS troubleshooting: http://ts.veranoest.net
*----------- Please reply in newsgroup -------------*
"Spin" <Spin@xxxxxxxx> wrote on 23 nov 2005:
> See that's just the thing. The article says this can even be
> caused by clients that disconnected their session correctly, and
> even if no client sessions have been disconnected. And that it
> applies to Windows 2000 (and if this is the case one can safely
> ignore this error message). Well, I am running Windows 2003.
.
- Follow-Ups:
- References:
- The RDP protocol component X.224 detected an error in the protocol stream and has disconnected the client.
- From: Spin
- Re: The RDP protocol component X.224 detected an error in the protocol stream and has disconnected the client.
- From: Dr.Conti
- Re: The RDP protocol component X.224 detected an error in the protocol stream and has disconnected the client.
- From: Spin
- The RDP protocol component X.224 detected an error in the protocol stream and has disconnected the client.
- Prev by Date: Re: Deployment - Active Directory and SQL Server
- Next by Date: Re: Office User Information in Word and Excel
- Previous by thread: Re: The RDP protocol component X.224 detected an error in the protocol stream and has disconnected the client.
- Next by thread: Re: The RDP protocol component X.224 detected an error in the protocol stream and has disconnected the client.
- Index(es):
Relevant Pages
|
