Does S@H still work?

[Cristatus]

When the screensaver is running, I get a message saying:

BOINC is currently idle.

I also get the following messagesin the messages tab:

29/06/2005 11:12:10||Starting BOINC client version 4.45 for windows_intelx86
29/06/2005 11:12:10||Data directory: C:\Program Files\BOINC
29/06/2005 11:12:10|SETI@home|Computer ID: 1122189; location: home; project prefs: default
29/06/2005 11:12:10||General prefs: from unknown project http://setiathome.berkeley.edu/ (last modified 2004-10-22 04:19:48)
29/06/2005 11:12:10||General prefs: using your defaults
29/06/2005 11:12:10||Remote control not allowed; using loopback address
29/06/2005 11:12:10||Insufficient work; requesting more
29/06/2005 11:12:10|SETI@home|Deferring communication with project for 8 hours, 26 minutes, and 1 seconds


I tried running one of my other computers all night in the hopes that this problem would solve itself after the given hours, and I got the same message over and over again, but with decreasing number of hours.

I have the following set up here

Thanks in advance.

 

[Rattledagger]

Except for some announced outages, don't know of any outages the last couple weeks, and atleast from here there's currently no problems to connecting to SETI@Home getting work.

Exponential backoff will count down for each hour, but to cut this shourt you can select the project under Project-tab and click "update". Note, if you gets a "RPC too resent", you must let it wait 10 minutes before it automatically tries to connect.

But, exponential backoff should be between 1 minute and 4 hours, you getting longer backoff than 4 hours indicates you get an error-message. This can example be too little disk-space, or not enough memory. For disk-space, look on your preferences, and if needed change them. After downloading the new preferences if still doesn't work, exit BOINC client and re-start it. For memory, you must have more than 64 MB memory to get any work, so this shouldn't be a problem for you.
To edit preferences, goto http://setiathome.ssl.berkeley.edu/prefs.php?subset=global

Other possibilities is you're having problems connecting, if you example uses the XP-firewall you must give boinc.exe access to internet.

If this doesn't work, post the log of a failing request...