Part 3

If you still have BOINC 5.2.x still running on a Windows system, can you try an experiment and post back with the result to see if it makes any difference? Use the program DrTCP to set the "Path MTU Discovery" and "Black Hole Detection" to NO and then reboot the system and test if it can get through. Then change those setting back to their original values Yes/No and reboot again. This at least might give us one small clue or rule out one of the minor theories as to what might be going wrong.

BOINC 5.2.13 (recommended client)

***************
DrTCP - before any changes

2.2.2006 7:55:52|SETI@home|Sending scheduler request to http://setiboinc.ssl.berkeley.edu/sah_cgi/cgi
2.2.2006 7:55:52|SETI@home|Reason: To fetch work
2.2.2006 7:55:52|SETI@home|Requesting 6556 seconds of new work, and reporting 3 results
2.2.2006 7:56:02|SETI@home|Scheduler request to http://setiboinc.ssl.berkeley.edu/sah_cgi/cgi failed with a return value of 500
2.2.2006 7:56:02|SETI@home|No schedulers responded

***************
DrTCP - "Path MTU Discovery" and "Black Hole Detection" set to NO - reboot


2.2.2006 8:16:16|SETI@home|Sending scheduler request to http://setiboinc.ssl.berkeley.edu/sah_cgi/cgi
2.2.2006 8:16:16|SETI@home|Reason: Requested by user
2.2.2006 8:16:16|SETI@home|Requesting 7665 seconds of new work, and reporting 3 results
2.2.2006 8:16:26|SETI@home|Scheduler request to http://setiboinc.ssl.berkeley.edu/sah_cgi/cgi failed with a return value of 500
2.2.2006 8:16:26|SETI@home|No schedulers responded

***************
DrTCP - "Path MTU Discovery" and "Black Hole Detection" set back to Default - reboot

2.2.2006 9:23:29|SETI@home|Sending scheduler request to http://setiboinc.ssl.berkeley.edu/sah_cgi/cgi
2.2.2006 9:23:29|SETI@home|Reason: Requested by user
2.2.2006 9:23:29|SETI@home|Requesting 11241 seconds of new work, and reporting 3 results
2.2.2006 9:23:34|SETI@home|Scheduler request to http://setiboinc.ssl.berkeley.edu/sah_cgi/cgi failed with a return value of 500
2.2.2006 9:23:34|SETI@home|No schedulers responded

---

Summary

Although I can access setiathome.ssl.berkeley.edu using interner browser,
I cannot ping it. Cannot also trace it.

Btw, ping of www.google.com also fails.

Regarding BOINC 5.2.13, DrTCP don't help.

That's all.

---

@Spok

Is 192.168.74.253 your router? Does it block pings or ICMP traffic? Does your ISP block pings or ICMP?

If you type http://128.32.18.173/ into your browser what does it reply to you? Is it this?

Forbidden
You don't have permission to access / on this server.
--------------------------------------------------------------
Apache/1.3.33 Server at setiboinc.ssl.berkeley.edu Port 80

If it is then you are getting to the scheduler even if your pings don't make it.

Also what does it say for this

http://66.28.250.125/

Does that say forbidden too? If it does this means you can talk to the ul/dl server also. Which is good news...although not an end to your problems.

Let me know

If you want to mail me your IP address I will try and ping you to see if there are blocks en-route. Send it to john_brown_gordon at ntlworld.com

Cheers
Ian

---

I can access these servers. At least to get message about permission, like you described. But this is not surprise for me. As I reported few posts ago, I can connect to projects, ul/dl, report results, etc. using BOINC 4.71.

What I cannot is to ping these servers. So if BOINC 5.2.x use ping to confirm availability of servers then I'm loosing.

Anyway - I will send you an email with some IP's.

---

Hi there
I had error 500 problems as well and after mailing some of the devs on the problem, they released a fix for version 5.3.13
Everything worked after that and I am on version 5.3.16 and it STILL WORKS.
So download 5.3.16 (5.3.17 is out but will only test it later) and install.
HAVE FUN
CHEERS

---

Tried 5.3.20. Still no progress for me.
If there is an algorithm which first try to ping seti, google, yahoo or whatever, and if it succeed then try to contact scheduler, maybe could be changed. First try to talk with scheduler and if it fails then try to ping
anything.

Since I cannot ping anything through my firewall (but can access google, seti, etc.), this can help me and others with the same problem.

Spok

**************************************
24.2.2006 6:29:01|SETI@home|Sending scheduler request to http://setiboinc.ssl.berkeley.edu/sah_cgi/cgi
24.2.2006 6:29:01|SETI@home|Reason: Requested by user
24.2.2006 6:29:01|SETI@home|Reporting 1 tasks
24.2.2006 6:29:02||web site RPC to http://www.google.com
24.2.2006 6:29:02||HTTP error: Send failed since rewinding of the data stream failed
24.2.2006 6:29:04||Network check: success
24.2.2006 6:29:06|SETI@home|Scheduler request to http://setiboinc.ssl.berkeley.edu/sah_cgi/cgi failed: http error
24.2.2006 6:29:06|SETI@home|No schedulers responded
24.2.2006 6:29:06|SETI@home|Deferring scheduler requests for 1 minutes and 0 seconds
**************************************

---

The same for 5.3.22

---

The same for 5.3.22

Hi
You say you cannot ping through your firewall? Then let pings through and see if it helps

---

The same for 5.3.22

Hi
You say you cannot ping through your firewall? Then let pings through and see if it helps

Sorry, I don't understand you. I'm connected through big company proxy and firewall, and I suppose they will not change configuration for me.
So how can I "let pings through" ?
(I'm not networking expert, so if you can, tell me how-to do.)

In versions until 4.7x there probably was no checking using ping, so these versions works here (and I'm still using version 4.71). Versions 5.x.x
are not usable for me. Just because of this "ping" test. If I understand well, BOINC gives up communication before it tries.

---

Just reporting - 5.3.26 no progress.

15.3.2006 6:56:43|SETI@home|Sending scheduler request to http://setiboinc.ssl.berkeley.edu/sah_cgi/cgi
15.3.2006 6:56:43|SETI@home|Reason: Requested by user
15.3.2006 6:56:43|SETI@home|Requesting 3031 seconds of new work
15.3.2006 6:56:45||web site RPC to http://www.google.com
15.3.2006 6:56:45||HTTP error: Send failed since rewinding of the data stream failed
15.3.2006 6:56:47||Network check: success
15.3.2006 6:56:48|SETI@home|Scheduler request to http://setiboinc.ssl.berkeley.edu/sah_cgi/cgi failed: http error
15.3.2006 6:56:48|SETI@home|No schedulers responded
15.3.2006 6:56:48|SETI@home|Deferring scheduler requests for 1 minutes and 0 seconds

---

5.3.27 - no progress

5.3.28 - different message (error 400), but the same result - cannot connect, UL or DL

*******************
23.3.2006 7:10:31|SETI@home|Sending scheduler request to http://setiboinc.ssl.berkeley.edu/sah_cgi/cgi
23.3.2006 7:10:31|SETI@home|Reason: Requested by user
23.3.2006 7:10:31|SETI@home|Requesting 25429 seconds of new work
23.3.2006 7:10:36|SETI@home|Scheduler request to http://setiboinc.ssl.berkeley.edu/sah_cgi/cgi failed: Error 400
23.3.2006 7:10:36|SETI@home|No schedulers responded
23.3.2006 7:10:36|SETI@home|Deferring scheduler requests for 14 minutes and 37 seconds
*******************

---

You might try one of the sugestions in this post http://support.microsoft.com/kb/314825/en-ur

---

You might try one of the sugestions in this post http://support.microsoft.com/kb/314825/en-ur

First thank you for suggestion.

Anyway, while I have some small experience with network hardware, I'm not networking specialist. So this article didn' help me. I don't know what the "Black Hole Router" is.

When I try to ping for example "boinc.berkeley.edu", I get a message
"Answer from 192.168.74.235: Target network not available."

In both cases - "ping 128.32.18.189" and "ping 128.32.18.189 -f -l 548"

In the article (paragraph MORE INFORMATION) is mentioned 'the router is expected to send an ICMP "destination unreachable" message...' and also ' If the router does not send a message, the packet might be dropped...'

I everytime get the message. (I have localised version of Windows,
so let's say my back-translation "Target network not available" means "destination unreachable".)

Then it seems for me, this article is not about my case.

Did I made something wrong? Please correct me.

Thank you
Spok

---

...and more funny is, that until now I can at least use version 4.71, which was able to communicate with Berkeley, but from saturday I get messages

***UNHANDLED EXCEPTION****
Reason: Access Violation (0xc0000005) at address 0x00425BBC read attempt to address 0x00000158

1: 03/27/06 06:57:38
1: SymGetLineFromAddr(): GetLastError = 126

when trying to start boinc.exe. Doesn't matter if directly or using Boincmgr.exe

It makes crunching on company computer nearly impossible.

"Nearly" means I have some possibilities, but not very comfortable.
Versions 5.x cannot communicate with servers but can crunch. Version 4.71 before few days can crunch and communicate, but now cannot even start. I have to now take the computer home to do all ul/dl outside of company firewall.
Why?
Because of some "ping" test, which was added to Boinc 5.x and which I cannot disable. Don't like it :-\\

---

Boinc 5.4.0 - no progress

*********************************************************************
11.4.2006 6:34:47|SETI@home|Sending scheduler request to http://setiboinc.ssl.berkeley.edu/sah_cgi/cgi
11.4.2006 6:34:47|SETI@home|Reason: Requested by user
11.4.2006 6:34:47|SETI@home|Requesting 522964 seconds of new work
11.4.2006 6:34:52|SETI@home|Scheduler request to http://setiboinc.ssl.berkeley.edu/sah_cgi/cgi failed: Error 400
11.4.2006 6:34:52|SETI@home|No schedulers responded
11.4.2006 6:34:52|SETI@home|Deferring scheduler requests for 1 minutes and 0 seconds
*********************************************************************

---

Boinc 5.4.0 - no progress

*********************************************************************
11.4.2006 6:34:47|SETI@home|Sending scheduler request to http://setiboinc.ssl.berkeley.edu/sah_cgi/cgi
11.4.2006 6:34:47|SETI@home|Reason: Requested by user
11.4.2006 6:34:47|SETI@home|Requesting 522964 seconds of new work
11.4.2006 6:34:52|SETI@home|Scheduler request to http://setiboinc.ssl.berkeley.edu/sah_cgi/cgi failed: Error 400
11.4.2006 6:34:52|SETI@home|No schedulers responded
11.4.2006 6:34:52|SETI@home|Deferring scheduler requests for 1 minutes and 0 seconds
*********************************************************************

We are in the same boat, I can fetch the master file but as far as work goes I cannot retrieve any. I get the error 500 here too, very frustrating. BTW where did you download 4.71 at?

---

Just wondering...Did they change the connection port after between 4.x and 5.x?

---

We are in the same boat, I can fetch the master file but as far as work goes I cannot retrieve any. I get the error 500 here too, very frustrating. BTW where did you download 4.71 at?

You can download all versions here:

http://boinc.berkeley.edu/dl/

---

Just wondering...Did they change the connection port after between 4.x and 5.x?

Short answer is yes, detailed answer is port was really changed between 5.2.15 and 5.3.something. What did change between 4 and 5 was the use of libcurl proxy authentification.

---

Boinc Wiki

Sometimes I hate my Bob Newhart style of humor.

We are in the same boat, I can fetch the master file but as far as work goes I cannot retrieve any. I get the error 500 here too, very frustrating. BTW where did you download 4.71 at?

You can download all versions here:

http://boinc.berkeley.edu/dl/

Thanks :) I downloaded that version and I have no problems now. It is able to communicate with seti servers.

---