I've been getting these mesages since early AM here on the East coast.
11/4/2006 6:45:23 PM|SETI@home|Reason: Requested by user
11/4/2006 6:45:23 PM|SETI@home|Reporting 17 tasks
11/4/2006 6:50:29 PM||Project communication failed: attempting access to reference site
11/4/2006 6:50:29 PM|SETI@home|Scheduler request failed: a timeout was reached
11/4/2006 6:50:29 PM|SETI@home|Deferring scheduler requests for 1 minutes and 42 seconds
11/4/2006 6:50:30 PM||Access to reference site succeeded - project servers may be temporarily down.
11/4/2006 6:52:14 PM|SETI@home|Sending scheduler request to http://setiboinc.ssl.berkeley.edu/sah_cgi/cgi
11/4/2006 6:52:14 PM|SETI@home|Reason: Requested by user
11/4/2006 6:52:14 PM|SETI@home|Reporting 17 tasks
11/4/2006 6:55:24 PM||Project communication failed: attempting access to reference site
11/4/2006 6:55:25 PM|SETI@home|Scheduler request failed: failed sending data to the peer
11/4/2006 6:55:25 PM|SETI@home|Deferring scheduler requests for 4 minutes and 38 seconds
11/4/2006 6:55:26 PM||Access to reference site succeeded - project servers may be temporarily down.
11/4/2006 7:00:05 PM|SETI@home|Sending scheduler request to http://setiboinc.ssl.berkeley.edu/sah_cgi/cgi
11/4/2006 7:00:05 PM|SETI@home|Reason: Requested by user
11/4/2006 7:00:05 PM|SETI@home|Reporting 17 tasks
11/4/2006 7:00:27 PM||Project communication failed: attempting access to reference site
11/4/2006 7:00:28 PM||Access to reference site succeeded - project servers may be temporarily down.
11/4/2006 7:00:30 PM|SETI@home|Scheduler request failed: couldn't connect to server
11/4/2006 7:00:30 PM|SETI@home|Deferring scheduler requests for 8 minutes and 48 seconds

---

check firewall to ensure boinc.exe and boincmgr.exe have internet access. Being unable to reach the "reference" site, means it can't get to yahoo or google and most certainly they are working (atleast one was when your boinc.exe tried).

I've been getting these mesages since early AM here on the East coast.
11/4/2006 6:45:23 PM|SETI@home|Reason: Requested by user
11/4/2006 6:45:23 PM|SETI@home|Reporting 17 tasks
11/4/2006 6:50:29 PM||Project communication failed: attempting access to reference site
11/4/2006 6:50:29 PM|SETI@home|Scheduler request failed: a timeout was reached
11/4/2006 6:50:29 PM|SETI@home|Deferring scheduler requests for 1 minutes and 42 seconds
11/4/2006 6:50:30 PM||Access to reference site succeeded - project servers may be temporarily down.
11/4/2006 6:52:14 PM|SETI@home|Sending scheduler request to http://setiboinc.ssl.berkeley.edu/sah_cgi/cgi
11/4/2006 6:52:14 PM|SETI@home|Reason: Requested by user
11/4/2006 6:52:14 PM|SETI@home|Reporting 17 tasks
11/4/2006 6:55:24 PM||Project communication failed: attempting access to reference site
11/4/2006 6:55:25 PM|SETI@home|Scheduler request failed: failed sending data to the peer
11/4/2006 6:55:25 PM|SETI@home|Deferring scheduler requests for 4 minutes and 38 seconds
11/4/2006 6:55:26 PM||Access to reference site succeeded - project servers may be temporarily down.
11/4/2006 7:00:05 PM|SETI@home|Sending scheduler request to http://setiboinc.ssl.berkeley.edu/sah_cgi/cgi
11/4/2006 7:00:05 PM|SETI@home|Reason: Requested by user
11/4/2006 7:00:05 PM|SETI@home|Reporting 17 tasks
11/4/2006 7:00:27 PM||Project communication failed: attempting access to reference site
11/4/2006 7:00:28 PM||Access to reference site succeeded - project servers may be temporarily down.
11/4/2006 7:00:30 PM|SETI@home|Scheduler request failed: couldn't connect to server
11/4/2006 7:00:30 PM|SETI@home|Deferring scheduler requests for 8 minutes and 48 seconds

Mine are communicating fine.
-Michael

---

Well I checked my fire wall and all of boinc and seti are allowed and still get
11/4/2006 9:31:07 PM||Access to reference site succeeded - project servers may be temporarily down.
11/4/2006 9:31:10 PM|SETI@home|Scheduler request failed: a timeout was reached
11/4/2006 9:31:10 PM|SETI@home|Deferring scheduler requests for 1 minutes and 0 seconds
11/4/2006 9:32:10 PM|SETI@home|Sending scheduler request to http://setiboinc.ssl.berkeley.edu/sah_cgi/cgi
11/4/2006 9:32:10 PM|SETI@home|Reason: Requested by user
11/4/2006 9:32:10 PM|SETI@home|Requesting 1885041 seconds of new work, and reporting 19 completed tasks
11/4/2006 9:32:32 PM||Project communication failed: attempting access to reference site
11/4/2006 9:32:33 PM||Access to reference site succeeded - project servers may be temporarily down.
11/4/2006 9:32:35 PM|SETI@home|Scheduler request failed: couldn't connect to server

---

Thanks All for your help I made a call to my ISP and after that things seemed to work just fine. Again thank you.

---

Thanks All for your help I made a call to my ISP and after that things seemed to work just fine. Again thank you.

So what was going on with the ISP?

---

The T1 Trust, PRR T1 Class 4-4-4-4 #5550, 1 of America's First HST's