Question Locked

Is there a simple way to...

0 helpful
123 replies
Closed to new repliesThis discussion is closed. It stays readable, but it takes no new replies.

This is page 2 of the discussion. Read the opening post

123 replies

by the 'g-man.'

Enabling Remote Desktop using regedit

1. Run REGEDIT from Start>Run

2. Browse to HKEY_LOCAL_MACHINE\SYSTEM\CurrentControlSet\Control\Terminal Server, in the right panel, seelct fDenyTSConnection (REG_DWORD). Change the value data from 1 (Remote Desktop disabled) to 0 (Remote Desktop enabled).

3. Close the regeidt.

4. Reboot

by the 'g-man.'

Have you updated them recently?

Could you update them?
and / or
Try them when set to just basic SVGA?

Remote Desktop can be picky with some graphic drivers.

by var1016

Computer "A", which is the one I want to access the other one from (i.e. I think not the host) has a Nvidia 8600GT graphics card. Computer "B", the one I would like to access has a Nvidia 8400 GE (or GS perhaps) graphics card. All drivers are up to date - in fact I think they use the same drivers.

Paul

by the 'g-man.'

Here is the Fix :-)

This is a registry fix that increases the size of the session image space. Add the following key:

[HKEY_LOCAL_MACHINE\SYSTEM\CurrentControlSet\Control\Session Manager\Memory Management]

"SessionImageSize"=dword:00000020

by var1016

Thanks for your tip about adding a registry key.

Whilst I can modify existing keys I do not fully understand how to make a new one. All the values in the list read something like:
0x00000030(0)

The value you gave doesn't look like this, and I have learned through bitter experience that minor changes can result in a machine that will not boot, and this summer I have done more than enough reinstallations!

Paul

by the 'g-man.'

Backup the Registry First (as always)

Navigate to:

[HKEY_LOCAL_MACHINE\SYSTEM\CurrentControlSet\Control\Session Manager\Memory Management]

Right click on a blank space on the left secect New then DWord

Enter the DWord Text - SessionImageSize
Then
Edit the DWord to read 00000020

by the 'g-man.'

I see no reply but you are posting away in other places on site.

by var1016

Just a bit busy at the moment. I'll report back of course very soon.

Paul

by var1016

I put in the numbers you suggested and it said "invalid Dword value"

Note: in "change binary value" the numbers were disposed thus:

0000 00 00 00

Before I changed them to 0000 00 00 20 and this gave me the error message.

Paul

by var1016

Brilliant

Finally I have Remote Desktop working.

Incredible...

All I need now is to change the keyboard setting from French to English!!!

Many thanks,

Paul

by rob miners

Verify that Terminal Services is running on both of the XP Pro desktops:

You can verify if the Terminal Services is running on the desktop PC by executing the services.msc command from the Windows XP Start | Run command window. The Server status should be Started.

Verify the PC's are listening on TCP Port 3389:

From the Windows XP desktop Start | Run command window execute the cmd command. At the command line prompt type the command netstat -a and verify the PC is listening on TCP Port 3389.

Windows XP Pro Remote Desktop
configuration, use and troubleshooting help and tips

http://theillustratednetwork.mvps.org/RemoteDesktop/RemoteDesktopSetupandTroubleshooting.html#Troubleshooting

by var1016

Thanks for this. I made the enquiries and all is present and correct!

Regards

Paul

by the 'g-man.'

Copy the below to notepad, save using 'save as', selecting 'all file types' in the save as type box. Call the file rdpfix.reg. Close notedpad. Find and double click the saved file to add it to your registry saying yes when propmted. Reboot after and try remote desktop.

Windows Registry Editor Version 5.00

[HKEY_LOCAL_MACHINE\SYSTEM\CurrentControlSet\Control\Session Manager\Memory Management]

"SessionImageSize"=dword:00000020

by var1016

G man has cracked it.

There is NOT a simple way, but we got there in the end.

Thanks to all who contributed.

Note, I am still keen to learn about virtualisation!

Best wishes, and thanks again<

Paul

by rob miners

I did notice that G Man was pretty persistent. He has done an excellent job. ;)

Rob

by var1016

Yes,

As a very poor junior apprentice, I was fascinated that something to do with the Nvidia graphics cards could interfere with network stuff and even more surprised that a registry edit would cure the problem.

Incidentally, it was necessary to do the registry edit on both of the computers - they do both have Nvidia cards (running at nearly 50?C as usual...and I'm not even a "gamer"!!).

All the best

Paul

by rob miners

that this doesn't happen very often. I think that it was very clever of G-Man to work this out. ;)

G-Man also has a couple of posts that would look good with a Thumb just for the effort that was put in. ;)

< speel chucker not working >

Rob

by the 'g-man.'

I know it is strange but remember remote desktop is mostly about display. In this case capturing another systems session and letting you interact with it.

All the best :-)

by var1016

Yes I think I have that in mind now. Interestingly talking of displays, when I have the remote desktop up on screen, the "wallpaper" is not there.

Of course this is no problem, but I wondered if it is typical?

Best wishes

Paul

by the 'g-man.'

Look at the remote desktop options when connecting - Options, Experience Tab

by var1016

Yes, that brought back the wallpaper - thanks.

Interestingly, the IP address of the computer I am accessing via remote desktop has remained the same for three days - this makes things so much easier!

Best wishes

Paul

This discussion is closed to new replies.