I have been running seti@home for ten years and recently upgraded my equipment. Now I continue to have config. and pref. problems. Example:

9/30/2011 9:03:52 AM | | Fetching configuration file from http://setiathome.berkeley.edu/get_project_config.php
9/30/2011 9:04:17 AM | SETI@home | Master file download succeeded
9/30/2011 9:04:22 AM | SETI@home | Sending scheduler request: Project initialization.
9/30/2011 9:04:22 AM | SETI@home | Requesting new tasks for CPU
9/30/2011 9:04:40 AM | SETI@home | Scheduler request failed: Couldn't connect to server
9/30/2011 9:05:00 AM | | Project communication failed: attempting access to reference site
9/30/2011 9:05:03 AM | | Internet access OK - project servers may be temporarily down.
9/30/2011 9:06:00 AM | SETI@home | Sending scheduler request: Project initialization.
9/30/2011 9:06:00 AM | SETI@home | Requesting new tasks for CPU
9/30/2011 9:06:17 AM | SETI@home | Scheduler request failed: Couldn't connect to server
9/30/2011 9:06:39 AM | | Project communication failed: attempting access to reference site
9/30/2011 9:06:41 AM | | Internet access OK - project servers may be temporarily down.
9/30/2011 9:09:08 AM | SETI@home | Sending scheduler request: Project initialization.
9/30/2011 9:09:08 AM | SETI@home | Requesting new tasks for CPU
9/30/2011 9:09:26 AM | SETI@home | Scheduler request failed: Couldn't connect to server
9/30/2011 9:09:47 AM | | Project communication failed: attempting access to reference site
9/30/2011 9:09:48 AM | | Internet access OK - project servers may be temporarily down.
9/30/2011 9:13:41 AM | SETI@home | Sending scheduler request: Project initialization.
9/30/2011 9:13:41 AM | SETI@home | Requesting new tasks for CPU
9/30/2011 9:13:59 AM | SETI@home | Scheduler request failed: Couldn't connect to server
9/30/2011 9:14:20 AM | | Project communication failed: attempting access to reference site
9/30/2011 9:14:23 AM | | Internet access OK - project servers may be temporarily down.
9/30/2011 9:24:00 AM | SETI@home | Sending scheduler request: Project initialization.
9/30/2011 9:24:00 AM | SETI@home | Requesting new tasks for CPU
9/30/2011 9:24:16 AM | SETI@home | Scheduler request failed: Couldn't connect to server
9/30/2011 9:24:37 AM | | Project communication failed: attempting access to reference site
9/30/2011 9:24:39 AM | | Internet access OK - project servers may be temporarily down.


Anyone, please help!

---

And why would that show config. and/or pref. problems? ;-)

That's just the SETI@home servers having problems.

Gruß,
Gundolf

---

Computer sind nicht alles im Leben. (Kleiner Scherz)

SETI@home classic workunits 3,758
SETI@home classic CPU time 66,520 hours

A quick test of your config would be to join another project or two and see if they download work...

---

BOINC WIKI

Thanx. 8-))

---