Remote Desktop Error with Shell Version 6.0.6001

J

jms88

When I try to connect to an NT4.0 Server, Terminal Server Edition with the
latest Remote Desktop Client, I get: "Because of a protocol error, this
session will be disconnected. Please try connecting to the remote computer
again."

However, I can connect to said server from a machine running Shell version
6.0, build 6000, Control version 6.0.6000, and below.

This connection problem seems to be related to the latest version of RDC. If
there a workaround, or a fix so I can connect to this legacy terminal server?
I have tried the "Themes" fix to no avail. I also cannot downgrade the RDC on
the XP SP3, or Vista SP1 machines, as Windows prevents me from doing so.
 
J

jms88

It is not installed on NT4.0. Sorry for the confusion.

I am trying to connect to an NT4.0 Server with a client (XP Pro SP3 or Vista
SP1) that is running the latest RDC.
 
J

jms88

I did see that KB, and that patch has been applied, but the error still
occurs, even using the /admin switch.

This is a frustrating issue!
 
J

jms88

I finally had enough. I copied mstsc.exe and mstscax.dll from an XP SP2
machine, put them in a new directory on my file server. I can run the
connection from there.

I don't like it, but it works and fortunately the volume of use is low on
that legacy NT 4 TS, so the users can just deal with it!
 
T

Thee Chicago Wolf

I finally had enough. I copied mstsc.exe and mstscax.dll from an XP SP2
machine, put them in a new directory on my file server. I can run the
connection from there.

I don't like it, but it works and fortunately the volume of use is low on
that legacy NT 4 TS, so the users can just deal with it!

You beat me to the punch. I was going to tell you to copy the RDP 6.0
files from you SP2 backup folder in C:\Windows.

- Thee Chicago Wolf
 
T

Thee Chicago Wolf

I finally had enough. I copied mstsc.exe and mstscax.dll from an XP SP2
machine, put them in a new directory on my file server. I can run the
connection from there.

I don't like it, but it works and fortunately the volume of use is low on
that legacy NT 4 TS, so the users can just deal with it!

You may also want to try the hotfix from
http://support.microsoft.com/kb/956072 and the registry fix mentioned
in it as well.

- Thee Chicago Wolf
 

Ask a Question

Want to reply to this thread or ask your own question?

You'll need to choose a username for the site, which only take a couple of moments. After that, you can post your question and our members will help you out.

Ask a Question

Top