Lots of Remote Desktop problems..
Posted by admin on Feb 6th, 2007
Hi All,Wanted to see if anyone knows of fixes workarounds for my problems with Remote Desktop 6.Target PC is a Vista Business machine. I've installed RD6 client for XP onto my XP Pro machine.However whenever I connect across, the CPU of my XP Pro machine spikes (sometimes after 2 mins or so) to 100%, and the memory for the terminal client process grows to > 400Mb...Also, quite often on the remote PC, I get messages about not being able to connect. Various messages appear on the remote logon screen. Sometimes I just get a "Welcome" screen with a static circle, other times a spinning circle.. but no access. I usually have to wait 10 mins or so before trying again.Fed up with the whole thing... Tried to report the issues to Microsoft, only to be told that I'd have to contact Microsoft UK (due to the "localised" versions) what exactly is localised about RDP ?? So I'm expected to spend cash on the premium rate phones to try and report a bug. Its a joke.So then I've tried to install RealVNC.. only find that doesn't work with Vista yet.. I give up..
Feb 10th, 2007 at 10:24 am
There could be a whole host of things causing the RDP issues, but Vista does work. I use it all the time to access my main office PC (Vista Ultimate) and it works like a charm. Sounds more like a networking issue to me...
Feb 14th, 2007 at 07:17 pm
Running Vista 64 clean install on formatted HD. One of the other HDs (I have three) had XP Pro installed. Now I can't reformat the XP Pro HD, as Vista refuses to delete the main system folders. If unplug that HD before boot up, I get an error message saying that BootMgr is missing. The same thing happens if I fail to keep the Vista CD in the drive whilst booting up. Arrrgh!I did have a problem with the Vista Boot Manager appearing, asking which version of Windows I wanted to run, but I've managed to get that changed so, supposedly, it only recognises that Vista is the only OS. (I used a program called VistaBoot).Any suggestions for this? Thanks Paul
Feb 16th, 2007 at 05:23 pm
Well... no networking issue would explain the client eating 100% CPU, and >400Mb of ram..Now the interesting part (ignoring the client issues).. is that my target machine does have multiple NICs. I disabled the firewall to rule that out as an issue, and I do actually get connected as I see the remote "Welcome" spinning wheel/not spinning wheel.. So I think in this bug, whatever it is has to be on the target (vista) machine.I can also RDP into a Wk3 sbs server from the same client, and don't have the same issues (the XP client still eats memory though)..A.aftermath wrote: