Questions and Answers :
Windows :
Master File Fetch Failed
Message board moderation
Author | Message |
---|---|
tmd_63 Send message Joined: 28 Mar 04 Posts: 29 Credit: 179,843 RAC: 0 |
I am unable to connect BOINC in my home PC to setiathome.berkeley.edu. All I get is: Using your default projecy prefs Insufficient work; requesting more Master file fetch failed Resetting Project Detaching from project I have set BOINC manager and BOINC Core Client CLI to have full access through my McAfee Firewall and I am routing through a NAPT router. But neither BOINC app is communicating on port 80. BOINC Manager has one outbound hook to 127.0.0.1 on port 1043. BOINC CLI has two hooks; 127.0.0.1 port 1768 and Listening port 1043 I have tried to disable the firewall briefly and attempted a connect without it and it still failed. Has anyone had experience of this problem with BOINC, McAfee firewalls and NAPT ADSL routers? If so. HELP!!!!!! |
mikey Send message Joined: 17 Dec 99 Posts: 4215 Credit: 3,474,603 RAC: 0 |
TheIP address 127.0.0.1 is an inidcation that your machine is not connected to the net. The file fetch issue means that you and Berkeley are not connected long enough for the file to be transferred. |
tmd_63 Send message Joined: 28 Mar 04 Posts: 29 Credit: 179,843 RAC: 0 |
The IP address 127.0.0.1 is an indication that your machine is not connected to the net. The file fetch issue means that you and Berkeley are not connected long enough for the file to be transferred. So what do I need to set up in BOINC to get it to talk through the NAPT router? If I look at my machine with ipconfig, it shows the default gateway as XXX.X.X.X (actual number withheld for security). Do I need to set the proxy in BOINC to point to the same gateway? What port number should be used? |
Jord Send message Joined: 9 Jun 99 Posts: 15184 Credit: 4,362,181 RAC: 3 |
At this moment it doesn't matter, since the Seti scheduler is down. Without it you won't be able to attach to the Seti project. So to keep up with the latest information, read the front page news, the server status and the technical news for all that has happened in the past couple of weeks. It'll also explain why the schedulers are down. If you don't mind doing some other work at this moment, there's a whole host of other projects out there that you can attach to. Use Boincstats as a guideline. It links to those projects that are Up & Running. Although only Einstein, SZTAKI, CPDN and Predictor have work at this moment. boinc.exe uses port TCP 80 for the internet, while boincmgr.exe uses TCP ports 1043 and 31416 for the network connections. |
Darrell Wilcox Send message Joined: 11 Nov 99 Posts: 303 Credit: 180,954,940 RAC: 118 |
The IP address 127.0.0.1 is an indication that your machine is not connected to the net. The IP address of 127.0.0.1 is the "loopback address", the address of itself. The BOINC Manager has the capability to "talk" to remote computers, and the implementation is such that the same technique is used to "talk" to the local machine on which the Manager is running. EVERY machine has as its own address the 127.0.0.1 |
©2024 University of California
SETI@home and Astropulse are funded by grants from the National Science Foundation, NASA, and donations from SETI@home volunteers. AstroPulse is funded in part by the NSF through grant AST-0307956.