Install SP2 to Win XP-Pro. Now, no connect to client
3 Dec 2005 16:59:41 UTC
Topic 190284
(moderation:
BOINC was running fine. "Updated" to SP-2 and now BONC cannot connect.
Firewall is off. Just for the heck of it/to be safe, added both BOINC.mgr and BOINC as "exceptions." Am using a router (as before).
Did a clean install and connection the client fails from startup. Added "localhost" VIA Files section, password appears but connection still fails.
Any clues out there?
Chuck
Hinterlands, VA
Install SP2 to Win XP-Pro. Now, no connect to client
)
When you say "fails to connect", do you mean to Localhost or to the server? If to the server, then the firewall might be the issue, unless the firewall were "over protective" and blocks internal traffic. If it's turned off, then obviously it's not that. So I'm assuming you're referring to "localhost", the lower-right corner of the BOINC Manager window says "disconnected" instead of the normal "Connected to localhost".
If you are not running V5.2.13, the first step is to download and install that version as it handles "localhost" connection problems better. The "localhost" problem occurs whenever BOINC Manager cannot communicate with boinc.exe, the daemon. This is often because of BOINC trying to start up "too early" in the Windows boot process, but if that were the case, quitting and relaunching would be solving it.
If under Options, Connections, you have "Automatically detect", you might change to "Use my LAN" - that sometimes (but admittedly not often) helps.
You mention password - there is a "randomly assigned" password, contained in the file gui_rpc_auth.cfg, for "localhost". Normally this only matters if you are remotely controlling the computer from another one, but if you are being _asked_ for a password, you can either copy/paste this random string and see if that gets you past the problem, or you can edit the file with Notepad and change the password. If you do this, be sure to leave the "return" at the end of the line intact. If that works once but it _continues_ to ask for a password every time, someone can help you solve that.
One other thing that causes some people problems is if some "other" Windows program grabs port 1043 before BOINC can. If you know how to check for this, you can find and fix the offending program; again, if that's the problem, someone can help you solve it. There are a couple of threads on this over on SETI, I don't recall exactly which programs are known to sometimes do this...
Give us all the information you can, we'll be happy to help!