171.67.108.21 is Reject;

[tobor]

[noorman]

This not just a few ,it's pretty wide spresd...

http://www.google.com/search?q=171.64.6 ... ox&ie=&oe=
http://www.google.com/search?q=171.67.1 ... ox&ie=&oe=
http://www.google.com/search?hl=en&rls= ... f&aqi=&oq=

.


The ONLY recent one in there is http://foldingforum.org/viewtopic.php?f=50&t=13514 which is about someone's machine that CAN connect but gets an error reply '503', meaning server is too busy to 'respond in time' ...


.

[noorman]

...

.

I tested CS6 a minute ago and I got an OK twice (on port 8080)

the trace-route would only fail if the server was down or the connection to it was disabled or disconnected ...
You seem to be unable to make a HTTP connection to those servers, which is a higher layer problem (which could be coming from a Firewall blocking such traffic)


.

[tobor]

I have no firewalls.
If it was a firewall issue on my end nothing would get through I would think.

[noorman]

I have no firewalls.
If it was a firewall issue on my end nothing would get through I would think.

.

The firewall I use is two-way and program specific. A firewall is also protocol and port number specific.
So, it 's completely possible that one (kind of)connection works and another doesn't (because it 's blocked) ...

Doesn't your O.S. have a firewall ?
Windows XP, Vista and 7 have ...
I 've just tested 108.26 also, it responds with an OK for me too ...
So, it is definitely working and the load is fluctuating (to be expected in this current situation)

.

[noorman]

.

MORE Official news here: http://foldingforum.org/viewtopic.php?f=24&t=13474

and here: http://folding.typepad.com/news/2010/02 ... rvers.html.


.

[Ragnar Dan]

I was getting failures on this server again. One of my GPU's switched to .11 and was fed a WU, but another had 7 failures and wouldn't stop pounding the same one until I restarted it, for whatever reason.

[Ragnar Dan]

Now all 3 of my GPU's have been trying to upload WU's to this server, with no success. Normally this will eventually be solved, but it should not be that this kind of thing happens so often.

[Marine Iguana]

Same here both GPU's unable to send.

[noorman]

.

Have they still not been uploaded ?

EDIT: I guess something has been wrong with it; my GPU production also crashed during the night

.

[toTOW]

my GPU production also crashed during the night

It's probably related to this issue : viewtopic.php?f=18&t=13753 ...

[vsekh]

I have the same problem with several GPU clients. I had to restart them to get new work units.

[noorman]

.

171.67.108.21 was in REJECT again / passed it on to V.P. a while ago

seems to be solved now ...

EDIT: Received confirmation of server fix from V.P.

.

[anko1]

Still in a hotel. My GPU client has been trying to p/u a unit since [March 23 20:29:17 UTC], about 45 tries now. The error message I've been getting is "Initial: 48FA; - Error: Bad packet type from server, expected work assignment" I get an OK when I put it in my browser window. Here's part of the latest log [attempt number doesn't match b/c I restarted the client a couple of times]:

Code: Select all

[07:42:34] + News From Folding@Home: Welcome to Folding@Home
[07:42:34] Loaded queue successfully.
[07:42:34] Connecting to http://171.67.108.21:8080/
[07:44:34] Posted data.
[07:45:34] Initial: 48FA; - Error: Bad packet type from server, expected work assignment
[07:45:34] - Attempt #8  to get work failed, and no other work to do.
Waiting before retry.
[07:56:25] + Attempting to get work packet
[07:56:25] - Will indicate memory of 2553 MB
[07:56:25] - Connecting to assignment server
[07:56:25] Connecting to http://assign-GPU.stanford.edu:8080/
[07:56:25] Posted data.
[07:56:25] Initial: 43AB; - Successful: assigned to (171.67.108.21).
[07:56:25] + News From Folding@Home: Welcome to Folding@Home
[07:56:25] Loaded queue successfully.
[07:56:25] Connecting to http://171.67.108.21:8080/
[07:58:25] Posted data.
[07:59:25] Initial: 48FA; - Error: Bad packet type from server, expected work assignment
[07:59:25] - Attempt #9  to get work failed, and no other work to do.
Waiting before retry.

[noorman]

.

The server seems to be OK according to the server stats page.
I don't think this is a server problem.

Since your Client can't get work, I 'd suggest stopping it, deleting the Work folder and queue.dat file and restarting it.
There might be file corruption in play (queue) here ...

Do you have the switch -verbosity 9 in your start command (or Client config) ? (for maximum data on Client processes for problem solving in cases like this).

Can you work remotely on that computer ?
Otherwise you are stuck

.