I have 'upgraded' my old SETI@HOME account to run on BOINC. I have received the new 'Project URL' and 'Account Key' etc.. but for the last 'month' I've been unable to get the first work unit for use with the BOINC software! All I get is 'Master File Fetch Failed' etc!!.

I know the program boinc.exe needs to have contact with IP address 66.28.250.125 port 80 which is setiboinc.ssl.berkeley.edu

My firewall says that boinc.exe has outbound traffic to 127.0.0.1 on port 1277. This is a loopback ip not the internet. How can boinc be setup to allow access as
I have a firewall on my pc which I can setup and then a NAT server for the internet.
I have tried to set the use http proxy but this does not work.

The IP address 127.0.0.1 is my local host. When using Boinc Manager, that program needs to have contact with my local host with IP address 127.0.0.1

The firewall is configured to allow BOINC access to the NAT router. but BOINC is not talking to the router (even if I specify the routers local network address with port 80).
How do I tell BOINC to communicate with 66.28.250.125 port 80 throught a NAPT or NAT router without opening port 80 to attack from outsiders?

I have tried to re-install without the firewall in place but it still gets 'Master File Fetch Failed'.
BOINC does not want to talk to the NAPT router at all. Considering that this is my only means of running Seti on my home machines, will anyone help with this problem?

---

tmd63... since SETI had a server outage yesterday, currently none of us are getting through with project requests. I realize this isn't your problem though, since you've been having issues for a month or so now. It just might not be easy to test your setup today.

As far as your firewall is concerned, Boinc.exe uses Port 1043 to communicate with the GUI. Then Port 80 outbound only to communicate with the project servers, but if you have internet access then that is already setup i imagine. These are the only exceptions you should have to allow. I have Boinc.exe setup to allow traffic on Port 1043 from the localhost only, to keep the riff-raff out.

This has worked great for me. Wish i could be of more help, but my knowledge of firewalls and such is quite limited. :)

Dig

---