Almost two months ago I transitioned from the "old" SETI to BOINC and overcame the "can't connect to local host..." problem only to encounter the "can't connect to BOINC client..." problem. After messing around with this for a while, I realized that I don't have the patience or computer knowledge to get the program running properly. I decided to just relax and come back "later" when the problems had been corrected. 45 days later, they still haven't been fixed. I can't find any mention of the problem on the BOINC web site. Does anyone know why? Does anyone know when they plan to fix it? I really want to donate my computer time but can't decide if it's worth hanging around. Any comments?

---

Almost two months ago I transitioned from the "old" SETI to BOINC and overcame the "can't connect to local host..." problem only to encounter the "can't connect to BOINC client..." problem. After messing around with this for a while, I realized that I don't have the patience or computer knowledge to get the program running properly. I decided to just relax and come back "later" when the problems had been corrected. 45 days later, they still haven't been fixed. I can't find any mention of the problem on the BOINC web site. Does anyone know why? Does anyone know when they plan to fix it? I really want to donate my computer time but can't decide if it's worth hanging around. Any comments?

Open the files menu select computer - leave blank, click oK.
else enter localhost or 127.0.0.1, click oK.

Your firewall could be blocking comunication between boincmgr.exe, boinccmd.exe and boinc.scr has they need local access on ports 1043 and 31416.
boinc.exe needs access on ports 80 and 443, local access on ports 1043 and 31416.

---

Boinc V 7.4.36
Win7 i5 3.33G 4GB NVidia 470

Hello Aurora! Thanks for the input. I've been through all this. It's not my firewall and, after much grinding of teeth, I've learned how to find the "gui_rpc_auth.config" file and modify it using a text editor. But every time I have to shut down or re-boot it takes multiple attempts at down-loading and modifying to get it to work again. Sometimes it works and sometimes it doesn't. My real question is is this the future of distributed computing? Do they plan to fix the software? Do they plan to tell us what they plan to do? I'm just curious. Thanks again for your time. Tom.

---

Hello Aurora! Thanks for the input. I've been through all this. It's not my firewall and, after much grinding of teeth, I've learned how to find the "gui_rpc_auth.config" file and modify it using a text editor. But every time I have to shut down or re-boot it takes multiple attempts at down-loading and modifying to get it to work again. Sometimes it works and sometimes it doesn't. My real question is is this the future of distributed computing? Do they plan to fix the software? Do they plan to tell us what they plan to do? I'm just curious. Thanks again for your time. Tom.

Have you tried any of the alpha available on this page? I'm in the process of downloading the latest test version 5.3.15 posted in the last 24 hr.

The standard caveat applies --- this is a very early test version and can contain unexpected problems.

---

Boinc V 7.4.36
Win7 i5 3.33G 4GB NVidia 470

Hello Aurora! Thanks for the input. I've been through all this. It's not my firewall and, after much grinding of teeth, I've learned how to find the "gui_rpc_auth.config" file and modify it using a text editor. But every time I have to shut down or re-boot it takes multiple attempts at down-loading and modifying to get it to work again. Sometimes it works and sometimes it doesn't. My real question is is this the future of distributed computing? Do they plan to fix the software? Do they plan to tell us what they plan to do? I'm just curious. Thanks again for your time. Tom.

Have you tried any of the alpha available on this page? I'm in the process of downloading the latest test version 5.3.15 posted in the last 24 hr.

The standard caveat applies --- this is a very early test version and can contain unexpected problems.

Thanks again! I may just give it a try. The unexpected problems shouldn't be any worse than the expected ones in 5.3.13.

---