Update: it is believed that the problems described below were fixed in the SETI Windows client version 3.07 and later, and that it should no longer be necessary to set explicit proxies in the SETI client, even if your ISP uses transparent proxies. If you have an earlier version, download the latest version from http://setiathome.ssl.berkeley.edu/. [Thanks to Paul].
Old info: Failure of your SETI@home client (Windows version 3.06 and earlier) to talk to the SETI server can be caused by the transparent web proxy caches run by your ISP. To work around this:
Return to Index.