I recently switched over to Boinc from the old Seti and had to fight the "won't connect to localhost" battle to get it to run. Took 4 or 5 hours of my time - I'm not real bright. Got it going finally and then had to reboot to install other software. Now I'm faced with the "can't connect to Boinc client" battle. After several more hours, I decided to give up and run an aquarium screensaver instead. Then the solution dawned on me. I have un-installed Boinc (so the screensaver error messages won't taunt me) and I'm going to use patience. I'll check back in a several months and download version ".20" with all the fixes. When Boinc is finally ready - I'll be there!

---

Tom,

We're sorry to have you go, and hope to see you back soon. In the interim, to fend off Distributed Computing Withdrawal Syndrome, maybe you'd like to look at a non-Boinc DC project, such as Folding@Home. I've been a long time away from Folding, so I don't know whether they've had any problems there recently, but in my limited time there, I didn't encounter any. That's the best I can do for you. Good luck!

Michael

---

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

Tom,

We're sorry to have you go, and hope to see you back soon. In the interim, to fend off Distributed Computing Withdrawal Syndrome, maybe you'd like to look at a non-Boinc DC project, such as Folding@Home. I've been a long time away from Folding, so I don't know whether they've had any problems there recently, but in my limited time there, I didn't encounter any. That's the best I can do for you. Good luck!

Michael

Hello again Michael! I'm not leaving, just letting the software developers finish their job. The distributed computing idea is so powerful that it will certainly flourish. If Boinc can't get it right then someone else will. The researchers will be there and I'll join them! I'll keep an eye on the message board to see where we stand. Thanks again. Tom

---

Someplace in all the stopping with BOINC and all, did someone tell you to try either of the following (simple, but effective) solutions?

Go to your BOINC directory.
Find the file called gui_rpc_auth.cfg
Open it with Notepad or another text editor.
Delete everything in it.
Leave an empty carriage return (meaning hit Enter once so you have an empty line).
Save the file.

Or:
Stop BOINC from running.
Go to your BOINC directory.
Find the file called gui_rpc_auth.cfg
Delete it.
Start Boinc.

That will usually stop all the problems with "won't connect to localhost"/"Can't connect to the Boinc client".

All the two messages were saying was that Boinc Manager (the GUI) could not communicate with Boinc (the daemon).

---

Someplace in all the stopping with BOINC and all, did someone tell you to try either of the following (simple, but effective) solutions?

Jord,

No, I didn't. As you'll see here, the fix(es) suggested appear(ed) to have solved the problem, and then when he posted in this thread, it was apparently too late.
I have added the "gui_rpc_auth.cfg" fix to my "toolkit" recently, just hadn't hit Tom with that one yet. :-{
edit - Hope I get a little bettar at this someday. (sigh)

Michael

---

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

Someplace in all the stopping with BOINC and all, did someone tell you to try either of the following (simple, but effective) solutions?

Jord,

No, I didn't. As you'll see here, the fix(es) suggested appear(ed) to have solved the problem, and then when he posted in this thread, it was apparently too late.
I have added the "gui_rpc_auth.cfg" fix to my "toolkit" recently, just hadn't hit Tom with that one yet. :-{
edit - Hope I get a little bettar at this someday. (sigh)

Michael

Hey Michael, Jord. Don't be upset! I really appreciate your help, but "making" software run is not how I spend my time (usually). I don't know how to find the Boinc directory, open it in a text editor, or how to then delete it. I just figure that the folks at Boinc will get it fixed and then I'll use it. Hang in there Michael! Tom.

---