ThinTerm gets Protocol Error only to one Server.

  • Thread starter Thread starter Scott Townsend
  • Start date Start date
S

Scott Townsend

I have a Wyse ThinTerm and it connects to two Servers. One of the server (A)
it connects to gets protocol error and drops the connection. The other
server (B) we connect to stays connected just fine. The two server are
right next to each other.

There are only 2 of 12 ThinTerms that this happens to. the other 10 work
great. They are also on the same network as the 2 that drop. All PC RDP
connections are fine.

If I connect to Server B and then from Server B connect to Server A, it
stays Connected.

Both Server A & B are Win2000 Server with the latest service Packs.

Any Suggestions?

Thanks,
Scott<-
 
Hmmm... I looked in the Logs and do not see anything that might come close
to relating.

Some events I should be looking for?

Thanks,
Scott-
 
I had expected this:

Event ID: 50
Event Source: TermDD
Event Description: The RDP protocol component X.224 detected an
error in the protocol stream and has disconnected the client.

or this:

Event Type: Error
Event Source: TermDD
Event ID: 50
Description: The RDP protocol component "DATA ENCRYPTION" detected
an error in the protocol stream and has disconnected the client.

Anyhow, the solution for both is the same: delete some certificates
from the server:

329896 - Error Message: Because of a Security Error, the Client
Could Not Connect to the Terminal Server
http://support.microsoft.com/?kbid=329896

323497 - Error Message: The RDP Protocol Component "DATA
ENCRYPTION" Detected an Error...
http://support.microsoft.com/?kbid=323497

But check this as well:

824683 - FIX: A Terminal Server Client Session Quits Unexpectedly
Because of a Protocol Error
http://support.microsoft.com/?kbid=824683
 
Back
Top