I have tried the Boinc related forums, with my problem, and it seems that it comes down to a DNS problem. I am running Boinc 5.2.13 on a Linux Libranet 2.8.1 box, and same on a windows box. The windows box has no problem updating, and getting new wu's. The linux does, I haven't been able to update or get new wu's for several days now. I have done a ping on all the projects that I am connected with and they all work.
Here is one ping.
peterhin@GNULinux01:~$ ping -c10 setiboincdata.ssl.berkeley.edu
PING setiboincdata.ssl.berkeley.edu (66.28.250.125): 56 data bytes
64 bytes from 66.28.250.125: icmp_seq=0 ttl=246 time=179.7 ms
64 bytes from 66.28.250.125: icmp_seq=1 ttl=246 time=178.4 ms
64 bytes from 66.28.250.125: icmp_seq=2 ttl=246 time=190.0 ms
64 bytes from 66.28.250.125: icmp_seq=3 ttl=246 time=239.5 ms
64 bytes from 66.28.250.125: icmp_seq=4 ttl=246 time=178.2 ms
64 bytes from 66.28.250.125: icmp_seq=5 ttl=246 time=179.7 ms
64 bytes from 66.28.250.125: icmp_seq=6 ttl=246 time=171.2 ms
64 bytes from 66.28.250.125: icmp_seq=7 ttl=246 time=179.0 ms
64 bytes from 66.28.250.125: icmp_seq=8 ttl=246 time=160.0 ms
64 bytes from 66.28.250.125: icmp_seq=9 ttl=246 time=180.0 ms

--- setiboincdata.ssl.berkeley.edu ping statistics ---
10 packets transmitted, 10 packets received, 0% packet loss
round-trip min/avg/max = 160.0/183.5/239.5 ms

This is what I get when I try to update.

peterhin@GNULinux01:~$
Mon Dec 12 21:43:13 2005|Einstein@Home|Fetching master file
Mon Dec 12 21:43:14 2005||Couldn't resolve hostname [einstein.phys.uwm.edu]
Mon Dec 12 21:43:18 2005|Einstein@Home|Master file fetch failed
Mon Dec 12 21:43:18 2005|Einstein@Home|Too many backoffs - fetching master file
Mon Dec 12 21:43:24 2005|World Community Grid|Fetching master file
Mon Dec 12 21:43:25 2005||Couldn't resolve hostname [www.worldcommunitygrid.org]
Mon Dec 12 21:43:29 2005|World Community Grid|Master file fetch failed
Mon Dec 12 21:43:29 2005|World Community Grid|Too many backoffs - fetching master file

If there is anyone with some ideas, I would appreciate the input.
I am a newbie to linux (computers for that matter, in general, trying hard to learn) So please don't expect a lot of fundamental knowledge.
Thanks.

My problem appears to be fixed. It appears that it was not a DNS issue. Once I was able to upload my Seti wu's I could then get WCG, sofar to download.
Can someone please explain to me what was happening here. It seems that it was being held up by Seti, as I haven't done anything to BOINC in the mean time.

http://setiathome.berkeley.edu/index.php

It was a seti problem. Next time you have an issue, check the news on the main seti site, you can look at the Latest news post if you have any other questions.

I did that, I make a point of checking the status whenever there is an issue. It still does not explain why or how it effects the other Projects.
Is it that Seti takes over BOINC to try and get its wu's out or what that is my question. Nothing that I have read over the last week (Seti Tech. news, etc.) indicates that Seti's problem would affect the other projects upload and download.

Sorry, Missed the part about other projects. I associate Boinc = seti. I don't use it for anything else.

It's possible that all boinc projects were affected by it, as boinc and seti are a part of the berkeley network.

I also observed the same problem. My windows machines recovered from whatever was wrong at SETI faster than my linux machines. 9 times out of 10 it's a SETI problem.

Yea I never thought of it that way, but it does make sense. Yes my windows box was up much quicker than my linux box also.
Thanks for your time. Forever learning.