Hello, BOINC-community !

I updated my BOINC client from 4.45 to 5.2.13 yesterday and now connecting to any project scheduler doesn't work anymore.
I tried the new client on another machine in the same network (with no boinc formerly installed), same result: not able to connect to scheduler, BUT:
Attaching to a project is possible, master file was downloaded, the host was registered on the project.
Somtimes I've got an HTTP 500 - Error, sometimes only a simple HTTP-Error, both in BOINCManager Messages-Tab.

What to check next ?

Regards, Frank

---

Hello, BOINC-community !

I updated my BOINC client from 4.45 to 5.2.13 yesterday and now connecting to any project scheduler doesn't work anymore.
I tried the new client on another machine in the same network (with no boinc formerly installed), same result: not able to connect to scheduler, BUT:
Attaching to a project is possible, master file was downloaded, the host was registered on the project.
Somtimes I've got an HTTP 500 - Error, sometimes only a simple HTTP-Error, both in BOINCManager Messages-Tab.

What to check next ?

Regards, Frank

Hi. There is coverage of this on this BOINC Wiki page.
Click here .Its about 3/4 down the page..look for Error 500.

If you are Windows I have a patched client thathelp some but not all. Let me know if the page remedies work or not.

---

Hello, Tigher !

Thanx for your help. I used the automated test batch file and (after some modifications for german version of ms windows)it worked.
Almost all tests are fine, only the following failed:

ping setiboinc.ssl.berkeley.edu -l 2048 -n 4 > g.btf
ping setiboincdata.ssl.berkeley.edu -l 2048 -n 4 > i.btf

It seems, that 2048 bytes are too much. In fact, any value greater than 1472 did not work. So, there is a problem with packet fragmentation, I beliefe.
I can send you the complete logfile per email, if this helps.

Regards, Frank

---

Ok, it seems, there wasa a bug in boinc version 5.2.13. I just installed 5.3.24 and all works fine. Thanx.

---