WU2610 not submitting on Windows SMP client

D

deansfurniture5

Weaksauce
Joined
Sep 7, 2004
Messages
65
Hi All,

I've been running the SMP client for about a month, and I've been getting the 2610 work unit a lot, but it never is able to connect to the collection server to submit. However, I got a different WU the other day and it submitted no problem.

Anyone else having this problem?

Thanks,
Kyle
 
deansfurniture5 said:
Hi All,

I've been running the SMP client for about a month, and I've been getting the 2610 work unit a lot, but it never is able to connect to the collection server to submit. However, I got a different WU the other day and it submitted no problem.

Anyone else having this problem?

Thanks,
Kyle
Click to expand...

I don't have a problem with submitting the 2610s. However, I believe those WU are pretty big and something in your Internet connection is timing out when trying to send this. Are you behind a router ?

 
Xilikon said:
I don't have a problem with submitting the 2610s. However, I believe those WU are pretty big and something in your Internet connection is timing out when trying to send this. Are you behind a router ?
Click to expand...

Yes, I am behind a router, although this has happened in two locations: at school and at home (where I am now), so I'm suspecting it might be something else.
 
deansfurniture5 said:
Yes, I am behind a router, although this has happened in two locations: at school and at home (where I am now), so I'm suspecting it might be something else.
Click to expand...

You can try to force sending those WU by stopping fah.exe then run fah -queueinfo to find if there are unsent WU (lines with DONE as status). After this, do fah -send # with the line number to force sending this WU.

Do this within the command line.
 
Xilikon said:
You can try to force sending those WU by stopping fah.exe then run fah -queueinfo to find if there are unsent WU (lines with DONE as status). After this, do fah -send # with the line number to force sending this WU.

Do this within the command line.
Click to expand...

Just tried that--I'm still getting the same "Couldn't send HTTP request to server" error.
 
[22:37:05] Couldn't send HTTP request to server (wininet)
[22:37:05] + Could not connect to Work Server (results)
[22:37:05] (171.65.103.100:8080)
[22:37:05] Could not transmit unit 00 to Collection server; keeping in queue.


[22:37:05] + Attempting to send results
[22:37:40] Couldn't send HTTP request to server (wininet)
[22:37:40] + Could not connect to Work Server (results)
[22:37:40] (171.64.65.64:8080)
[22:37:40] - Error: Could not transmit unit 00 (completed May 13) to work server.


[22:37:40] + Attempting to send results
[22:38:17] Couldn't send HTTP request to server (wininet)
[22:38:17] + Could not connect to Work Server (results)
[22:38:17] (171.65.103.100:8080)
[22:38:17] Could not transmit unit 00 to Collection server; keeping in queue.
 
Is the client set for big packets.
You dont need it set to yes to download work but you do need it set to upload.

Luck ....... :D
 
I do have "bigpackets" set to yes, but I don't remember what I said for using IE settings--which is that in client.cfg?
 
Not sure, just stop the service and then run it with a -config switch, make sure it's set to no, then restart the service.
 
ND40oz said:
Not sure, just stop the service and then run it with a -config switch, make sure it's set to no, then restart the service.
Click to expand...

Just tried that, now when I try to send (using -send XX from the command line) it's hanging at "Attempting to send results"
 
You must log in or register to reply here.
Back
Top