Why was Client assigned to Server with IP address 0.0.0.0?

From time to time, the project may not have work units that match the configuration of the platform running the fah client. When that is true, F@h will not supply duplicate "stay busy" work units. It is better to have some clients idle and repeatedly rechecking for new work than busy for long periods working on something that is of little benefit to the project. Even though a computer may see occasional idle periods, F@h still value all donations. The Assignment Server now goes through a logical set of conditions and if it can't find a match, it assigns to 0.0.0.0, which means the client will just try again later. If this continues for an extended period of time (more than 4 hours), be sure to ask for help in the Folding-Community support forum because this problem is normally corrected quickly. (Please be sure to check if someone has already posted about the problem, and add your comment there.)

NOTE: The SMP client requires the >5MB (Big WU) option set to Yes. A No setting will often result in being assigned to 0.0.0.0. Setting the SMP client (and possibly the GPU and CPU clients) to request deadlineless WUs may also cause the 0.0.0.0 work server assignment.

Related Links


 * Folding@home FAQ - Answer
 * Folding@home News - See Post on 12/15/2006
 * Folding@home SMP FAQ - mentions IP 0.0.0.0