Anyone else with this problem?

I have two W7 systems (one 64-bit, one 32-bit) with Boinc 6.12.43. Both have a problem uploading files. 16k is transferred immediately at decent speed, and then the transfer freeze. The funny thing is that one of the systems typically succeed to upload the rest after 2 - 3 days. The other one has had the same tasks uploading for over two weeks, even if it is on daily. I have tried rebooting several times, resetting the Boinc-settings and setting the http-mode to 1.0. I have also upgraded from 6.12.34 to 6.12.43, which did not solve the problem.

I got a lot of this stuff in the log:
12/02/2012 18:15:26 | SETI@home | Temporarily failed upload of 02oc11ag.6471.27724.14.10.201_1_0: HTTP error
12/02/2012 18:15:26 | SETI@home | Backing off 11 hr 58 min 34 sec on upload of 02oc11ag.6471.27724.14.10.201_1_0
12/02/2012 18:15:29 | | Project communication failed: attempting access to reference site
12/02/2012 18:15:33 | | Internet access OK - project servers may be temporarily down.

Downloads work OK on both machines.

Any ideas what could be wrong here? Would normally suspect a server problem, but why are these two machines acting differently?

Anyone else with this problem?

I have two W7 systems (one 64-bit, one 32-bit) with Boinc 6.12.43. Both have a problem uploading files. 16k is transferred immediately at decent speed, and then the transfer freeze. The funny thing is that one of the systems typically succeed to upload the rest after 2 - 3 days. The other one has had the same tasks uploading for over two weeks, even if it is on daily. I have tried rebooting several times, resetting the Boinc-settings and setting the http-mode to 1.0. I have also upgraded from 6.12.34 to 6.12.43, which did not solve the problem.

I got a lot of this stuff in the log:
12/02/2012 18:15:26 | SETI@home | Temporarily failed upload of 02oc11ag.6471.27724.14.10.201_1_0: HTTP error
12/02/2012 18:15:26 | SETI@home | Backing off 11 hr 58 min 34 sec on upload of 02oc11ag.6471.27724.14.10.201_1_0
12/02/2012 18:15:29 | | Project communication failed: attempting access to reference site
12/02/2012 18:15:33 | | Internet access OK - project servers may be temporarily down.

Downloads work OK on both machines.

Any ideas what could be wrong here? Would normally suspect a server problem, but why are these two machines acting differently?

Not certain, but could you try an experiment? Please report the results.

Follow the directions here and set up the following flags:

<http_transfer_timeout>seconds</http_transfer_timeout>3000</http_transfer_timeout>seconds</http_transfer_timeout>
<max_file_xfers>N</max_file_xfers>4</max_file_xfers>N</max_file_xfers>
<max_file_xfers_per_project>1</max_file_xfers_per_project>

I had a very similar problem with CPDN that was timing out arter 10 minutes. The setting is **supposed** to be since last activity, but at least in my case, it was for the entire file transfer. The machine that I was having problems with was win7 - 64 bit.

---

BOINC WIKI

Shouldn't that read

<http_transfer_timeout>3000</http_transfer_timeout>
<max_file_xfers>4</max_file_xfers>
<max_file_xfers_per_project>1</max_file_xfers_per_project>

? ;-)

Gruß,
Gundolf

Shouldn't that read

<http_transfer_timeout>3000</http_transfer_timeout>
<max_file_xfers>4</max_file_xfers>
<max_file_xfers_per_project>1</max_file_xfers_per_project>

? ;-)

Gruß,
Gundolf

Yes. Umm, I was in a hurry. Sorry about that.

---

BOINC WIKI

Thanks, but that did not help.

But I think I have a clue. I tried disabling my firewall before posting, and that had no effect. Now I tried uninstalling the FW and the tasks started to upload! The FW configuration was correct. Will investigate some more ...

Thanks, but that did not help.

But I think I have a clue. I tried disabling my firewall before posting, and that had no effect. Now I tried uninstalling the FW and the tasks started to upload! The FW configuration was correct. Will investigate some more ...

BOINC.exe needs outbound to the internet on ports 80 and 443 (http and https).

BOINC.exe needs inbound from the LAN or local host on port 31416.
BOINCmgr.exe and BOINCcmd.exe need outbound to the LAN or local host on port 31416. If you use a third party admin (BOINC Tasks or such) it will also need outbound access on port 31416 to the LAN or local host.

LAN access is needed if you want to control more than one computer on your LAN. local host access is needed to control the local host.

---

BOINC WIKI