Whoever did the programming on boinc certainly does not know what he or she is doing. I should not be getting these kind of error messages or having these kind of problems. I downloaded everything which needs downloaded. Everything required should be installed and running.

---

You use some special Firewall?
You want BOINC to somehow hack your Firewall settings?
(in fact there is no question in your post so probably you don't want any more info)

---

 


- ALF - "Find out what you don't do well ..... then don't do it!" :)
 

If the coders for BOINC do not know what they're doing, then why does the software work successfully for literally 150,000+ other users?

Rather than automatically place the blame at the programmers, why don't you describe the problem you're having so we can assist you in getting it working?

If your question is in the thread title, "not connected to a client", that would be caused by your firewall. The way BOINC works is that there's two main pieces: BOINC Manager (the graphical piece that most people interact with) and the BOINC Core Client (the actual program that runs everything). These two pieces communicate with each other locally over TCP port 31416. If your firewall blocks this communication, the BOINC Manager will not be able to connect to the Core Client, and it will give you the message "Cannot connect to client".

Try disabling your firewall or putting an exception in place for BOINCMGR.EXE and BOINC.EXE over TCP 31416.

Whoever did the programming on boinc certainly does not know what he or she is doing.

Ofcourse they do, for if they didn't know what they were doing, you wouldn't have a message that the BOINC Manager (the graphical user interface (GUI) used to control and command the BOINC client with) cannot make contact with the BOINC client. Then it would just not work, as the developer wouldn't have invested time and money into programming a sequence that checks whether or not the client and GUI are actually communicating with each other. And if they don't, to tell you about that, so you can go to forums and ask for help.

I should not be getting these kind of error messages or having these kind of problems. I downloaded everything which needs downloaded. Everything required should be installed and running.

Now, I also understand from this that you do not need any help. You're just here to rant. As when you would've wanted help, you would've told us at least what kind of system it was, with which Windows, or at least if it was a different system than your old one, and what you possibly already tried to do to fix things.

You've done nothing of the sort.
Now then, you probably know way better than the developers how these things should work, so off to the source code, download it, change it so it works as you see fit, compile it, and everything's hunky dory. No? :-)

---

I only seem to have this problem of not connecting to core client when I reboot.

---

Boinc was running Seti but when I rebooted Boinc now is saying Unable to connect to the core client. It has tried 3x would I like to restart.

That doesn't work.

It have boincmgr and boinc client added to my firewall to connect.

I am using Win 7 Pro SP1, Boinc 7.2.39 x86, and all ATI graphics drivers, etc are up to date.

---

Boinc was running Seti but when I rebooted Boinc now is saying Unable to connect to the core client. It has tried 3x would I like to restart.

That doesn't work.

It have boincmgr and boinc client added to my firewall to connect.

I am using Win 7 Pro SP1, Boinc 7.2.39 x86, and all ATI graphics drivers, etc are up to date.

BOINCMgr needs to get out to the local machine or the Local Area Network on port 31416. BOINC.exe needs to act as a server for same. There are two basic problems that may have to be found and fixed.
1) Firewall.
2) Some other program using port 31416. Some malware uses this port to phone home.

---

BOINC WIKI

I have all boinc exe's added to Firewall and virus etc programs.

I didn't see that 31416 was being used by any other program.

How do I add port 31416 for boinc?

---

I went back to 7.0.64 and it works fine.

Problem is the new version.

---