WCG tasks are reporting ok but I have 4 Seti tasks 100% which will not report, here is a typical message log:
02/02/2012 15:26:51 BOINC can't access Internet - check network connection or proxy configuration.
02/02/2012 15:27:19 SETI@home Fetching scheduler list
02/02/2012 15:27:50 World Community Grid update requested by user
02/02/2012 15:27:57 World Community Grid Sending scheduler request: Requested by user.
02/02/2012 15:27:57 World Community Grid Reporting 4 completed tasks, not requesting new tasks
02/02/2012 15:27:59 World Community Grid Scheduler request completed
02/02/2012 15:36:14 World Community Grid Sending scheduler request: To fetch work.
02/02/2012 15:36:14 World Community Grid Requesting new tasks
02/02/2012 15:36:17 World Community Grid Scheduler request completed: got 1 new tasks
02/02/2012 15:36:18 World Community Grid Started download of E205650_095_A.33.C26H13NO3S3.40.1.set1d06_A.33.C26H13NO3S3.40.1.zip
02/02/2012 15:36:23 World Community Grid Finished download of E205650_095_A.33.C26H13NO3S3.40.1.set1d06_A.33.C26H13NO3S3.40.1.zip
02/02/2012 15:38:50 SETI@home work fetch suspended by user
02/02/2012 15:38:53 SETI@home update requested by user
02/02/2012 15:38:57 SETI@home Fetching scheduler list
02/02/2012 15:38:59 Project communication failed: attempting access to reference site
02/02/2012 15:39:00 BOINC can't access Internet - check network connection or proxy configuration.
02/02/2012 15:39:14 SETI@home Fetching scheduler list

As you can see I suspended 'fetch work' on Seti to see if this would help but it still says it can't access the internet despite WCG working fine. Are there still issues with the servers being overloaded?

Your BOINC client seems to have problems with http connections, as it can't even reach google (the test site):

02/02/2012 15:39:00 BOINC can't access Internet - check network connection or proxy configuration.

AFAIK, WCG uses https connections.

Gruß,
Gundolf

---

Computer sind nicht alles im Leben. (Kleiner Scherz)

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

This is probably outbound firewall rules blocking BOINC.exe from reaching out to the internet on ports 80 and 443 or a proxy setting someplace.

---

BOINC WIKI