problems with Remote Desktop

[Ensign]

My company recently moved me to a different physical location. At my previous location, I could use Remote Desktop (client, not web version) on a W2K PC to connect to my home XP Pro PC without any issues. Now, when I try to connect, I get one of the following errors (seems to toggle between them after each successive try):

Because of a protocol error detected at the client (code 0x1104), this session will be disconnected. Please try connecting to the remote computer again.

Because of a protocol error, this session will be disconnected. Please try connecting to the remote computer again.

I confirmed that a co-worker at my previous location can still connect through Remote Desktop to my home PC, so I don't believe it's an issue on my home PC.

I checked my Event Viewer and found the following entry (checked out everything mentioned on the MS site about this and everything looked fine). Oddly enough, there was not an Event entry for each connection attempt, I only saw one (I tried a bunch of times):disgust::

Event Type: Error
Event Source: TermDD
Event Category: None
Event ID: 50
Date: 10/19/2005
Time: 11:29:52 AM
User: N/A
Computer: HOME-PC
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 30 00 02 00 7e 00 ..0...~.
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 2c .......,
0030: 02 f0 80 64 00 06 03 eb .ð?d...ë
0038: 70 1e 08 08 00 00 c7 71 p.....Çq
0040: 5b 44 ca 11 c4 73 12 00 [DÊ.Äs..
0048: 17 00 ef 03 ea 03 01 00 ..ï.ê...
0050: 00 01 04 00 24 00 00 00 ....$...

Anyone have any ideas about what's going on or how to solve this problem?

Thanks!

 

[blemoine]

does the new location have a firewall or IPS that may be blocking you from accessing RDP at your house? that is always a possibility.

 

[Ensign]

Originally posted by: blemoine
does the new location have a firewall or IPS that may be blocking you from accessing RDP at your house? that is always a possibility.

It is definitely possible. How can I test this? Unfortunately, I can't just ask the network people, as they probably wouldn't want to support this.

 

[ktwebb]

From eventid.net
You'll need a subscription to view the links referenced. I have one so if your running windows 2000 on that machine then link by Louis Robertson below is

http://support.microsoft.com/default.aspx?scid=kb;en-us;312313

You can search the knowledge base as MS for these as well.

On another note. These are problems with configuations on machines, either server or client. If you find that this is some kind of network restriction then the first thing to do is talk to your network admins. Nobody in here will help you circumvent those guidelines, hopefully anyway, but there looks to be quite a few resources if it is a local configuration change.

Comments Ionut Marin (Last update 5/6/2004):
- Component: "DATA ENCRYPTION" - As per Microsoft: "Microsoft has added the FIPS Compliant setting to the options for Terminal Services encryption levels in Windows Server 2003. A Windows Server 2003-based server with the encryption level set to FIPS Compliant cannot permit Remote Assistance connections from a computer that is running Microsoft Windows XP or Windows XP Service Pack 1 (SP1)". See M811770 for more details.

Rui Martins (Last update 4/15/2003):
If you have a slow connection it could be also a problem with the MTU size (change that in the registry). Increase to 1100 and test. Increase in steps of 50 each until the connection brokes. And keep in the last value. Of course, backup the registry before.

PaulD
- Component: "DATA ENCRYPTION". A potential race condition between the Icaapi.dll and Rdpwsx.dll dynamic-link libraries (DLLs) may cause the private certificate key on the Terminal Services server not to be synchronized. See M323497.

Louis Robertson
- Component: "X.224". This is a known problem. See M312313.

B-rad
- Component: "DATA ENCRYPTION". A more likely cause to this error is due to a low-bandwidth situation, and decryption is not happening correctly. There is a hotfix for this error produced by Microsoft. See M311371.

Eric W. Bowers
- Component: "DATA ENCRYPTION". This behavior occurs because the Terminal Services client was installed from the Terminal Services client folder before the 128-bit encryption pack was applied to the Terminal Services computer. MSKB article M257894 resolves the issue. Also see M232514 for more information about Terminal Services security.

Kmex Jorgensen
There have been 3 basic causes for your error:

1. Encryption levels defined on the RDP-TCP connection (or ICA, if appropriate), are set too high for the client to successfully negotiate. For example, a client set to Low encryption would be unable to connect to a server with High (or now, FIPS compliant) encryption levels defined. Additionally, XP and XP SP1 clients are currently unable to connect at all if "FIPS compliant" encryption level is set (article in progress on this issue).

To check this, open Terminal Services Configuration (tscc.msc) on the Terminal Server, select the RDP-Tcp connection, select properties, and view the Encryption settings on the General tab. Verify that this is set to Client Compatible, or low, and retest the connection (if needed).

2. Another frequent cause of these problems stems from issues with some registry values in the TermService\Parameters registry key. To this end, could you export the following key: HKLM\System\CurrentControlSet\Services\TermServices\Parameters

After doing this, delete the Certificate, X509 Certificate, and X509 Certificate ID values, and restart the Terminal Server. These values should be regenerated on reboot (but keep the Exported values just in case). This is documented in M323497. The X509 Certificate and X509 Certificate ID values have also been known to cause this problem, so delete them as well. Also see M329896. In 9 out of 10 cases this resolves the issue.

3. The third possibility is that some software you are installing is overwriting some of the files needed for the protocol stream. Schannel.dll, rsaenh.dll, and several others are involved in this process.