XP SP2 and Remote Desktop

[Terry]

-----Original Message-----
I'm setting up a GPO to open Remote Desktop on all clients in our company. I
have followed all the instructions I can find on MS website. Port 3389 is
open on the client via the GPO. However, each time we try to use Remote
Desktop to access the client we get a message saying the remote computer has
ended the connection.

What am I overlooking?
.
It is port 3398 not 3389.................

 

[Guest]

No way!! All documentation says 3389 - I will change my settings, retry and
let you know.

 

[Guest]

Terry: thank you very much for your suggestion but it did not work.
Very frustrating problem.

 

[Guest]

I had the sam problem, I have uninstalled service pack 2 and now my remote
connection now works again. The computer that would not take the remote
connection is the only computer that i installed SP2 on from the windows
update site. The other 2 computer never had a problem cause i used the SP2
CD on them.
So i wonder if thats the problem from getting it thru the Windows update site
I have not yet to uninstalled it again and reinstalled it thru the web to
see if it changes again but planning to to see it i can recreate the problem.
Bernie

 

[Colin Pimlott]

I got round this problem by replacing the termsrv.dll in system32
folder with the original one saved in the SP2 uninstall folder.
You need to reboot safe mode to do this.
We have some pc's working ok with the new dll and some that only work
with the older one. All the registry settings in
HKLM\SYSTEM\CurrentControlSet\Services\TermService are the same
(except the Certificate key in Parameters)
The only thing that is different is that the ones that work had SP1
before SP2.
I have tried removing SP2 to do the SP1 and then SP2 but that didn't
work.
It would seem that once you have done the SP-none to SP2, that's it.
Your stuffed!

C

 

[Mike Trill]

Colin,

Thanks for the TIP! I'll try that tonight. I've been running remote
desktop on a virtual PC to connect, works okay but its a pain.

It is a shame that Microsoft have not taken an interest in this issue.
I logged a call with microsoft support, got an incident number, and
the advice was uninstall SP2 untill the problem is fixed. Case closed



Mike