I JUST got the rest of my work uploaded through a very slow PROXY. I hope they find an answer this problem Soon.

I just called my ISP and they are not blocking anything also they have no plans to go with IPv6 in the near future.
They also tried tracing and pinging all of the URL#s and got the same thing that I did and said the problem seems to be with the Hurricane routing.

Jim

Jim...
Hang in there a bit.
I have contacted Eric and asked if somebody had time to check into it from their end with Hurricane. No promises, but I made the inquiry.

Maybe the internet connection/hardware/ISP of S@h don't support IPv6?


- Best regards! - Sutaru Tsureku, team seti.international founder. - Optimize your PC for higher RAC. - SETI@home needs your help. -

Only since 15 June?

You both don't have IPv6 enabled in the OS, or? ;-)

---------------------------------------

What is if you test all the URLs from here in 'message 1120872', in your browser?



- Best regards! - Sutaru Tsureku, team seti.international founder. - Optimize your PC for higher RAC. - SETI@home needs your help. -

Can u please also test it with:
ping -l 1500 setiboinc.ssl.berkeley.edu
(after the dash, this is a small L :-) )

At least the German ping version needs the -f flag in conjunction with the -l flag:

ping -a -l 1448 -f 208.68.240.20
Ping setiboinc.ssl.berkeley.edu [208.68.240.20] mit 1448 Bytes Daten:
Antwort von 208.68.240.20: Bytes=1448 Zeit=245ms TTL=53

With -l 1449, I get

Paket müsste fragmentiert werden, DF-Flag ist jedoch gesetzt.

Gruß,
Gundolf

Can u please also test it with:
ping -l 1500 setiboinc.ssl.berkeley.edu
(after the dash, this is a small L :-) )

Can u please also test it with:
ping -l 1500 setiboinc.ssl.berkeley.edu
(after the dash, this is a small L :-) )

Command prompt commands,
ipconfig/flushdns did nothing.
tracert to berkeley stopped about 3 hops short. (208.68.240.20)
Ping timed out 5 times in a row. (208.68.240.20)
I would hate to detach/Reattach and lose all of the work on my boxes.
I don't want to reset S@H.
All of my equiptment checked out.
My ISP and or firewalls aren't the problem.(Called my ISP)
And ALL of my other projects are having a Blast.
I don't know what to do...I'm Stumped. :((

Only a guess, but could it be the old problem with DNS not resolving properly?

Try entering these lines in the HOSTS file:

208.68.240.16 setiboincdata.ssl.berkeley.edu
208.68.240.20 setiboinc.ssl.berkeley.edu
208.68.240.13 boinc2.ssl.berkeley.edu

And restart Boinc.

I think the point being made is that if some users can connect, then the problem cannot be SETI's as your first post requests them to fix the issue.

If some users can connect and others cannot, then the problem must exist somewhere in between those who cannot connect and Berkeley.

funny...I realize that it's not working for everyone, I have two win7 boxes
that aren't working myself.

here's info from this linux box...


laptop@laptop-laptop:~$ traceroute 208.68.240.20
traceroute to 208.68.240.20 (208.68.240.20), 30 hops max, 60 byte packets
1 10.141.70.1 (10.141.70.1) 1.459 ms 2.449 ms 3.200 ms
2 134.163.4.193 (134.163.4.193) 14.921 ms 15.155 ms 15.363 ms
3 134.163.136.10 (134.163.136.10) 15.644 ms 15.787 ms 15.948 ms
4 icapl250.shellus.com (134.163.253.250) 16.209 ms 16.427 ms 16.580 ms
5 12.119.213.117 (12.119.213.117) 16.905 ms 17.121 ms 17.548 ms
6 cr2.hs1tx.ip.att.net (12.123.212.198) 25.399 ms 21.568 ms 26.122 ms
7 cr1.dlstx.ip.att.net (12.122.28.157) 22.785 ms 24.318 ms 22.947 ms
8 dlstx01jt.ip.att.net (12.122.80.41) 29.475 ms 31.002 ms 31.223 ms
9 192.205.32.190 (192.205.32.190) 26.120 ms 27.988 ms 192.205.34.82 (192.205.34.82) 28.243 ms
10 Hurrican-Electric-LLC.Port-channel100.ar3.SJC2.gblx.net (64.214.174.246) 76.400 ms 76.206 ms 76.527 ms
11 10gigabitethernet3-2.core1.pao1.he.net (72.52.92.69) 79.053 ms 73.272 ms 79.158 ms
12 64.71.140.42 (64.71.140.42) 65.281 ms 64.939 ms 64.903 ms
13 208.68.243.254 (208.68.243.254) 93.221 ms 93.790 ms 93.927 ms
14 * * *
15 * * *
16 * * *
17 * * *
18 * * *


followed by:


Thu 23 Jun 2011 09:39:30 AM CDT Running CPU benchmarks
Thu 23 Jun 2011 09:39:30 AM CDT Suspending computation - running CPU benchmarks
Thu 23 Jun 2011 09:40:01 AM CDT Benchmark results:
Thu 23 Jun 2011 09:40:01 AM CDT Number of CPUs: 2
Thu 23 Jun 2011 09:40:01 AM CDT 1550 floating point MIPS (Whetstone) per CPU
Thu 23 Jun 2011 09:40:01 AM CDT 3819 integer MIPS (Dhrystone) per CPU
Thu 23 Jun 2011 09:40:03 AM CDT Resuming computation
Thu 23 Jun 2011 10:34:47 AM CDT SETI@home Computation for task 12ap11ab.12159.8403.12.10.207_0 finished
Thu 23 Jun 2011 10:34:47 AM CDT SETI@home Starting 13dc10ab.10471.4727.11.10.182_1
Thu 23 Jun 2011 10:34:47 AM CDT SETI@home Starting task 13dc10ab.10471.4727.11.10.182_1 using setiathome_enhanced version 603
Thu 23 Jun 2011 10:34:49 AM CDT SETI@home Started upload of 12ap11ab.12159.8403.12.10.207_0_0
Thu 23 Jun 2011 10:34:52 AM CDT SETI@home Finished upload of 12ap11ab.12159.8403.12.10.207_0_0
Thu 23 Jun 2011 10:51:34 AM CDT SETI@home update requested by user
Thu 23 Jun 2011 10:51:38 AM CDT SETI@home Sending scheduler request: Requested by user.
Thu 23 Jun 2011 10:51:38 AM CDT SETI@home Reporting 2 completed tasks, not requesting new tasks
Thu 23 Jun 2011 10:51:41 AM CDT SETI@home Scheduler request completed

and the 2 tasks were uploaded.

the *** is not an error. The routers are simply programmed to not respond
to ping requests....ie no DOS ability

Kevin

I know this machine runs Linux, have you tried a reboot? Works many times for Windows machines.

A project reset is also an option but you would lose the work already on board and completed. Berkeley should resend the work after the reset but you would have to crunch it again. Last but best option in my view. After 6 days of non communication you have to do something!

I have considered it. But since this is a database server, I have to find time to do so.

About the other last replies:

The problem machine, and all the other machines are located on different internal LANs connected to a firewall which again is connected to Internet through a ADSL router. Rebooting the router will not help, since all other traffic seem to work quite well (both BOINC and non-BOINC communication).

If there has been anyhting wrong with the machines network connection, the database traffic would also suffer from this error. Downloading new WUs did not seem to be any problem a few days ago. Uploading them seem to work from time to time, but reporting them is not possible.

Also, BOINC on this machine is currently reporting "Retrieved header from server: 500 Internal server error". This tell me (based on several years experience with web-design and -programming using PHP, MySQL and Apache web server) that the server (in this case NOT my machine, but the server in the other end) has a problem.

But since no other seem to report this error, it can be caused by invalid data sent from my machine.

And again... thanks for all replies :)

Have you tried flushing the DNS cache on the machine in question?

Edit: you may have corrupt, or outdated DNS entries for the project.

Still the same problem - the computer (id 5256434) will not report any tasks. According to http://setiathome.berkeley.edu/hosts_user.php?userid=7992989 this machine last reported June 14th while the other machines have reported completed works since then.

The other machine (id 5306094) is very similar and seem to work OK. Since I'm not able to find any solution to this, I'm about to give up this machine.... :(

Somebody in another thread found that using a proxy was a workaround for a similar situation. You might try something like Privoxy (with the filtering disabled).

                                                                 Joe