Posts by dmbott

1) Questions and Answers : Windows : http://setiboinc.ssl.berkeley.edu/sah_cgi/cgi failed with a return value of 500 (Message 241592)
Posted 3 Feb 2006 by Profile dmbott
Post:
After reading several other threads addressing similar problems, I found an answer for me that worked like a charm for ALL my computers: Windows 2000 Professional and Windows XP Professional: MS Knowledgebase article See Solution 1

Essentially the problem seems to be with a "black hole router" somewhere between my computers and the setiathome server. The three solutions include 1) a simple registry edit, 2) asking the router to be changed, or 3) limiting all packet sizes with a universal MTU size that will pass through the black hole router. Of these, the first is simplest and best.

Solution 1:
1. Start Registry Editor (Regedit.exe).

2. Locate the following key in the registry:
HKEY_LOCAL_MACHINE\\SYSTEM\\CurrentControlSet\\Services\\tcpip\\parameters

3. On the Edit menu, click Add Value, and then add the following registry value:
Value Name: EnablePMTUBHDetect
Data Type: REG_DWORD
Value: 1

4. Quit Registry Editor, and then restart the computer.

Here's the description from the Microsoft Knowledgebase:

"On a TCP/IP-based wide area network (WAN), communication over some routes may fail if an intermediate network segment has a maximum packet size that is smaller than the maximum packet size of the communicating hosts--and if the router does not send an appropriate Internet Control Message Protocol (ICMP) response to this condition or if a firewall on the path drops such a response. Such a router is sometimes known as a "black hole" router.

You can locate a black hole router by using the Ping utility, which is a standard utility that is installed with the Microsoft Windows TCP/IP protocol. You can then use one of three methods of fixing or working around black hole routers.

When a network router receives a packet that is larger than the size of the Maximum Transmission Unit (MTU) of the next segment of a communications network, and that packet's IP layer "don't fragment" bit is flagged, the router is expected to send an ICMP "destination unreachable" message back to the sending host.

If the router does not send a message, the packet might be dropped, causing a variety of errors that vary with the program that is communicating over the unsuccessful link. (These errors do not occur if a program connects to a computer on a local subnet.) The behavior may seem intermittent, but closer examination shows that the behavior can be reproduced, for example, by having a client read a large file that is sent from a remote host. "

There were a few -106 errors when the SetiatHome servers were actually down, but then all clients were able to report finished workunits and download new ones!

Yippee!
2) Questions and Answers : Web site : It seems others ARE getting data. My report deadlines were 1/15 should I reset? (Message 240881)
Posted 2 Feb 2006 by Profile dmbott
Post:
After reading several other threads addressing similar problems, I found an answer that worked like a charm for ALL my computers: Windows 2000 Professional and Windows XP Professional: MS Knowledgebase article See Solution 1

Essentially the problem seems to be with a "black hole router" somewhere between mean and the setiathome server. The three solutions include 1) a simple registry edit, 2) asking the router to be changed, or 3) limiting all packet sizes with a universal MTU size that will pass through the black hole router. Of these, the first is simplest and best.

Solution 1:
1. Start Registry Editor (Regedit.exe).

2. Locate the following key in the registry:
HKEY_LOCAL_MACHINE\\SYSTEM\\CurrentControlSet\\Services\\tcpip\\parameters

3. On the Edit menu, click Add Value, and then add the following registry value:
Value Name: EnablePMTUBHDetect
Data Type: REG_DWORD
Value: 1

4. Quit Registry Editor, and then restart the computer.

Here's the description from the Microsoft Knowledgebase:

"On a TCP/IP-based wide area network (WAN), communication over some routes may fail if an intermediate network segment has a maximum packet size that is smaller than the maximum packet size of the communicating hosts--and if the router does not send an appropriate Internet Control Message Protocol (ICMP) response to this condition or if a firewall on the path drops such a response. Such a router is sometimes known as a "black hole" router.

You can locate a black hole router by using the Ping utility, which is a standard utility that is installed with the Microsoft Windows TCP/IP protocol. You can then use one of three methods of fixing or working around black hole routers.

When a network router receives a packet that is larger than the size of the Maximum Transmission Unit (MTU) of the next segment of a communications network, and that packet's IP layer "don't fragment" bit is flagged, the router is expected to send an ICMP "destination unreachable" message back to the sending host.

If the router does not send a message, the packet might be dropped, causing a variety of errors that vary with the program that is communicating over the unsuccessful link. (These errors do not occur if a program connects to a computer on a local subnet.) The behavior may seem intermittent, but closer examination shows that the behavior can be reproduced, for example, by having a client read a large file that is sent from a remote host. "

There were a few -106 errors when the SetiatHome servers were actually down, but then all clients were able to report finished workunits and download new ones!

Yippee!
3) Questions and Answers : Web site : It seems others ARE getting data. My report deadlines were 1/15 should I reset? (Message 240775)
Posted 1 Feb 2006 by Profile dmbott
Post:
The group you previously pasted shows what happens when you start up (looks normal to me), but not when you try to connect.

MJ


2/1/2006 1:08:21 PM|SETI@home|Sending scheduler request to http://setiboinc.ssl.berkeley.edu/sah_cgi/cgi
2/1/2006 1:08:21 PM|SETI@home|Reason: Requested by user
2/1/2006 1:08:21 PM|SETI@home|Requesting 604800 seconds of new work
2/1/2006 1:08:46 PM||Couldn't connect to hostname [setiboinc.ssl.berkeley.edu]
2/1/2006 1:08:46 PM|SETI@home|Scheduler request to http://setiboinc.ssl.berkeley.edu/sah_cgi/cgi failed with a return value of -106
2/1/2006 1:08:46 PM|SETI@home|No schedulers responded
2/1/2006 1:21:50 PM||request_reschedule_cpus: project op
2/1/2006 1:21:51 PM|SETI@home|Sending scheduler request to http://setiboinc.ssl.berkeley.edu/sah_cgi/cgi
2/1/2006 1:21:51 PM|SETI@home|Reason: Requested by user
2/1/2006 1:21:51 PM|SETI@home|Requesting 604800 seconds of new work
2/1/2006 1:22:13 PM||Couldn't connect to hostname [setiboinc.ssl.berkeley.edu]
2/1/2006 1:22:14 PM|SETI@home|Scheduler request to http://setiboinc.ssl.berkeley.edu/sah_cgi/cgi failed with a return value of -106
2/1/2006 1:22:14 PM|SETI@home|No schedulers responded
2/1/2006 1:27:56 PM||request_reschedule_cpus: project op
2/1/2006 1:27:58 PM|SETI@home|Sending scheduler request to http://setiboinc.ssl.berkeley.edu/sah_cgi/cgi
2/1/2006 1:27:58 PM|SETI@home|Reason: Requested by user
2/1/2006 1:27:58 PM|SETI@home|Requesting 604800 seconds of new work
2/1/2006 1:28:19 PM||Couldn't connect to hostname [setiboinc.ssl.berkeley.edu]
2/1/2006 1:28:23 PM|SETI@home|Scheduler request to http://setiboinc.ssl.berkeley.edu/sah_cgi/cgi failed with a return value of -106
2/1/2006 1:28:23 PM|SETI@home|No schedulers responded
2/1/2006 1:58:41 PM|SETI@home|Sending scheduler request to http://setiboinc.ssl.berkeley.edu/sah_cgi/cgi
2/1/2006 1:58:41 PM|SETI@home|Reason: Requested by user
2/1/2006 1:58:41 PM|SETI@home|Requesting 604800 seconds of new work
2/1/2006 1:59:04 PM||Couldn't connect to hostname [setiboinc.ssl.berkeley.edu]
2/1/2006 1:59:07 PM|SETI@home|Scheduler request to http://setiboinc.ssl.berkeley.edu/sah_cgi/cgi failed with a return value of -106
2/1/2006 1:59:07 PM|SETI@home|No schedulers responded
2/1/2006 2:00:07 PM|SETI@home|Fetching master file
4) Questions and Answers : Web site : It seems others ARE getting data. My report deadlines were 1/15 should I reset? (Message 239715)
Posted 30 Jan 2006 by Profile dmbott
Post:
Your suggestion did not work. Tried using a wide variety of proxies and no changes in error messages.

Dave


I've seen a suggestion elsewhere that using a public proxy to connect might help. You can find a list of them at this web site, you may have to experiment before you get one that would work for you.
The proxy settings in the BOINC manager are under Options in the menu bar, find the HTTP Proxy tab.

MJ

5) Questions and Answers : Web site : It seems others ARE getting data. My report deadlines were 1/15 should I reset? (Message 238668)
Posted 28 Jan 2006 by Profile dmbott
Post:
I turned on my computer descriptions. Note I have 4 computers: WinXP Pro on 3 and Win2K on other. All have Norton AV (but not Internet Security). All have latest version of Seti@home installed. I have hardware firewall, but it's set to allow any communication from computers with MAC addresses for my network adapters. The XP firewalls have all been modified to allow Boinc.exe to communicate.

They all use Dantz Retrospect for backup (which is server/client over personal network) and Norton's update also works over the network.

I can't imagine why only Boinc Seti@home is not working right.

Dave
6) Questions and Answers : Web site : It seems others ARE getting data. My report deadlines were 1/15 should I reset? (Message 238666)
Posted 28 Jan 2006 by Profile dmbott
Post:
Need to post a few lines of messages at a time or it fails. Here's start of messages for laptop (from same as error message post):

1/26/2006 10:49:13 PM||Starting BOINC client version 5.2.13 for windows_intelx86
1/26/2006 10:49:13 PM||libcurl/7.14.0 OpenSSL/0.9.8 zlib/1.2.3
1/26/2006 10:49:13 PM||Data directory: C:\\Program Files\\BOINC
1/26/2006 10:49:16 PM||Processor: 1 GenuineIntel Intel(R) Pentium(R) 4 Mobile CPU 1.60GHz
1/26/2006 10:49:16 PM||Memory: 254.92 MB physical, 626.17 MB virtual
1/26/2006 10:49:16 PM||Disk: 17.45 GB total, 8.96 GB free
1/26/2006 10:49:16 PM|SETI@home|Computer ID: 1418299; location: home; project prefs: default
1/26/2006 10:49:16 PM||General prefs: from SETI@home (last modified 2005-09-07 18:45:07)
1/26/2006 10:49:16 PM||General prefs: no separate prefs for home; using your defaults
1/26/2006 10:49:17 PM||Remote control not allowed; using loopback address
7) Questions and Answers : Web site : It seems others ARE getting data. My report deadlines were 1/15 should I reset? (Message 238665)
Posted 28 Jan 2006 by Profile dmbott
Post:
Having problems posting message contents. See if this works. Failure return values of 500, -103 and -106.

Dave

1/26/2006 10:49:22 PM|SETI@home|Sending scheduler
request to http://setiboinc.ssl.berkeley.edu/sah_cgi/cgi
1/26/2006 10:49:22 PM|SETI@home|Reason: Requested by user
1/26/2006 10:49:22 PM|SETI@home|Requesting 604800 seconds
of new work, and reporting 17 results
1/26/2006 10:52:10 PM|SETI@home|Scheduler request to
http://setiboinc.ssl.berkeley.edu/sah_cgi/cgi failed with a return value of 500
8) Questions and Answers : Windows : No data since the beginin of january (Message 238662)
Posted 28 Jan 2006 by Profile dmbott
Post:
I try to post but it continually fails with messages in it. Let's see if I can post withOUT messages.
9) Questions and Answers : Web site : It seems others ARE getting data. My report deadlines were 1/15 should I reset? (Message 238075)
Posted 27 Jan 2006 by Profile dmbott
Post:
I read about all the problems and backlogs. What I want to know is whether I should reset and just lose all the work units that have been trying to report since 1/5/2006. I've been patient, but I have nothing but failures to upload and get new work. I have 4 separate computers and they all have failed to load. 3 of them have been upgraded to the latest version of SETI@home and one was kept in the old version 3.x I was running before all the problems began.

I've succeeded in downloading the master file when hitting update, but not in getting any new units or reporting completed units.

My ISP had some short outages, but all has been reset/rebooted and nothing else is having problems. Should I be patient or should I lose the processed units, reset and at least get analyzing again?





 
©2025 University of California
 
SETI@home and Astropulse are funded by grants from the National Science Foundation, NASA, and donations from SETI@home volunteers. AstroPulse is funded in part by the NSF through grant AST-0307956.