Boinc.exe and Boincmgr.exe only need to "talk" to eachother on the local network on either port 1043 or 31416. Else Boinc.exe will need an open port on port 80.

If you are able to post here from work, then port 80 is open.
If you aren't, then it isn't. ;) (it might be behind a proxy)

It just depends on if your own computer at work has its own firewall, yes or no, before being allowed to open ports 1043/31416 for Boinc.exe and Boincmgr.exe to talk to eachother. Really, this "chatter" will only happen on the local computer or local network if you have more than one computer running BOINC to reach from yours.

As for the old client, yes, 4,19 up to 4.45 still work.
Although maybe not for long as soon as the new Seti client comes along.

But in the mean time, you can still download 4.45 from here. Prior to installing that one, uninstall the 5.2.x client you have and go into the BOINC folder to delete a file called gui_rpc_auth.cfg. Then you can install 4.45 in the same directory and start up.

You do need your 32 character authenticator key though. 4.45 doesn't work with passwords. So if you don't know it, you can get it from here. Fill in the email address you used to register your account with and the key will be emailed to you.

---

Hence why I run this checklist these days:

Checklist:
1. You made sure Boinc.exe and Boincmgr.exe are allowed to talk to eachother on ports 1043 or 31416 if needed?
2. You made sure Boinc.exe is allowed to talk to the internet on port 80 and 1043 or 31416 if needed?
3. You went to Change your password twice, and used the Change password button there to save it? (You did not use Enter?)
4. You start up Boinc Manager, then go to Projects, Attach to project?
5. In the window that comes up, you fill in http://setiathome.berkeley.edu in the URL link and hit Next?
6. You then choose the (round) radio button in front of Existing Account?
7. You fill in the email address you used to register your account here at Seti?
8. You fill in the password that you just set and hit Next?

I think #2 answers why I can't use it at work. I'm sure those ports are blocked. And there is nothing that I can do about that.

Will the old client work? I think I still have it at home.

---

Hence why I run this checklist these days:

Checklist:
1. You made sure Boinc.exe and Boincmgr.exe are allowed to talk to eachother on ports 1043 or 31416 if needed?
2. You made sure Boinc.exe is allowed to talk to the internet on port 80 and 1043 or 31416 if needed?
3. You went to Change your password twice, and used the Change password button there to save it? (You did not use Enter?)
4. You start up Boinc Manager, then go to Projects, Attach to project?
5. In the window that comes up, you fill in http://setiathome.berkeley.edu in the URL link and hit Next?
6. You then choose the (round) radio button in front of Existing Account?
7. You fill in the email address you used to register your account here at Seti?
8. You fill in the password that you just set and hit Next?

---

Does your firewall allow both boinc.exe and boincmgr.exe to access the net?

MJ, the boincmgr.exe does NOT access the net. Everything is done by boinc.exe only, even the www.google.com test accesses.

True, but some firewalls (including my ZoneAlarm), interpret boincmgr's use of the TCP/IP protocol to talk to boinc.exe as internet access. So leaving it blocked from the net effectively blocks it from communicating across localhost to boincmgr.

MJ

---

Does your firewall allow both boinc.exe and boincmgr.exe to access the net?

MJ, the boincmgr.exe does NOT access the net. Everything is done by boinc.exe only, even the www.google.com test accesses.

1/18/2006 10:44:52 PM||Fetching config info from http://setiathome.berkeley.edu/get_project_config.php

Are there any entries after this line?

Does your firewall allow both boinc.exe and boincmgr.exe to access the net?

MJ

---

The Account Manager is a work in progress, and not available yet. Instead of that, use Attach to project from the same menu. Before you do that, make sure you've gone into Your Account and set up your own password for your account, then attach using an existing account.

The proxy dialog comes up if there is too long a delay in connecting to the project servers. This isn't unusual on a Wednesday, after the weekly maintenance outage when there's a backlog of people trying to connect causing a traffic jam. Two easy things I've seen recommended are to reboot after installing but before connecting, and have patience.

Also, one user reports the following:
Log onto your SETI account on the internet. After and only after you have logged in open Boinc. Now you can connect to the project and the proxy and socs prompt will not show up.

MJ

Thanks for the quick response! However, I still cannot connect. Get: Failed to attach to project.

1/18/2006 10:44:45 PM||Starting BOINC client version 5.2.13 for windows_intelx86
1/18/2006 10:44:45 PM||libcurl/7.14.0 OpenSSL/0.9.8 zlib/1.2.3
1/18/2006 10:44:45 PM||Data directory: C:\\Program Files\\BOINC
1/18/2006 10:44:45 PM||Processor: 1 GenuineIntel Intel(R) Pentium(R) M processor 1400MHz
1/18/2006 10:44:45 PM||Memory: 511.23 MB physical, 1.22 GB virtual
1/18/2006 10:44:45 PM||Disk: 27.94 GB total, 8.27 GB free
1/18/2006 10:44:45 PM||No general preferences found - using BOINC defaults
1/18/2006 10:44:46 PM||Remote control not allowed; using loopback address
1/18/2006 10:44:46 PM||This computer is not attached to any projects.
1/18/2006 10:44:46 PM||There are several ways to attach to a project:
1/18/2006 10:44:46 PM||1) Run the BOINC Manager and click Projects.
1/18/2006 10:44:46 PM||2) (Unix/Mac) Use boinc_cmd --project_attach
1/18/2006 10:44:46 PM||3) (Unix/Mac) Run this program with the -attach_project command-line option.
1/18/2006 10:44:46 PM||Visit http://boinc.berkeley.edu for more information
1/18/2006 10:44:52 PM||Fetching config info from http://setiathome.berkeley.edu/get_project_config.php

---

The Account Manager is a work in progress, and not available yet. Instead of that, use Attach to project from the same menu. Before you do that, make sure you've gone into Your Account and set up your own password for your account, then attach using an existing account.

The proxy dialog comes up if there is too long a delay in connecting to the project servers. This isn't unusual on a Wednesday, after the weekly maintenance outage when there's a backlog of people trying to connect causing a traffic jam. Two easy things I've seen recommended are to reboot after installing but before connecting, and have patience.

Also, one user reports the following:
Log onto your SETI account on the internet. After and only after you have logged in open Boinc. Now you can connect to the project and the proxy and socs prompt will not show up.

MJ

---

No matter what I try, I keep getting the above error. Failed to attach to account manager. I am at work trying to get this workign and we do have a proxy server. But even with that information in the program, it still will not work. If I take out the proxy information, I don't even get prompted for my username and password. Which tells me that it's at least talking to the server when I put that information in.

Any ideas out there? I tried looking in these forums, but have had no luck.

---