BOINC(5.2.8) automatically starts when my computer starts (Windows XP). At this time, I get an error message indicating the connection failed. In the lower right BOINC indicates disconnected. As far as I can tell:
1. There is no way to have BOINC retry. There is no menu option that works and it does not retry on its own even if there is work to send/recieve.
2. The only way I can get reconnected is to stop and restart BOINC. This defeats the purpose of having it automatically restart.

Also - My connection option indicates that BOINC should use my LAN connection.

What am I missing? I would like to get this software to function automatically.

Thanks,
Chuck

The problem you describe was one of the ones worked on in V5.2.10 through 5.2.13 - it is _hopefully_ fixed in 5.2.13. The way to retry with the older versions is to go to the "Select Computer" option in the File menu and pick "Localhost", normally with a blank password.

The connection that is failing is between BOINC Manager and the boinc.exe daemon, and not the internet connection to the servers. It typically appears when BOINC Manager runs "too early" in the Windows startup sequence, and the earlier patch to prevent it was a 3rd-party utility that delayed BOINC starting up. There are still issues with other Windows software occupying port 1043, that is used for this connection, but that is a rarer case.

---

I think I am having a similar problem but I have 5.2.13 At random times whenever I restart my computer I will get a message "BOINC manager is unable to connect to a BOINC client..." The only way that I have found that resolves the issue is to completly restart my comp. restarting teh app does nothing. Any ideas?

Also, This probably has nothing to do with this particular problem, maybe, but I have also been have random restarts. Usually occurs when another program is trying to open: firefox, media player, etc...

thanks,
Tim

---

Same connection failure on my Windows 2000 with boinc manager in startup folder.
This happens everytime I either switch on or reboot.
Only thing I can do is to reply to the connection failed pop-up window, and then quit the boinc manager (It will not allow anything to be changed and no menus work (this is boinc version 5.2.8)

---

(this is boinc version 5.2.8)

I'd definitely try an upgrade. It may still not work, but there were some fixes applied after that version.

---

I have the same problem, Win XP w/Zonealarm Security Suite. V is 5.2.13.

Won't connect to local host. I tried logging in to localhost with no password as suggested below. No luck.

---

I have the same problem, Win XP w/Zonealarm Security Suite. V is 5.2.13.

Won't connect to local host. I tried logging in to localhost with no password as suggested below. No luck.

I believe that the localhost connection is internal, Boinc's elements inter-communicating.. Upshot is, Boinc needs access to the net through port 80, and also access to ports 1043(?) and pi, port 31416.

---

"The arc of history is long, but it bends toward Justice"

Several possibilities here. Most common (with 5.2.13) is some other Windows application grabbing port 1043 on startup. I don't recall the "likely offenders", but I know there's a thread at SETI about it. I'm not Windows-savvy enough to be able to tell you how to see which programs are holding which ports... And obviously if some firewall is blocking internal use of port 1043, the two can't communicate.

Another is if the 'blank' password doesn't work for connecting to Localhost, either the boinc.exe program isn't running for some reason (check with Task Manager) or you need to copy/paste the randomly-assigned password (intended for controlling one computer remotely from another) that is stored in the file gui_rpc_auth.cfg. That should be a one-time thing, and only if you've gotten into this odd error loop, but if it happens often, you can change the password with Notepad to something you prefer - be sure to leave the "return" at the end of the line - until the underlying problem can be solved.

If you're signed up with SETI, your best bet is to post over there, as there are people there that are very familiar with this problem, due to the issues 5.2.10 through 5.2.12 had. V5.2.13 solved most of them, but obviously there are still a few!

---