I have been running 6.10.29 on four computers without any problems.

I have recently installed an ATI5970 into a box already running a GTX260. when I restarted the computer Boinc ran but I realised I forgot to install the drivers for the 5970. I did that but now BOINC is stuck withe message Connecting to Host. I uninstalled 3.10.29 and reinstalled 6.10.18, in case that made a difference but it did not.

The operating system is Win 7. I know others have run two different cards, so I am guessing I need to make a manual change to some config file????

I am reluctant to pull the GTX260 because I need it to run Seti.

Thanks

---

OK, I solved it, finally.

BOINC 6.10.29 and Cal 9.12 Hotfix is the magic combination.
I also needed to detach and reattach the projects affected. Seti and Milkyway.

---

Yes after scowering the message boards...I have the same problems on three of my machines..no work...at the bottom "connecting to local..." the manager will flash my info then disconect...(understand the reason now) So in the past i have tottaly detached my router and still the same problem..I was curious if it cud be my ISP..but i have been crunching on this ISP for three years. In fact amy 3800 AMD is down right now and dont want to lose my surplus. Ill read on..
All machines running XP all curently up todate on all Updates.

---

Do What Tho Will Shall Be The Whole Of The Law
Proud Member Of Team Carl Sagan.

[img}http://allprojectstats.com/su1639330l8-2a10-1-0.png[/img]

All rite.. I have worked on the AMD 3800 puter..have made sure ports 31416,80,443 ports are open..and to no avail ver.6.6.8 still same problem.while watching task manager and seeing boinc.exe flash on and off(yes all the while rebooting puter after every change).ok installed ver 5.5...went back and installed 6.10. and now the program runs..so i dont know..I think i will run out all my cach and use the OLD boinc untill something can be fixed?

---

Do What Tho Will Shall Be The Whole Of The Law
Proud Member Of Team Carl Sagan.

[img}http://allprojectstats.com/su1639330l8-2a10-1-0.png[/img]

If you have a LARGE cache of WUs, then BOINC can take a long time to communicate the info between the "client part" and the "gui part".
As the refresh rate for the list of WUs is one minute, if it takes BOINC longer than this, then the connection between the gui (Manager), and the client gets lost.

It was for this reason that a new button was introduced in recent versions. Clicking it will allow the Manager to only display the WUs being worked on, not everything that you have.
Not sure what the button is called, but it's been mentioned in the last few weeks if you want to search. Or just have a look around the Manager.

If you have a LARGE cache of WUs, then BOINC can take a long time to communicate the info between the "client part" and the "gui part".
As the refresh rate for the list of WUs is one minute, if it takes BOINC longer than this, then the connection between the gui (Manager), and the client gets lost.

I think it's one second, not one minute ;-)

It was for this reason that a new button was introduced in recent versions. Clicking it will allow the Manager to only display the WUs being worked on, not everything that you have.
Not sure what the button is called, but it's been mentioned in the last few weeks if you want to search. Or just have a look around the Manager.

That would be "Show active tasks" or "Show all tasks" respectively, in the Tasks tab, IIRC.

Gruß,
Gundolf

Ahh. 1 second sounds a bit 'worse' for a large cache. Now I just have to try and remember it. :(

I just started having the same problem on 1 of 2 comps. It seems that it was caused by a sudden shutdown, but I couldn't see anything different with boinc.exe or boincmgr.exe, not that I'm a software expert or anything. I was running boinc 5.10.30 under WinXP Pro SP3. I decided to install the latest version (6.10.18) in case something had gotten corrupted, but no change. The client is not running at all and does not run when double-clicked. I've tried the port openings, to no avail. Same with the select computer suggestion - both leaving it blank and selecting "localhost" (the p/w autofills). Also tried switching to "show active tasks" also to no avail.

Any help would be much appreciated. Thanks.

I've just started having the same problems (running windows vista). Windows Task Manager reports that the BOINC tasks are still running even though BOINC Manager has a blank screen (and "connecting to localhost" in lower right hand). Have tried re-installing BOINC, but, still no difference. Occasionally after hard restarts the details are displayed for a short period of time (haven't put a stopwatch to it yet...). All this started happening after loading pictures from a P&O Cruises USB stick (wife and daughter went on cruise and had photos taken and were given the photos on a USB stick). Anyone else have this issue ??

Cheers,
dk

I'm having the same issue. Boinc Manager is not able to connect to Boinc client. Tried upgrading. Running Win7Pro. Boinc is at 6.10.58.
Before this last upgrade, sometimes it started working after a restart. Not anymore. Firewall is ok.

What can I do ?

Tks,

What can I do ?

Check that BOINC its parts are allowed through your Windows firewall (or other firewall, if you use another). For Windows 7 firewall, Start->Control Panel->System and Security->Windows Firewall->Allowed Programs. Any of the entries of BOINC Manager and BOINC client, or boinc.exe and boincmgr.exe that aren't checked at the Home/Work (Private) level? Try checking them all (Change settings->check unchecked entries->OK).

Another possibility is that you have too much work in cache for the manager to show within the small time frame it can do RPCs (1 second) to update information about all work, and you have set BOINC Manager to show all tasks. Default is to show only Active tasks, to prevent the manager losing focus.

You can check what the status is in the registry:
HKEY_CURRENT_USER\Software\Space Sciences Laboratory, U.C. Berkeley\BOINC Manager\Tasks\ActiveTasksOnly should show as 1 (one). And if it isn't, try changing it to 1 (one), then exit BOINC Manager & reopen it.

---

Hello Ageless, tks for your reply. I have checked the firewall issue previously, and it was fine. The problem is that every time I (re)install the client, it works for some time and then, the problem starts.

I had Show all Tasks selected, but I don't have much of a queue. . .

I upgraded to the latest UNSTABLE release and so far it is fine. No Issues.

Tks,

I'm having the same problem: boinc is unable to communicate with a project and needs an internet connection

A common response by people on this forum is repeatedly "boinc.exe needs to be allowed to connect to the internet as well on TCP ports 80 and 443"

OK.... but how do I do this? How would a normal human know? I have tried and tried, but it just won't work.

I have a Cisco Linksys E3000 router. In the applications window, I guessed at the following additions:
BOINCManager, External Port 80, Internal Port 80, Protocol TCP
BOINCManager, External Port 443, Internal Port 443, Protocol TCP

(Its on a Mac, so boinc.exe is BOINCManager, I assume)

This obviously isn't correct. Can somebody tell me what the router entries should be?

(Its on a Mac, so boinc.exe is BOINCManager, I assume)

Nope! I don't know the name on the Mac, but it's definitely not the manager.

Gruß,
Gundolf

(Its on a Mac, so boinc.exe is BOINCManager, I assume)

No, even on a Mac, you have two binaries. One for BOINC (the client) --probably just called BOINC-- and one for BOINC Manager (the GUI) --probably called BOINCMGR. You will need to allow the BOINC binary through the firewall.

With firewall, we usually mean a software firewall on the computer, not necessarily any hardware firewalls, as they usually allow ports 80 and 443 (in stealth, or through uPnP) anyway.

Now, contrary to what you say your problem is, it's not the same as the one most people in this thread have. They have the problem that the GUI cannot talk to the client. You have the problem that your client cannot talk to anything on the internet. Although both can be caused by strict firewall settings, they're not the same thing.

---

Thank you, Ageless for the explanation.

But now, how do I fix it? I do not have a Firewall set up on my computer (I just checked... its not on).

So I guess it must be a router thing, correct? If so, how do I correctly make these changes?

I have a Cisco Linksys E3000 router. In the applications window, I guessed at the following additions:
BOINC, External Port 80, Internal Port 80, Protocol TCP
BOINC, External Port 443, Internal Port 443, Protocol TCP

Is this how to do it? What changes if any, do I make here?

The maddening thing is that I've been running Setiathome/BOINC since 1999. And all of a sudden not only it doesn't work, but I now need a graduate degree in computer science to figure it out.

"BOINC can't access internet - check network connection or proxy configuration"

You're posting from that same computer? Then I doubt it is a setting in your router, as any browser will by default use TCP port 80; so since you can post here, it's open.

Now, I have no knowledge at all about how to do anything on a Mac, I'm sorry to say. I am a Windows + self-built PC person.

So all I can ask is which version of BOINC are you using? Was there a version of BOINC on this system before? What has changed on that system, other than the router?

---

And thanks again for your help, Ageless...

Yes, I'm using the same computer for all internet access and BOINC. I have version 6.10.58. I had an earlier version of BOINC running on this computer. The only thing changed was the new router.

Everything on the computer works perfectly, except for BOINC.

Yeah, then the only thing that it can be is that router. So the setting you want to put in there (for BOINC) should be what makes it work. And if that doesn't work, it's time to pick up the manual for that router (PDF file) and check how to do things then.

---

Adding another data point to the unresolved-problem posts here, I had the "cannot communicate with client" problem as well. I was running Boinc 6.10.60 64-bit on Win 7, and after any "spike" in computer activity, boincmgr would lose its connection to the boinc client. It would then basically refuse to do anything, as clicking on anything in the Boinc manager window would put up an alert telling me it was communication with the client. It appeared that the client was still running, as Windows Task Manager showed the applications still using CPU cycles. However, it was impossible to do anything at all with the manager.

I tried explicitly opening the TCP/IP ports mentioned above and allowing bonc.exe and boincmgr.exe unfettered access, but this had no effect (My firewall is one of those that asks if a program should be allowed to communicate; it does not block connections silently). This didn't fix the problem.

So then I reverted to a previous working version of Boinc, and the problem went away. Sorry, I don't remember exactly which one, but I strongly suspect that it was 6.10.58. However, this was a 32-bit version of Boinc, inherited from an older machine that I "migrated" to this machine from (using the Windows migration utility).

Getting brave, I decided to try the 32-bit version of 6.10.60, and that version runs without any problems as well.

So for me, it appears that any recent 32-bit version of Boinc works fine, but the 64-bit version of 6.10.60 (and possibly others, my test case cannot say) has an unrecoverable timeout in it somewhere that basically locks it up.

Oh, and as I'm tagged as a new user, I should probably state that I came to Boinc back when SETI migrated over to the Boinc platform, and that I've been a computer hardware and software designer for 36 years. So, this isn't necessarily a case of PEBKAC here. ;)