Yesterday had to download a new browser for my broadband it includes everything, so I got a new firewall. Now climateprediction.net\\sulphur_um_4.19_windows_intelx86.exe is trying to get onto the web, why? If I have done right I have blocked it, yes.

---

Boinc uses port 80 to talk to the scheduler and ul/dl server(s). Port 80 is also the port used for web access. I guess as Boinc tries for port 80 your new firewall etc thinks its a web access. You will have to open it I think.

---

BOINC communicates amongst it\'s various parts with TCP messages. You will definately need to allow access to the ports listed for the following programs:
boinc.exe internet access ports 80 and 43, local access on ports 1043 and 31416
boincmgr.exe local access on ports 1043 and 31416
boinccmd.exe local access on ports 1043 and 31416

I have also seen reports that some firewalls will need holes opened for boinc.scr on ports 1043 and 31416. This is the first time I have seen a project executable need access (other than the F@H beta) I would try it with local access first and see if it will run properly.

---

BOINC WIKI

BOINCing since 2002/12/8

BOINC communicates amongst it\'s various parts with TCP messages. You will definately need to allow access to the ports listed for the following programs:
boinc.exe internet access ports 80 and 43, local access on ports 1043 and 31416
boincmgr.exe local access on ports 1043 and 31416
boinccmd.exe local access on ports 1043 and 31416

I have also seen reports that some firewalls will need holes opened for boinc.scr on ports 1043 and 31416. This is the first time I have seen a project executable need access (other than the F@H beta) I would try it with local access first and see if it will run properly.

@John K
What is on port 43? I thought 5.x.x brought 443 for ssl traffic?
Regards
Ian

---

BOINC communicates amongst it\'s various parts with TCP messages. You will definately need to allow access to the ports listed for the following programs:
boinc.exe internet access ports 80 and 43, local access on ports 1043 and 31416
boincmgr.exe local access on ports 1043 and 31416
boinccmd.exe local access on ports 1043 and 31416

I have also seen reports that some firewalls will need holes opened for boinc.scr on ports 1043 and 31416. This is the first time I have seen a project executable need access (other than the F@H beta) I would try it with local access first and see if it will run properly.

@John K
What is on port 43? I thought 5.x.x brought 443 for ssl traffic?
Regards
Ian

Your right, I\'ve been dropping that digit all day.

---

BOINC WIKI

BOINCing since 2002/12/8