Problem with Windows Remote Desktop Connection

Message boards : BOINC client : Problem with Windows Remote Desktop Connection
Message board moderation

To post messages, you must log in.

AuthorMessage
Andy Anderson

Send message
Joined: 3 Mar 06
Posts: 2
United States
Message 3320 - Posted: 3 Mar 2006, 19:45:15 UTC

I'm running Windows XP SP 2 with BOINC 5.2.13. I have BOINC running based on preferences.

I often want to login remotely with Remote Desktop Connection, but when the Boinc screensaver is running, it doesn't recognize that there is now a "user" present, so the core application continues to run. The desktop is black and I can see the core application's button in the taskbar, but it's extraordinarily slow to respond to mouse and keyboard, presumably because it's using so much CPU time. The same problem doesn't exist with the standard screensavers.

When I return to the local keyboard BOINC behaves properly (i.e. it suspends itself).

There is no problem when I use "run always" mode, it is responsive to user activity whether local or remote (but there's no pretty screensaver...).

Anything I can do to fix this? Or is this something that needs to be fixed in BOINC?
ID: 3320 · Report as offensive
Scott DeBruyn

Send message
Joined: 21 Mar 06
Posts: 1
United States
Message 3570 - Posted: 21 Mar 2006, 0:56:15 UTC

I've been noting this same Windows Remote Access problems. I have 5 machines onsite that I've been converting over from the old Setiathome to the new Boinc and started with the machines I use regularly which include ones I connect to remotely (garage shop business with access to PC's in the house). I'm seeing identical symptoms to Andy here and suspect it's Boinc as Setiathome didn't cause the problem. I'll add one other symptom that may help. If I attempt to log on repeatedly to the same machine, the progress towards getting a remote session started progresses incrementally for 3-4 attempts then gets no further than one completed screen from the remote PC but does not show Boinc or Seti. Looking locally at the remote PC after an attempt shows the same as it would if the machine had been logged into and out of remotely (user login screen). If I then login locally, there is an odd delay with a black screen before coming up. If I then go back to connecting remotely, it works fine and I can remain connected all day with the remote connection. Hope this all helps and it would be nice not to have to make the trek from the garage to the other end of the house to clear what I consider a screensaver. I'm sure there are plenty of other users that use multiple PC's in similar ways, I mean it is 'Distibuted Computing' that for me is more important than Seti. This must apply to others too.
ID: 3570 · Report as offensive

Message boards : BOINC client : Problem with Windows Remote Desktop Connection

Copyright © 2024 University of California.
Permission is granted to copy, distribute and/or modify this document under the terms of the GNU Free Documentation License, Version 1.2 or any later version published by the Free Software Foundation.