I've enjoyed helping to crunch data for the seti@home project and have enjoyed being able to contribute in the exploration of other intelligent life. However, I have decided to update from seti@home classic to BOINC. I started out with version 4.45 which worked ok and a little intermittant and now has taken a nose dive around July 23. It now cannot connect to the local host, have tried installing and uninstalling, checked my firewall and still refuses to connect to host. This happened a day or two after the newer buttons were introduced. I am convinced there are still some bugs with this version and hope our friends at Berkeley can figure out what's going on with this version without blaming it on user "firewall" error. I liked the features that it has but it seemed that it had some upload and download file transfer -106 error problems as well.

Anyway, I finally gave up on trying to get this to work and for it to connect to the localhost which was a losing battle. I uninstalled 4.45 and went to an earlier version 4.19 which started working just fine but doesn't have all the neat new features but at least doesn't have any connection problems thus far.

---

I had all these problems, and spent a lot of time waiting (and cursing) before someone suggested I click 'reset project'.
All was well after that.

---

Note that the 'local host' is not a server at Berkeley, it is your own computer. The 127.0.0.1 ip address is the local system loopback address. You very well could be having firewall issues. When you change the versions of a program it will appear to a firewall as a different program - you need to allow access to and from the Internet for the new program version to work.

Please cut the people running this project some slack. This isn't any highly funded, we'll make gobs of money from it project. We are all working as 'beta testers' for this and it is voluntary. And yes I do get frustrated when it doesn't work as smooth as I think it should, but so what.

Note that the 'local host' is not a server at Berkeley, it is your own computer. The 127.0.0.1 ip address is the local system loopback address. You very well could be having firewall issues. When you change the versions of a program it will appear to a firewall as a different program - you need to allow access to and from the Internet for the new program version to work.

Please cut the people running this project some slack. This isn't any highly funded, we'll make gobs of money from it project. We are all working as 'beta testers' for this and it is voluntary. And yes I do get frustrated when it doesn't work as smooth as I think it should, but so what.

When I first started running 4.45 I did get a Windows Firewall message whether or not to allow the connection. I said yes, and all was working fine until July 23. I see by this Q&A a lot of people are starting to experience the same problem. If someone has a step by step how to fix the windows XP SP2 firewall (assuming it is the firewall) that would be extremely helpful.

---

My rules
READ WIKI
1.Shut down Boinc and restart, not fixed
READ WIKI
2.Update Boinc, not fixed
READ WIKI
3.Reboot computer, not fixed
READ WIKI
4.As a last resort, reset and/or detach, with these you lose all WUs.
READ WIKI

"I am convinced there are still some bugs with this version and hope our friends at Berkeley can figure out what's going on with this version without blaming it on user "firewall" error."



I take exception with this comment, because there are a few that have problems but the majority do not so it leads one to believe that something other than BOINC is at fault.. I know BOINC is not perfect

Winblows FireWall and ZoneAlarm, you must give exception to BOINC core client command line interface and BOINC GUI

---

Semper Eadem
So long Paul, it has been a hell of a ride.

Park your ego's, fire up the computers, Science YES, Credits No.

The problem connecting to the local host is usually because the manager tries to contact the deamon before the daemon is ready. The simple work around is to try File - Select Computer - (leave the entries blank). If that doesn't work, try File - Select Computer - localhost.

Another likely problem is other programs that steal ports 1043 and 31416. There are two possible work arounds for this. Either make certain that BOINC loads before these programs do, or in some cases, much later than these programs do as they may release the port again.

The last likely problem is the personal firewall. Double check the settings just to be certain.

---

BOINC WIKI

My rules
READ WIKI
1.Shut down Boinc and restart, not fixed
READ WIKI
2.Update Boinc, not fixed
READ WIKI
3.Reboot computer, not fixed
READ WIKI
4.As a last resort, reset and/or detach, with these you lose all WUs.
READ WIKI

"I am convinced there are still some bugs with this version and hope our friends at Berkeley can figure out what's going on with this version without blaming it on user "firewall" error."



I take exception with this comment, because there are a few that have problems but the majority do not so it leads one to believe that something other than BOINC is at fault.. I know BOINC is not perfect

Winblows FireWall and ZoneAlarm, you must give exception to BOINC core client command line interface and BOINC GUI

By looking at the posts, it appears to be more than a "few" that are starting to experience this problem. Why would 4.19 work just fine and 4.45 not work or be able to connect to localhost? especially when 4.45 was working? what is the difference other than more buttons and more graphics? I cannot reset the project in 4.45 because it is not greyed out and there is nothing on the project line anymore (yes, I have tried to reattach the project). Have modified the firewall and have also allowed the zone alarms and yes I have WIKI WIKI WIKI and it has been of no help. Also have done the select computer blank, localhost, reboot and have installed single user or multi-user. If I am experiencing this problem and others have been by the looks of the Q&A posts, and the standard responses of "firewall" "select localhost" "reset project (which cannot be done if greyed out)" "WIKI" are not correcting the problem, what is my next course of action? It may work fine for you and numerous others, but doesn't for me and numerous others. Yes, I may be frustrated, but am being civil and trying to get to the bottom of this problem. All I ask is for people to not to come off like a know-it-all and not to reply back with the standard responses as I stated earlier. What else can I do or is there something indeed wrong with this program version? I take it since this is not a funded project, that there is no tech support line or IM capability (which would be very helpful right now).

---