Please Post For Data Collection!
#1-Since June 15/16...And Still having trouble.

---

I Desire Peace and Justice, Jim Scott (Mod-Ret.)

Since middle June.

I have many wu's waiting to download, or the famous "Retry in ........

---

SETI@home classic workunits 4,019
SETI@home classic CPU time 34,348 hours

#3-Since June ...And Still having trouble, connection only by Proxy...

---

http://www.boincstats.com/signature/user_2436064.gif

Since June 15.

This HE internal routing issue is impacting the whole project as not everyone can report data. I have two links and one times out, the other doesn't. I have slowed my uptake of SETI work units because I am getting little completed confirmed results back.

---

since july 19th, cannot connect to servers project may be down or so it says. i can upload finished results fine. but i cannot update requested by user, or download any new work.

basically i am out of work except for 2 astropulse units i have left. my cida cards are idling and doing nothing. my rac is tanking.

#6 Since June 16th - no uploads, no downloads

Since mid June on only one of my 2 machines. It connects reliably when using a proxy, but only occasionally when not using proxy server.

---

I haven't had a new task in a very long time either. Is everything just plain down?

You may have the same issues as these people in this thread. Everything is working fine on my end.

---

Traveling through space at ~67,000mph!

Maybe I'm ok now. I just received a few tasks last night.

Surely I'm not the only one Still having trouble? (BUMP)

---

I Desire Peace and Justice, Jim Scott (Mod-Ret.)

Surely I'm not the only one Still having trouble? (BUMP)

Jim, in your originating post you asked "One Post Per Member Please!". That logically rules out followup posts, though you can rescind that of course.

For the record, I have not had any extended period of being completely unable to reach the servers.

                                                                  Joe

On a couple of machines I'm still trying to download units that were allocated 3 days ago. I'm getting the same as others here, short periods of fast downloading followed by much longer periods where the downloads grind to a halt and then the BOINC client goes into a 3 hour backoff. ;-P

I forgot to mention that the forums are also as slow as a wet week.

I've just done some pings and trace routes as as per Matt's request in the "HE Connection Problems" thread and they were all over the shop. All 4 attempts to ping x.13 showed at least 50% packet loss. Tracerts to that address had latencies of over a second for the last few hops on 3 out the 4 attempts. The 4th attempt went through sweet as. This was also at a time I could download units at reasonable speed.

One thing I noticed. Look at lines 11 to 16 of the trace route below where x.13 seems to have got itself in a loop. I'm not ofay enough with networking to know if it means anything or not. It did this 3 out of the 4 times I TR'ed the site.

Tracing route to boinc2.ssl.berkeley.edu [208.68.240.13]
over a maximum of 30 hops:

1 <1 ms <1 ms <1 ms 192.168.2.254
2 168 ms 110 ms 65 ms nexthop.sa.iinet.net.au [203.215.11.249]
3 65 ms 65 ms 64 ms po2.ade-pipe-bdr1.iinet.net.au [203.215.10.22]
4 88 ms 87 ms 89 ms ge-3-0-1-0.syd-mas-core1.iinet.net.au [203.215.2
0.70]
5 278 ms 280 ms 280 ms 34023.sydp06.cu.reach.com [134.159.160.57]
6 235 ms 238 ms 237 ms i-0-0-2-0.paix-core01.bx.reach.com [202.84.140.1
06]
7 236 ms 236 ms 235 ms i-2-1.paix01.bi.reach.com [202.84.251.101]
8 268 ms 259 ms 266 ms paix.he.net [198.32.176.20]
9 261 ms 260 ms 261 ms 64.71.140.42
10 302 ms * 302 ms 208.68.243.254
11 377 ms 359 ms * boinc2.ssl.berkeley.edu [208.68.240.13]
12 * * * Request timed out.
13 326 ms 332 ms * boinc2.ssl.berkeley.edu [208.68.240.13]
14 318 ms 330 ms * boinc2.ssl.berkeley.edu [208.68.240.13]
15 329 ms 339 ms * boinc2.ssl.berkeley.edu [208.68.240.13]
16 * * 496 ms boinc2.ssl.berkeley.edu [208.68.240.13]

Trace complete.

T.A.

No problems here.

---

TThrottle Control your temperatures. BoincTasks The best way to view BOINC. Anza Borrego Desert hiking.

With BOINC (6.12.33) shutdown, I get:

Microsoft Windows [Version 6.1.7601]
Copyright (c) 2009 Microsoft Corporation. All rights reserved.

C:\Windows\system32>tracert 208.68.240.13

Tracing route to boinc2.ssl.berkeley.edu [208.68.240.13]
over a maximum of 30 hops:

1 1 ms <1 ms <1 ms 192.168.1.1
2 21 ms 12 ms 27 ms c-67-174-200-1.hsd1.ca.comcast.net [67.174.200.1]
3 10 ms 8 ms 9 ms te-5-4-ur03.walnutcreek.ca.sfba.comcast.net [68.85.191.105]
4 16 ms 16 ms 14 ms te-1-6-0-3-ar01.sfsutro.ca.sfba.comcast.net [68.85.154.194]
5 15 ms 17 ms 15 ms pos-1-9-0-0-cr01.sanjose.ca.ibone.comcast.net [68.86.90.225]
6 22 ms 19 ms 19 ms pos-0-3-0-0-pe01.11greatoaks.ca.ibone.comcast.net [68.86.87.18]
7 19 ms 19 ms 27 ms 208.178.58.5
8 21 ms 19 ms 18 ms po4-20G.ar2.SJC2.gblx.net [67.16.142.214]
9 35 ms 18 ms 20 ms po1-20G.ar3.SJC2.gblx.net [67.16.134.26]
10 21 ms 19 ms 22 ms Hurrican-Electric-LLC.Port-channel100.ar3.SJC2.gblx.net [64.214.174.246]
11 19 ms 26 ms 20 ms 10gigabitethernet3-2.core1.pao1.he.net [72.52.92.69]
12 21 ms 24 ms 21 ms 64.71.140.42
13 60 ms * 62 ms 208.68.243.254
14 66 ms 75 ms * boinc2.ssl.berkeley.edu [208.68.240.13]
15 * * 83 ms boinc2.ssl.berkeley.edu [208.68.240.13]

Trace complete.

C:\Windows\system32>ping 208.68.240.13

Pinging 208.68.240.13 with 32 bytes of data:
Reply from 208.68.240.13: bytes=32 time=69ms TTL=51
Reply from 208.68.240.13: bytes=32 time=104ms TTL=51
Request timed out.
Request timed out.

Ping statistics for 208.68.240.13:
Packets: Sent = 4, Received = 2, Lost = 2 (50% loss),
Approximate round trip times in milli-seconds:
Minimum = 69ms, Maximum = 104ms, Average = 86ms

I see tracert NOT speedy at the SSL, and 50% ping loss. I'm on a fast (~20Mbps) cable connection, not using any proxies. BTW earlier today after manually nurse-maiding stalled downloads and forcing reporting to complete, I set No New Tasks, worked off & reported all cached MB WUs. My cruncher is going on hiatus from S@H until the root cause(s), be it SSL network / server, or borked BOINC 6.12.33 scheduler/netcode or some combination of these issues get fixed. Current situation is too frustrating and nurse-maiding it is too time-consuming.

Hopefully "I'll be back" when things get fixed.......

Edit: Here's another tracert & ping result:
C:\Windows\system32>tracert 208.68.240.13

Tracing route to boinc2.ssl.berkeley.edu [208.68.240.13]
over a maximum of 30 hops:

1 <1 ms <1 ms <1 ms 192.168.1.1
2 25 ms 19 ms 19 ms c-67-174-200-1.hsd1.ca.comcast.net [67.174.200.1]
3 10 ms 9 ms 9 ms te-5-4-ur03.walnutcreek.ca.sfba.comcast.net [68.85.191.105]
4 14 ms 28 ms 15 ms te-1-6-0-3-ar01.sfsutro.ca.sfba.comcast.net [68.85.154.194]
5 15 ms 16 ms 16 ms pos-1-9-0-0-cr01.sanjose.ca.ibone.comcast.net [68.86.90.225]
6 19 ms 19 ms 19 ms pos-0-3-0-0-pe01.11greatoaks.ca.ibone.comcast.net [68.86.87.18]
7 20 ms 22 ms 23 ms 208.178.58.5
8 18 ms 35 ms 19 ms po4-20G.ar2.SJC2.gblx.net [67.16.142.214]
9 19 ms 18 ms 19 ms po1-20G.ar3.SJC2.gblx.net [67.16.134.26]
10 19 ms 19 ms 24 ms Hurrican-Electric-LLC.Port-channel100.ar3.SJC2.gblx.net [64.214.174.246]
11 23 ms 21 ms 21 ms 10gigabitethernet3-2.core1.pao1.he.net [72.52.92.69]
12 76 ms 275 ms 283 ms 64.71.140.42
13 62 ms 61 ms 61 ms 208.68.243.254
14 99 ms 99 ms * boinc2.ssl.berkeley.edu [208.68.240.13]
15 212 ms 100 ms 110 ms boinc2.ssl.berkeley.edu [208.68.240.13]

Trace complete.

C:\Windows\system32>ping 208.68.240.13

Pinging 208.68.240.13 with 32 bytes of data:
Reply from 208.68.240.13: bytes=32 time=148ms TTL=51
Request timed out.
Reply from 208.68.240.13: bytes=32 time=126ms TTL=51
Reply from 208.68.240.13: bytes=32 time=120ms TTL=51

Ping statistics for 208.68.240.13:
Packets: Sent = 4, Received = 3, Lost = 1 (25% loss),
Approximate round trip times in milli-seconds:
Minimum = 120ms, Maximum = 148ms, Average = 131ms

---

Sabertooth Z77, i7-3770K@4.2GHz, GTX680, W8.1Pro x64
P5N32-E SLI, C2D E8400@3Ghz, GTX580, Win7SP1Pro x64 & PCLinuxOS2015 x64

Microsoft Windows XP [Version 5.1.2600]


Tracing route to boinc2.ssl.berkeley.edu [208.68.240.13]
over a maximum of 30 hops:

1 <1 ms <1 ms <1 ms 192.168.1.1
2 25 ms 26 ms 25 ms 66-38-56-1.static.bbtel.com [66.38.56.1]
3 26 ms 27 ms 25 ms bbtel-6509-g2-2.serial.blue.net [66.38.60.193]
4 26 ms 26 ms 25 ms rc-mlx8-ve31.serial.blue.net [66.38.58.169]
5 27 ms 27 ms 27 ms h1.126.55.139.static.ip.windstream.net [139.55.1
26.1]
6 29 ms 29 ms 29 ms h25.222.90.75.static.ip.windstream.net [75.90.22
2.25]
7 29 ms 29 ms 29 ms h36.254.213.151.static.ip.windstream.net [151.21
3.254.36]
8 47 ms 47 ms 46 ms h14.254.213.151.static.ip.windstream.net [151.21
3.254.14]
9 47 ms 46 ms 47 ms ip65-47-204-81.z204-47-65.customer.algx.net [65.
47.204.81]
10 47 ms 48 ms 47 ms v306.core1.dal1.he.net [64.71.189.217]
11 101 ms 100 ms 100 ms 10gigabitethernet1-2.core1.phx1.he.net [72.52.92
.253]
12 97 ms 96 ms 97 ms 10gigabitethernet2-2.core1.lax1.he.net [72.52.92
.249]
13 111 ms 116 ms 111 ms 10gigabitethernet1-3.core1.pao1.he.net [72.52.92
.21]
14 * * * Request timed out.
15 * * * Request timed out.

30 * * * Request timed out.

Trace complete.

This is what I get on .13, .16, .18 and.20 since June 15/16th.

---

I Desire Peace and Justice, Jim Scott (Mod-Ret.)

Microsoft Windows XP [Version 5.1.2600]
Tracing route to boinc2.ssl.berkeley.edu [208.68.240.13]
over a maximum of 30 hops:

Try using another dns server like the Google DNS 8.8.8.8 and 8.8.4.4

---

TThrottle Control your temperatures. BoincTasks The best way to view BOINC. Anza Borrego Desert hiking.

I am not having any issues {Comcast}.

[OT]
I have had good luck using "Domain Name Speed Benchmark"
http://www.grc.com/dns/benchmark.htm

I run it once a week and use the best DNS for my location. It changes all the time. Today Google DNS is at the bottom of the list when I checked.
[/OT]

---

...

I am not having any issues {Comcast}.

[OT]
I have had good luck using "Domain Name Speed Benchmark"
http://www.grc.com/dns/benchmark.htm

I run it once a week and use the best DNS for my location. It changes all the time. Today Google DNS is at the bottom of the list when I checked.
[/OT]

It is not a DNS problem, note that the test method is to do Ping and/or Trace Route to an IP address. This thread is an extension of the other threads related to total inability to reach the S@H servers since the middle of June from some areas.

All of us have occasional difficulties which come and go. That's a far different thing than a solid failure to get a connection.

                                                                   Joe