Remote Desktop problem

[andyc209]

Tried to connect to a server running windows 2000 from my XP pro machine using remote desktop and everything was OK until about 2 miuntes after connecting when the server's CPU went to 100% and that was it, I had to reboot the server.

Definitley my XP remote desktop as all is OK until I log on. We used to use 2000 clients with Terminal Services but recently bought new computers, hence the XP. Any way to get Termainal Services for the XP machines??

Anyone any ideas why it keeps spiking the processor on the server at 100%

 

[aftertaf]

it isnt the XP client that is to blame, or at least i dont think so.

we have had in the past 10-12 concurrent sessions with clients 9X-NT/2000/XP on 2 TS servers.... never had aproblem like this...

Did you find anything in the event log??

I gather the server was already in production, so nothing to change on the TServer parameters side of things...

Is it up to speed on service packs + patches??


Aftertaf (david)
MCSA 2003

 

[HMarcBower]

Has the problem happened again, or did you try a second time? It might have simply been coincidental to you connecting, but not a result of the connection. Did you get a chance to look at the Task Manager and see what process what taking up all the CPU time?

I think the Remote Desktop client is really just a Terminal Services client that's a little prettier (and can connect to other XP machines).

Marc

 

[andyc209]

Did reboot and got the XP machine to connect to the 2000 machine again and the performance graph hit 100% again - could not do anything else except reboot again.

 

[bcastner]

If either Host or Client machine is running an NVIDIA display adapter either update the drivers, or go into the services applet and stop then set to disabled the Nvidia Helper service.