If you are having download issues with Seti (as many of us have been), you can go to this link and follow the instructions from cdemers (at the top of the link). The issues appear to be related to TCP settings. I have implemented his suggestion across all my boxes and I am not having any download issues with Seti any more and I am no longer using a Proxy to get wus.
http://setiathome.berkeley.edu/forum_thread.php?id=71002 (http://setiathome.berkeley.edu/forum_thread.php?id=71002)
My observations following implementation are also included in the link and copied here below:
Download speeds appear to be similar to the proxy that I was generally using, around 5-10kB/s, so no apparent significant improvement there. What I have noticed is that the downloads start quicker, they sometimes have a tendency to burst in the first 5-15% of the download with speeds in the range 15-20kB/s, they don't seem to stall as often (in fact, hardly ever), and if downloads do hesitate, the hesitation is not for long. Overall, I think the outcome is positive and have modified all my machines accordingly.
BTW, in comparison to not using a proxy, hugely beneficial and well worth doing.
I have also increased the number of simultaneous downloads (for Seti) from 2 to 8. The download speed of any wu has not changed as a result of implementing the above. The outcome is that I can now pull down 8 wus inside 1m 20s on any machine. As I only crunch Seti, I have no conflicts with any other project in doing this.
In order to change N=2 to N=8 you will need to introduce/create a cc_config.xml file. If you are new to this, the following may be helpful.
http://boinc.berkeley.edu/wiki/Client_configuration (http://boinc.berkeley.edu/wiki/Client_configuration)
http://www.boinc-wiki.info/Cc_config.xml (http://www.boinc-wiki.info/Cc_config.xml)
rgds
Lionel