Another thought are the required ports open, 443 ssl, required to pass Host ID etc. I assume others like port 80, normal HTTP, 1043 and/or 31416, one of these at least must be open as Manager is talking to BOINC.exe.
Also there is a dev version 5.2.14 that has been tried at Seti, Rom wrote as possible patch for some comms problems.
Yes, I've seen a little bit of that on the Boinc boards, seems to be some help on the comm probs, though the devs found it had it's own shortcomings, thus didn't make "official". Might be worth a try here for the 106 and 500 codes. I'm almost sorry that I brought over the MTU fix suggestion last week, also from Boinc boards, idea being that a smaller packet size facilitated things. It hasn't seemed to help in a single case on Einstein, AFAIK.
Theory being bounced around now is that the 500 prob is related to passing through so many devices - hubs, switches, routers, servers, etc - on an intranet before being sent out on internet, but is just theory at this point, and no solution.
(edited for typos)
(edit) 5.2.14 probably worth a shot. next version may be available as early as today, might not ?/?
microcraft
"The arc of history is long, but it bends toward justice" - MLK
Another thought are the required ports open, 443 ssl, required to pass Host ID etc. I assume others like port 80, normal HTTP, 1043 and/or 31416, one of these at least must be open as Manager is talking to BOINC.exe.
Shot in the dark:
If her workplace has say Microsoft IIS running which gobbles 1043, but port 31416 was opened but then subsequently shut ( say by some security on her work net ) would that scenario not that give such errors. This would not be diagnosable by either the BOINC client or server.
(edit) ....would that scenario not then give such errors?
Bedtime...
I have made this letter longer than usual because I lack the time to make it shorter ...
... and my other CPU is a Ryzen 5950X :-) Blaise Pascal
I am very sorry to hear that, and I apologize for all the problems and for the fact that we have had you work so hard, trying so many things. If it appears that we are just guessing, that is very close to the truth, at several of the projects and at Boinc itself, that is pretty much what we have all been reduced to - with the very likely exception of Rom, who writes a good deal of the code for Boinc. I'm also guessing that he is close to releasing another version update. My own knowledge of networking is very small, and leagues behind the rest of the people trying to help you here.
microcraft
"The arc of history is long, but it bends toward justice" - MLK
RE: Another thought are the
)
Yes, I've seen a little bit of that on the Boinc boards, seems to be some help on the comm probs, though the devs found it had it's own shortcomings, thus didn't make "official". Might be worth a try here for the 106 and 500 codes. I'm almost sorry that I brought over the MTU fix suggestion last week, also from Boinc boards, idea being that a smaller packet size facilitated things. It hasn't seemed to help in a single case on Einstein, AFAIK.
Theory being bounced around now is that the 500 prob is related to passing through so many devices - hubs, switches, routers, servers, etc - on an intranet before being sent out on internet, but is just theory at this point, and no solution.
(edited for typos)
(edit) 5.2.14 probably worth a shot. next version may be available as early as today, might not ?/?
microcraft
"The arc of history is long, but it bends toward justice" - MLK
RE: Another thought are the
)
Shot in the dark:
If her workplace has say Microsoft IIS running which gobbles 1043, but port 31416 was opened but then subsequently shut ( say by some security on her work net ) would that scenario not that give such errors. This would not be diagnosable by either the BOINC client or server.
(edit) ....would that scenario not then give such errors?
Bedtime...
I have made this letter longer than usual because I lack the time to make it shorter ...
... and my other CPU is a Ryzen 5950X :-) Blaise Pascal
Just instaled version
)
Just instaled version 5.2.14;
Still get the same error 500.
RE: Just instaled version
)
Condez,
I am very sorry to hear that, and I apologize for all the problems and for the fact that we have had you work so hard, trying so many things. If it appears that we are just guessing, that is very close to the truth, at several of the projects and at Boinc itself, that is pretty much what we have all been reduced to - with the very likely exception of Rom, who writes a good deal of the code for Boinc. I'm also guessing that he is close to releasing another version update. My own knowledge of networking is very small, and leagues behind the rest of the people trying to help you here.
microcraft
"The arc of history is long, but it bends toward justice" - MLK
All the help is
)
All the help is appreciated.
Even if it doesn't solve the problem.
That's the porpuse of the foruns.
If anyone has any idea of how to solve the this, post it here.
Thank You all.