Folding Forum

I have 5 Fermi GPU's waiting for work connected to 171.67.108.36
They all look like this:
15:58:23:WU01:FS00:0x15:Folding@home Core Shutdown: FINISHED_UNIT
15:58:23:WU01:FS00:FahCore returned: FINISHED_UNIT (100 = 0x64)
15:58:23:WU01:FS00:Sending unit results: id:01 state:SEND error:NO_ERROR project:8070 run:285 clone:2 gen:111 core:0x15 unit:0x0000007f6652edb45122e091f32b32ee
15:58:23:WU01:FS00:Uploading 341.17KiB to 171.67.108.36
15:58:23:WU01:FS00:Connecting to 171.67.108.36:8080
15:59:00:WU01:FS00:Upload complete
15:59:00:WU01:FS00:Server responded WORK_ACK (400)
15:59:00:WU01:FS00:Final credit estimate, 3874.00 points
15:59:00:WU01:FS00:Cleaning up

Windows XP and 7
Client V7.2.x and 7.3.x
GPU3

The troubleshooting steps all gave me OK, but I'm not getting work.

Can a problem with one computer cascade across a network? I had one client/slot/computer do what's listed above and then every other client/slot that finished after that did the same. The only fix has been to restart the systems involved.

Did you configure the next-unit-percentage value or not?

Can you find the following lines in your log:
12:32:05:WU01:FS00:Connecting to assign-GPU.stanford.edu:80
12:32:07:WU01:FS00:News: Welcome to Folding@Home
12:32:07:WU01:FS00:Assigned to work server 171.67.108.149
12:32:07:WU01:FS00:Requesting new work unit for slot 00: RUNNING gpu:0:"GF114 [GeForce GTX 675M]" from 171.67.108.149
12:32:07:WU01:FS00:Connecting to 171.67.108.149:8080

Sometimes, if there was a connectivity issue, the slot will be stuck, attempting to download a WU. Currently, that is fixed by restart the client or the system, depending on how it was installed.

Never touched the next-unit-percentage value. One of my systems has been running for a couple weeks and I had not touched it when this happened.

If that's the case, it should automatically attempt to get a new WU near 99% (if that's the default). This line indicates it and maybe you can try to find it in your log:
Connecting to assign-GPU.stanford.edu:80

Normally, if it happened once, it can be chalked up to a rare glitch somewhere. However, if it happens often, then troubleshooting would be required.