Remote Desktop Connection and XP Service Pack 3

Same problem here. SP3 and then I cannot do an RDP connection to this XP Pro
Workstation just upgraded. RDP client freezes. Black Screen. Then connection
error. Agh!! For me, when I logged in with RDP session that was not same as
Host machines current login, all worked well. Eg) I was having trouble
connecting the RDP session as "User1". Note, at host, I was also logged in
locally as "User1". While logged in as User1 at local machine I created a new
user "User2". I then went to remote machine and connected RDP session to host
as "User2". All worked.
SP3 has buggered something up and I'm a bit frustrated, many hours wasted.
Something to do with profiles and not allowing multiple instances of same
login.

Does someone have a fix for this problem induced by SP3?
At least I have a workaround for now...

Any help appreciated.







"MattM@NIST" wrote:

> I noticed this problem today as well when deploying SP3 to my users
> computers. I would connect to a computer (computer alpha) from my computer
> (computer beta) via mstsc and install SP3. Upon reboot, I could not connect
> to the machine. I had to go log in at the machine and then I could connect
> remotely again. I happened to notice that for some reason, the XP SP3
> install was turning off the Windows Firewall/ICS service. I restarted the
> service and tried logging out and connecting remotely again and it worked.
> Not sure if this will fix everyone's problem, but it fixed mine and thought I
> would offer it.
>
> "Rogan Josh" wrote:
>
> > Hi, All!
> >
> > I am experiencing an issue using Remote Desktop Connection (RDC) after
> > installing XP Service Pack 3. Connecting to servers (Win2003) works without
> > a problem; however, attempting to use Remote Desktop Connection between PCs
> > running Windows XP Pro does not work unless the user has already logged onto
> > the machine locally. For example, if a PC is powered up to the login screen
> > and a user attempts to use Remote Desktop Connection to connect to the
> > machine, then the connection will fail. Now, if a user logs into the machine
> > locally and then that same user attempts to login to the machine using Remote
> > Desktop Connection, then the connection will succeed. This phenomenon did
> > not exist prior to the installation of the XP SP3 update.
> >
> > XP Service Pack 3 contained an update to the Remote Desktop Protocol used in
> > Windows which may be part of the problem. Has anyone else experienced this
> > type of behavior from the RDC client?
> >
> > Any help would be greatly appreciated!
> >
> > Thanks in advance!
> >

I can't follow this appraoch as my SP3 is a new install not an update. What
is happening with me is that I am being rejected through "incorrect user name
and password" despite both being correct. It is also happening in net work
mapping. It is as if my keys ar not being recorded correctly.

"detlev.pohlig@gmx.net" wrote:

> On 31 Jul., 13:04, BigB <B... RemoveThis @discussions.microsoft.com> wrote:
> > After rolling back to the restore point whereXPSP3was not installed, RDC
> > is back again.
> > B
> >
> >
> >
> > "BigB" wrote:
> > > Hi, I have a similar issue:
> > > I can not use Remote Desktop after installing WindowsXPSP3on the target
> > > machine.
> > > I accessed my taget machine via RDC, installedXPSP3(using an RD
> > > connection). It finished without any problems, but since then, I can not
> > > access it via RDC (regardless of the client operating system {Vista Business
> > > 32bit, Windows Server 2003}).
> >
> > > Does anyone have a solution?
> > > B
> >
> > > "P+" wrote:
> >
> > > > It certainly is not an isolated issue, then. I am experiencing exactly the
> > > > same symptoms.
> >
> > > > "·" wrote:
> >
> > > > > I have a similar problem except that I cannot connect whether or not a
> > > > > user has logged into theSP3machine. Everything was fine prior toSP3.
> >
> > > > > I updated to theRDP6.1 client on my existing SP2 system (
> > > > >http://support.microsoft.com/?kbid=952155), but it hasn't seemed to
> > > > > help.
> >
> > > > > Rogan Josh wrote:
> >
> > > > > > Hi, All!
> >
> > > > > > I am experiencing an issue using Remote Desktop Connection (RDC) after
> > > > > > installingXPService Pack 3. Connecting to servers (Win2003) works
> > > > > > without a problem; however, attempting to use Remote Desktop
> > > > > > Connection between PCs running WindowsXPPro does not work unless
> > > > > > the user has already logged onto the machine locally. For example,
> > > > > > if a PC is powered up to the login screen and a user attempts to use
> > > > > > Remote Desktop Connection to connect to the machine, then the
> > > > > > connection will fail. Now, if a user logs into the machine locally
> > > > > > and then that same user attempts to login to the machine using Remote
> > > > > > Desktop Connection, then the connection will succeed. This
> > > > > > phenomenon did not exist prior to the installation of theXPSP3
> > > > > > update.
> >
> > > > > >XPService Pack 3 contained an update to the Remote Desktop Protocol
> > > > > > used in Windows which may be part of the problem. Has anyone else
> > > > > > experienced this type of behavior from the RDC client?
> >
> > > > > > Any help would be greatly appreciated!
> >
> > > > > > Thanks in advance!- Zitierten Text ausblenden -
> >
> > - Zitierten Text anzeigen -
> Hi All,
>
> I've had the following problem:
> I tried to install service pack 3 on a XP SP2 MUI with KB925877
> installed. Installation has aborted with Error. In a newsgroup I found
> the hint to uninstall the Patch but my uninstallation directory was
> deleted long time ago. So I deleted the registry entries that it was
> installed and SP3 installation ran perfectly.
> After a restart I tried to start a RDP connection to one of my
> servers, but nothing happened. When starting the Taskmanager I saw
> that the process has started.
>
> Solution:
> - Stopped the process mstsc.exe
> - Created a new folder "RDP" in %windir%
> - Copied "mstsc.exe" and "mstscax.dll" from "C:\Windows\
> $NtServicePackUninstall$" to this folder
> - Copied the folder "en-US" "from C:\Windows\System32" to this folder
> - Copied the "mstsc.exe.mui" and "mstscax.dll.mui" from "C:\Windows\
> $NtServicePackUninstall$" to "C:\Windows\RDP\en-US"
> - Changed my RDP shortcut to ""C:\Windows\RDP\mstsc.exe"
>
> Now I can use the 6.0 Version of RDP without problems. Maybe the next
> update will destroy my shortcut in the start menu, but I copied it to
> the desktop as well.
> Note: At this time it is not possible to reinstall any version of RDP
> when SP3 is installed. Hope this will be changed by MS.
>
> I hope this helps.
>
> (* nobody's worthless. He can still be a bad example *)
>

Hi,

I had the same problem of not being able to remotely connect to a PC unless there was someone already logged into it.

I trawled the groups and found a couple of things to do which worked for me.

Turning these two services to automatic on the remote PC.

NLA - Network Location Awareness

and

Terminal Services

Hope this helps.

Franc.

detlev.pohlig wrote:

On 31 Jul., 13:04, BigB Hi All, I've had the following problem: I tried to install service pack 3 on a XP SP2 MUI with KB925877 installed. Installation has aborted with Error. In a newsgroup I found the hint to uninstall the Patch but my uninstallation directory was deleted long time ago. So I deleted the registry entries that it was installed and SP3 installation ran perfectly. After a restart I tried to start a RDP connection to one of my servers, but nothing happened. When starting the Taskmanager I saw that the process has started.

While this is not the original problem here, I had this, too. And while your solution of using the old version works, the better solution would be to really solve the problem. And that you needed the .enu-files gave me the hint.

If you use an english XP with MUI Pack, you need the SP3-MUI update after installing SP3. Without it, the RemoteDesktop client or even the IE-Plugin-Manager won't work, together with other things. So simply go to the Microsoft page, search for "XP SP3 MUI" and install that update. And immediately your RD-client will work again.

The other solution would be to switch your system language back to english.

I don't know if this is the same problem or not, but I've found that if I use the target machine's IP address rather than its name, I get a reliable RDP connection into an XP Pro machine with SP3 from either a pro or home XP machine. I haven't let Vista in here yet. We have 8 XP machines here in our home office and four NAS boxes (two Netgear and two Thecus). All this plays together nicely without a Windows Server to control it all.

Well after months of trying to figure this out finally got it working. It also fixed a problem with a particular printer driver crashing. It makes sense as the explanation of the fix says it's for both video and printer drivers. I would have never guessed this was the problem. Should be checking event.log files for errors in the future. Since it was such a find, I wanted to post it on other sites to get the word out. The solution was this taken from Windows IT Pro forums:

=============================================
Along those lines, you gave me an idea to check NVidia for any known issues. I found a blog mentioning the same issue but with an error "RDPDD.dll failed to load" in the event log. Sure enough, when I checked the event log on the target machine I had the same error. Though I'd expect this problem to be solved with the latest driver, it seems it's existed atleast since May of 2008 and version 175.16.

The following is a quote from Nvidia's site:

"The root of the problem is that the session image space is too small and it can't load any more drivers into it. The session image space is shared for the display driver drivers and printer drivers. rdpdd = remote desktop protocol display driver.

You can fix this bug by increasing the size of the session image space via a registry key. Add the following key:
[HKEY_LOCAL_MACHINESYSTEMCurrentControlSetControlSession ManagerMemory Management]

"SessionImageSize"=dword:00000020

0x20 == 32 MB works on my system anyway."


I added that registry key, rebooted and now it works... I still have no clue why one day it would suddenly stop working but that fixed it and I'm happy with that.

===============================================