Quote:
Originally Posted by SnM77  Hmm - I have a completed work unit waiting to send, and it's assigned to 171.64.65.64, but it's telling me that it is trying to use port 8080, despite the fact that I have my client configured to use a proxy server on another port. Has anyone seen this before? |
BAH. I found a thread on the folding site - getting an IP of 0.0.0.0 is their system's way of telling the client that the server is not accepting connections and to try again later. It looks like 172.64.65.64 has been dead for most of the day. the same thread stated that there is nothing to do for this but to wait for Stanford to fix it. I have a feeling I'm going to lose a bunchof points to this. . .