HE connection problems thread


log in

Advanced search

Message boards : Number crunching : HE connection problems thread

Previous · 1 · 2 · 3 · 4 · 5 · 6 . . . 25 · Next
Author Message
archae86
Send message
Joined: 31 Aug 99
Posts: 889
Credit: 1,572,794
RAC: 3
United States
Message 1122866 - Posted: 29 Jun 2011, 22:59:35 UTC - in response to Message 1122731.

At low traffic this morning I saw:
[quote]

min max avg loss server 43 178 50 1% .13 43 56 46 0% .16 43 107 46 0% .18 43 180 48 1% .20


Just a couple of minutes ago, about 3:50 p.m. PDT, with high traffic (91.36 "in", 18.12 "out" I saw:
min max avg loss server 83 181 105 28% .13 62 185 91 19% .16 52 190 91 25% .18 47 153 89 19% .20

Which hardly proves, but is consistent with a traffic dependent modulation of both the delay and the loss numbers from my location (Albuquerque/Comcast, as mentioned in my previous post).
____________

Profile Earl Needham
Send message
Joined: 28 May 99
Posts: 6
Credit: 142,938
RAC: 0
United States
Message 1122877 - Posted: 30 Jun 2011, 0:50:17 UTC - in response to Message 1122870.
Last modified: 30 Jun 2011, 0:53:45 UTC

I'm about 200 miles east of Albuquerque (in Clovis) and see much the same problem and events in the log. No communications since about the 15th of June.

1. Are you able to reach ANY of the upload, download, or scheduling servers?
No. Well, I'm not 100% sure, but I don't seem to be able to get any results form SETI at all.

2. When did you start having this problem?
About 15 June.

3. What is your ISP?
Plateautel.net

4. What is your geographic location?
Clovis, New Mexico, USA
3425.84N/10313.56W
DM84jk

5. What happens when you ping
208.68.240.13?
Request timed out
Request timed out
Request timed out
Request timed out
Ping statistics for 208.68.240.13
Packets: Sent = 4, Received = 0, Lost = 4 (100% loss).

All four do the same thing.

6. How about traceroutes of the above four addresses?
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 344 ms 317 ms 282 ms 067-209-192-002.plateautel.net [67.209.192.2]
3 422 ms 393 ms 415 ms 68-66-94-162.plateautel.net [68.66.94.162]
4 271 ms 144 ms 130 ms 68-66-94-194.plateautel.net [68.66.94.194]
5 320 ms 303 ms 365 ms ge-8-34.car2.Dallas1.Level3.net [4.59.196.89]
6 505 ms 386 ms 241 ms ae-2-70.edge4.Dallas3.Level3.net [4.69.145.77]
7 339 ms 331 ms 358 ms te2-2-10G.ar5.dal2.gblx.net [64.208.27.9]
8 664 ms 774 ms 823 ms Hurrican-Electric-LLC.Port-channel100.ar3.SJC2.g
blx.net [64.214.174.246]
9 512 ms 463 ms 496 ms 10gigabitethernet3-2.core1.pao1.he.net [72.52.92
.69]
10 * * * Request timed out.
11 * * * Request timed out.
12 * * * Request timed out.
13 * * * Request timed out.
14 * * * Request timed out.
15 * * * Request timed out.
16 * * * Request timed out.
17 * * * Request timed out.
18 * * * Request timed out.
19 * * * Request timed out.
20 * * * Request timed out.
21 * * * Request timed out.
22 * * * Request timed out.
23 * * * Request timed out.
24 * * * Request timed out.
25 * * * Request timed out.
26 * * * Request timed out.
27 * * * Request timed out.
28 * * * Request timed out.
29 * * * Request timed out.
30 * * * Request timed out.

Trace complete.

C:\Windows\system32>

***The other three are all the same, they die at step 10.


7. Or nslookups of the above four addresses?

C:\Users\Earl>nslookup 208.68.240.13
Server: resolver1.opendns.com
Address: 208.67.222.222

Name: boinc2.ssl.berkeley.edu
Address: 208.68.240.13


C:\Users\Earl>nslookup 208.68.240.16
Server: resolver1.opendns.com
Address: 208.67.222.222

Name: setiboincdata.ssl.berkeley.edu
Address: 208.68.240.16


C:\Users\Earl>nslookup 208.68.240.18
Server: resolver1.opendns.com
Address: 208.67.222.222

Name: boinc2.ssl.berkeley.edu
Address: 208.68.240.18


C:\Users\Earl>nslookup 208.68.240.20
Server: resolver1.opendns.com
Address: 208.67.222.222

Name: setiboinc.ssl.berkeley.edu
Address: 208.68.240.20
____________

Profile Jim_SProject donor
Avatar
Send message
Joined: 23 Feb 00
Posts: 4534
Credit: 19,246,052
RAC: 10,185
United States
Message 1122896 - Posted: 30 Jun 2011, 2:43:05 UTC

My Info hasn't changed since the 16th.
____________

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

Profile Sergio Santos
Send message
Joined: 29 Dec 03
Posts: 2
Credit: 2,488,842
RAC: 2,500
Portugal
Message 1122902 - Posted: 30 Jun 2011, 3:27:36 UTC - in response to Message 1122896.
Last modified: 30 Jun 2011, 3:28:27 UTC

Hi, i'm in Portugal and this problem started to happen in the 15th/16th June.

I couldn't connect to project servers, althouth the address is resolved, looks like it's a routing problem.

I have two service providers, through my "default one" -netcabo- i can't reach project servers either to upload or download work units, althoug i can reach the website.

I tried also another provider -TMN- through which I could (finally) upload and download workunits.

Regarding the question Matt asked, the addresses all resolve DNS-wise, but i can't reach the servers, pings timeout and traceroute is as follows:

1 2 ms <1 ms <1 ms 192.168.0.200
2 * * * Request timed out.
3 13 ms 9 ms 12 ms 10.137.204.137
4 20 ms 18 ms 18 ms 10.255.48.74
5 56 ms 53 ms 54 ms ix-0-2-1-0.tcore2.PV9-Lisbon.as6453.net [195.219
214.21]
6 54 ms 51 ms 72 ms 80.231.158.5
7 56 ms 50 ms 54 ms 80.231.158.10
8 49 ms 70 ms 51 ms if-2-2.tcore2.SV8-Highbridge.as6453.net [80.231.
39.1]
9 91 ms 53 ms 54 ms if-9-2.tcore1.L78-London.as6453.net [80.231.139.
8]
10 66 ms 53 ms 71 ms Vlan704.icore1.LDN-London.as6453.net [80.231.130
10]
11 56 ms 53 ms 51 ms te4-2-10G.ar7.lon3.gblx.net [64.215.195.237]
12 188 ms 196 ms 205 ms Hurrican-Electric-LLC.Port-channel100.ar3.SJC2.g
lx.net [64.214.174.246]
13 264 ms 268 ms 204 ms 10gigabitethernet3-2.core1.pao1.he.net [72.52.92
69]
14 * * * Request timed out.
15 * * * Request timed out.
16 * * * Request timed out.
17 * * * Request timed out.

[...] Snipped, it timed out until last tried hop (30th)

I have some background on net topology, it looks like the problem is on he.net or immediately after... Question is are packets reaching and not being sent back, or aren't they reaching at all? An HE tech would be a ton of help!
____________

Profile Jim_SProject donor
Avatar
Send message
Joined: 23 Feb 00
Posts: 4534
Credit: 19,246,052
RAC: 10,185
United States
Message 1122903 - Posted: 30 Jun 2011, 3:29:26 UTC
Last modified: 30 Jun 2011, 3:29:50 UTC

5 minutes ago...Something has changed,

Microsoft Windows XP [Version 5.1.2600]
(C) Copyright 1985-2001 Microsoft Corp.



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 26 ms 25 ms 26 ms 66-38-56-1.static.bbtel.com [66.38.56.1]
3 26 ms 25 ms 26 ms bbtel-6509-g2-2.serial.blue.net [66.38.60.193]
4 28 ms 28 ms 28 ms bg-6509-vlan32.serial.blue.net [66.38.60.49]
5 32 ms 32 ms 63 ms 65-127-33-81.dia.static.qwest.net [65.127.33.81]

6 36 ms 78 ms 36 ms chp-brdr-04.inet.qwest.net [67.14.8.238]
7 36 ms 36 ms 36 ms chi-bb1-link.telia.net [213.248.85.29]
8 121 ms * 121 ms sjo-bb1-link.telia.net [213.248.80.25]
9 84 ms 86 ms 84 ms hurricane-113209-sjo-bb1.c.telia.net [213.248.86
.54]
10 * * * Request timed out.
11 * * * Request timed out.
12 * * * Request timed out.

30 * * * Request timed out.

Trace complete.


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

1 <1 ms <1 ms <1 ms 192.168.1.1
2 26 ms 26 ms 25 ms 66-38-56-1.static.bbtel.com [66.38.56.1]
3 26 ms 25 ms 26 ms bbtel-6509-g2-2.serial.blue.net [66.38.60.193]
4 28 ms 28 ms 28 ms bg-6509-vlan32.serial.blue.net [66.38.60.49]
5 33 ms 32 ms 33 ms 65-127-33-81.dia.static.qwest.net [65.127.33.81]

6 80 ms 36 ms 35 ms chp-brdr-04.inet.qwest.net [67.14.8.238]
7 37 ms 36 ms 37 ms chi-bb1-link.telia.net [213.248.85.29]
8 112 ms 130 ms 129 ms sjo-bb1-link.telia.net [213.248.80.25]
9 84 ms 88 ms 84 ms hurricane-113209-sjo-bb1.c.telia.net [213.248.86
.54]
10 * * * Request timed out.
11 * * * Request timed out.
12 * * * Request timed out.

30 * * * Request timed out.

Trace complete.



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

1 <1 ms <1 ms <1 ms 192.168.1.1
2 26 ms 26 ms 26 ms 66-38-56-1.static.bbtel.com [66.38.56.1]
3 26 ms 28 ms 25 ms bbtel-6509-g2-2.serial.blue.net [66.38.60.193]
4 28 ms 27 ms 28 ms bg-6509-vlan32.serial.blue.net [66.38.60.49]
5 33 ms 32 ms 32 ms 65-127-33-81.dia.static.qwest.net [65.127.33.81]

6 36 ms 36 ms 36 ms chp-brdr-04.inet.qwest.net [67.14.8.238]
7 37 ms 37 ms 49 ms chi-bb1-link.telia.net [213.248.85.29]
8 132 ms 124 ms 124 ms sjo-bb1-link.telia.net [213.248.80.25]
9 84 ms 92 ms 84 ms hurricane-113209-sjo-bb1.c.telia.net [213.248.86
.54]
10 * * * Request timed out.
11 * * * Request timed out.
12 * * * Request timed out.

30 * * * Request timed out.
Trace complete.

Tracing route to 218.68.240.18 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 25 ms 26 ms bbtel-6509-g1-2.serial.blue.net [66.38.60.189]
4 33 ms 52 ms 203 ms bg-6509-vlan32.serial.blue.net [66.38.60.49]
5 32 ms 32 ms 33 ms 65-127-33-81.dia.static.qwest.net [65.127.33.81]

6 81 ms 80 ms 80 ms sjp-brdr-04.inet.qwest.net [67.14.34.38]
7 323 ms 331 ms 337 ms 63.146.27.86
8 552 ms 529 ms 524 ms 219.158.29.221
9 351 ms 360 ms 365 ms 219.158.5.129
10 329 ms 333 ms 337 ms 219.158.4.57
11 354 ms 367 ms 365 ms 219.158.20.22
12 355 ms * * 202.99.66.202
13 354 ms * * 117.8.1.10
14 * * * Request timed out.
15 * * * Request timed out.
16 * * * Request timed out.

30 * * * Request timed out.

Trace complete.
____________

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

pdelgado
Send message
Joined: 2 Jun 99
Posts: 58
Credit: 15,672,700
RAC: 261
United States
Message 1122904 - Posted: 30 Jun 2011, 3:36:24 UTC
Last modified: 30 Jun 2011, 3:37:32 UTC

Except for congestion I haven't had connectivity issues. Don't know if it helps but some data from a working connection may help HE narrow things down.

AT&T DSL in Miami, FL.

C:\Users\PDelgado>ping 208.68.240.13 Pinging 208.68.240.13 with 32 bytes of data: Reply from 208.68.240.13: bytes=32 time=128ms TTL=49 Reply from 208.68.240.13: bytes=32 time=132ms TTL=49 Reply from 208.68.240.13: bytes=32 time=137ms TTL=49 Reply from 208.68.240.13: bytes=32 time=134ms TTL=49 Ping statistics for 208.68.240.13: Packets: Sent = 4, Received = 4, Lost = 0 (0% loss), Approximate round trip times in milli-seconds: Minimum = 128ms, Maximum = 137ms, Average = 132ms C:\Users\PDelgado>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 pmd-gw [192.168.14.1] 2 10 ms * 10 ms 65.14.252.9 3 11 ms 12 ms 10 ms 70.151.241.77 4 23 ms 12 ms 13 ms 12.81.8.26 5 10 ms 9 ms 8 ms 12.81.8.9 6 22 ms 51 ms 54 ms 74.175.192.186 7 13 ms * 13 ms cr81.fldfl.ip.att.net [12.122.106.94] 8 12 ms 12 ms 11 ms fdlfl01jt.ip.att.net [12.122.81.29] 9 28 ms 32 ms 27 ms 208.178.58.145 10 99 ms 100 ms 87 ms Hurrican-Electric-LLC.Port-channel100.ar3.SJC2.gblx.net [64.214.174.246] 11 102 ms 87 ms 87 ms 10gigabitethernet3-2.core1.pao1.he.net [72.52.92.69] 12 94 ms 122 ms 94 ms 64.71.140.42 13 135 ms * 138 ms 208.68.243.254 14 * * * Request timed out. 15 * 169 ms 343 ms boinc2.ssl.berkeley.edu [208.68.240.13] Trace complete.

KB7RZF
Volunteer tester
Avatar
Send message
Joined: 15 Aug 99
Posts: 9464
Credit: 3,112,738
RAC: 10
United States
Message 1122918 - Posted: 30 Jun 2011, 5:26:41 UTC
Last modified: 30 Jun 2011, 5:27:23 UTC

Here's my info from just over the hill. Haven't had any problems, don't know if it helps. All info from Reno Nevada.


Microsoft Windows [Version 6.0.6002]
Copyright (c) 2006 Microsoft Corporation. All rights reserved.

C:\Users\Home>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 7 ms 7 ms rno-atm0-mtu0.greatbasin.net [216.82.142.1]
3 8 ms 7 ms 9 ms rno-core0-ge.greatbasin.net [207.228.35.136]
4 9 ms 26 ms 7 ms 67.138.231.149
5 18 ms 15 ms 15 ms ge2-20.cr01.renonvmp.integra.net [209.63.99.169]

6 16 ms 17 ms 15 ms tg13-2.cr02.sntdcabl.integra.net [209.63.97.158]

7 22 ms 14 ms 15 ms tg1-1.br01.plalcaxc.integra.net [209.63.115.14]

8 23 ms 17 ms 16 ms paix.he.net [198.32.176.20]
9 15 ms 15 ms 15 ms 64.71.140.42
10 63 ms 55 ms 54 ms 208.68.243.254
11 64 ms * 395 ms boinc2.ssl.berkeley.edu [208.68.240.13]

Trace complete.

C:\Users\Home>tracert 208.68.240.20

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

1 1 ms 1 ms 1 ms 192.168.1.1
2 67 ms 8 ms 7 ms rno-atm0-mtu0.greatbasin.net [216.82.142.1]
3 7 ms 12 ms 7 ms rno-core0-ge.greatbasin.net [207.228.35.136]
4 7 ms 7 ms 7 ms 67.138.231.149
5 141 ms 203 ms 199 ms ge2-20.cr01.renonvmp.integra.net [209.63.99.169]

6 40 ms 214 ms 15 ms tg13-2.cr02.sntdcabl.integra.net [209.63.97.158]

7 15 ms 14 ms 15 ms tg1-1.br01.plalcaxc.integra.net [209.63.115.14]

8 17 ms 18 ms 20 ms paix.he.net [198.32.176.20]
9 17 ms 15 ms 15 ms 64.71.140.42
10 50 ms 52 ms 55 ms 208.68.243.254
11 54 ms 56 ms * setiboinc.ssl.berkeley.edu [208.68.240.20]
12 55 ms 55 ms 55 ms setiboinc.ssl.berkeley.edu [208.68.240.20]

Trace complete.

Microsoft Windows [Version 6.0.6002]
Copyright (c) 2006 Microsoft Corporation. All rights reserved.

C:\Users\Home>tracert 208.68.240.18

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

1 <1 ms <1 ms <1 ms 192.168.1.1
2 7 ms 7 ms 7 ms rno-atm0-mtu0.greatbasin.net [216.82.142.1]
3 9 ms 6 ms 7 ms rno-core0-ge.greatbasin.net [207.228.35.136]
4 147 ms 9 ms 59 ms 67.138.231.149
5 41 ms 215 ms 207 ms ge2-20.cr01.renonvmp.integra.net [209.63.99.169]

6 46 ms 213 ms 149 ms tg13-2.cr02.sntdcabl.integra.net [209.63.97.158]

7 16 ms 15 ms 15 ms tg1-1.br01.plalcaxc.integra.net [209.63.115.14]

8 18 ms 25 ms 23 ms paix.he.net [198.32.176.20]
9 16 ms 15 ms 15 ms 64.71.140.42
10 57 ms 57 ms 55 ms 208.68.243.254
11 53 ms * 56 ms boinc2.ssl.berkeley.edu [208.68.240.18]

Trace complete.

C:\Users\Home>

Microsoft Windows [Version 6.0.6002]
Copyright (c) 2006 Microsoft Corporation. All rights reserved.

C:\Users\Home>tracert 208.68.240.20

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

1 <1 ms <1 ms <1 ms 192.168.1.1
2 7 ms 6 ms 8 ms rno-atm0-mtu0.greatbasin.net [216.82.142.1]
3 7 ms 7 ms 7 ms rno-core0-ge.greatbasin.net [207.228.35.136]
4 11 ms 7 ms 7 ms 67.138.231.149
5 15 ms 15 ms 15 ms ge2-20.cr01.renonvmp.integra.net [209.63.99.169]

6 32 ms 200 ms 204 ms tg13-2.cr02.sntdcabl.integra.net [209.63.97.158]

7 15 ms 14 ms 15 ms tg1-1.br01.plalcaxc.integra.net [209.63.115.14]

8 16 ms 17 ms 24 ms paix.he.net [198.32.176.20]
9 17 ms 16 ms 17 ms 64.71.140.42
10 * 57 ms 55 ms 208.68.243.254
11 53 ms 56 ms 56 ms setiboinc.ssl.berkeley.edu [208.68.240.20]

Trace complete.

C:\Users\Home>

Microsoft Windows [Version 6.0.6002]
Copyright (c) 2006 Microsoft Corporation. All rights reserved.

C:\Users\Home>ping 208.68.240.13

Pinging 208.68.240.13 with 32 bytes of data:
Reply from 208.68.240.13: bytes=32 time=76ms TTL=54
Request timed out.
Reply from 208.68.240.13: bytes=32 time=341ms TTL=54
Reply from 208.68.240.13: bytes=32 time=67ms TTL=54

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

C:\Users\Home>ping 208.68.240.16

Pinging 208.68.240.16 with 32 bytes of data:
Reply from 208.68.240.16: bytes=32 time=55ms TTL=54
Reply from 208.68.240.16: bytes=32 time=62ms TTL=54
Reply from 208.68.240.16: bytes=32 time=54ms TTL=54
Reply from 208.68.240.16: bytes=32 time=61ms TTL=54

Ping statistics for 208.68.240.16:
Packets: Sent = 4, Received = 4, Lost = 0 (0% loss),
Approximate round trip times in milli-seconds:
Minimum = 54ms, Maximum = 62ms, Average = 58ms

C:\Users\Home>ping .208.68.240.18
Ping request could not find host .208.68.240.18. Please check the name and try a
gain.

C:\Users\Home>ping 208.68.240.18

Pinging 208.68.240.18 with 32 bytes of data:
Reply from 208.68.240.18: bytes=32 time=56ms TTL=54
Reply from 208.68.240.18: bytes=32 time=60ms TTL=54
Reply from 208.68.240.18: bytes=32 time=94ms TTL=54
Reply from 208.68.240.18: bytes=32 time=56ms TTL=54

Ping statistics for 208.68.240.18:
Packets: Sent = 4, Received = 4, Lost = 0 (0% loss),
Approximate round trip times in milli-seconds:
Minimum = 56ms, Maximum = 94ms, Average = 66ms

C:\Users\Home>ping 208.68.240.20

Pinging 208.68.240.20 with 32 bytes of data:
Request timed out.
Request timed out.
Reply from 208.68.240.20: bytes=32 time=53ms TTL=54
Reply from 208.68.240.20: bytes=32 time=54ms TTL=54

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

C:\Users\Home>

Microsoft Windows [Version 6.0.6002]
Copyright (c) 2006 Microsoft Corporation. All rights reserved.

C:\Users\Home>nslookup 208.68.240.13
Server: ns1.greatbasin.net
Address: 207.228.35.42

Name: boinc2.ssl.berkeley.edu
Address: 208.68.240.13


C:\Users\Home>nslookup 208.68.240.16
Server: ns1.greatbasin.net
Address: 207.228.35.42

Name: setiboincdata.ssl.berkeley.edu
Address: 208.68.240.16


C:\Users\Home>nslookup 208.68.240.18
Server: ns1.greatbasin.net
Address: 207.228.35.42

Name: boinc2.ssl.berkeley.edu
Address: 208.68.240.18


C:\Users\Home>nslookup 208.68.240.20
Server: ns1.greatbasin.net
Address: 207.228.35.42

Name: setiboinc.ssl.berkeley.edu
Address: 208.68.240.20


C:\Users\Home>

Lasse Hægland
Send message
Joined: 6 Jul 99
Posts: 1
Credit: 109,259
RAC: 0
Norway
Message 1122954 - Posted: 30 Jun 2011, 8:06:20 UTC

I'm in Bergen, Norway, using an ISP called BKK.no. I'm using Mac OS X 10.6.8.

I don't know when the problems started as I don't monitor everything that closely, and there's usually tasks from a couple of other projects in between. As late as yesterday there were a couple of SETI-tasks ready, but now there are none (and SETI is set at ~77% resource share, so that's a bit less than expected, you might say).

Ping-results:

--- 208.68.240.13 ping statistics --- 10 packets transmitted, 8 packets received, 20.0% packet loss round-trip min/avg/max/stddev = 223.758/227.562/233.837/3.338 ms --- 208.68.240.16 ping statistics --- 10 packets transmitted, 9 packets received, 10.0% packet loss round-trip min/avg/max/stddev = 230.655/231.494/232.190/0.576 ms --- 208.68.240.18 ping statistics --- 10 packets transmitted, 8 packets received, 20.0% packet loss round-trip min/avg/max/stddev = 225.471/229.450/231.069/1.782 ms --- 208.68.240.20 ping statistics --- 10 packets transmitted, 7 packets received, 30.0% packet loss round-trip min/avg/max/stddev = 220.610/223.703/225.085/1.391 ms


Traceroute:

$ traceroute 208.68.240.18 traceroute to 208.68.240.18 (208.68.240.18), 64 hops max, 52 byte packets 1 73.85-200-224.bkkb.no (85.200.224.73) 0.999 ms 0.664 ms 0.499 ms 2 ba-f-gw1.bkkb.no (193.28.236.253) 12.439 ms 12.449 ms 12.426 ms 3 ba-f-gw1.bkkb.no (193.28.236.253) 12.453 ms 12.468 ms 12.501 ms 4 tengigabitethernet8-4.ar1.osl2.gblx.net (64.209.94.125) 14.952 ms 12.444 ms 12.507 ms 5 hurrican-electric-llc.port-channel100.ar3.sjc2.gblx.net (64.214.174.246) 193.894 ms 191.797 ms 209.926 ms 6 10gigabitethernet3-2.core1.pao1.he.net (72.52.92.69) 190.544 ms 192.018 ms 190.369 ms 7 64.71.140.42 (64.71.140.42) 191.711 ms 191.451 ms 207.818 ms 8 208.68.243.254 (208.68.243.254) 223.758 ms 224.746 ms 224.648 ms 9 * * * [***] 64 * * * $ $ traceroute 208.68.240.13 traceroute to 208.68.240.13 (208.68.240.13), 64 hops max, 52 byte packets 1 73.85-200-224.bkkb.no (85.200.224.73) 1.136 ms 0.646 ms 0.502 ms 2 ba-f-gw1.bkkb.no (193.28.236.253) 15.095 ms 12.253 ms 12.216 ms 3 ba-f-gw1.bkkb.no (193.28.236.253) 12.209 ms 12.182 ms 12.230 ms 4 tengigabitethernet8-4.ar1.osl2.gblx.net (64.209.94.125) 12.240 ms 12.168 ms 12.141 ms 5 hurrican-electric-llc.port-channel100.ar3.sjc2.gblx.net (64.214.174.246) 191.004 ms 190.667 ms 191.747 ms 6 10gigabitethernet3-2.core1.pao1.he.net (72.52.92.69) 196.954 ms 193.703 ms 190.253 ms 7 64.71.140.42 (64.71.140.42) 191.316 ms 191.239 ms 191.289 ms 8 208.68.243.254 (208.68.243.254) 224.567 ms * 224.003 ms 9 * * * [***] 64 * * * $ $ traceroute 208.68.240.16 traceroute to 208.68.240.16 (208.68.240.16), 64 hops max, 52 byte packets 1 73.85-200-224.bkkb.no (85.200.224.73) 1.060 ms 0.634 ms 0.497 ms 2 ba-f-gw1.bkkb.no (193.28.236.253) 12.451 ms 12.418 ms 12.448 ms 3 ba-f-gw1.bkkb.no (193.28.236.253) 12.447 ms 12.465 ms 13.339 ms 4 tengigabitethernet8-4.ar1.osl2.gblx.net (64.209.94.125) 12.482 ms 12.430 ms 12.433 ms 5 hurrican-electric-llc.port-channel100.ar3.sjc2.gblx.net (64.214.174.246) 191.204 ms 197.453 ms 199.945 ms 6 10gigabitethernet3-2.core1.pao1.he.net (72.52.92.69) 190.627 ms 196.227 ms 190.634 ms 7 64.71.140.42 (64.71.140.42) 191.463 ms 191.359 ms 191.877 ms 8 208.68.243.254 (208.68.243.254) 223.525 ms 224.217 ms 224.214 ms 9 * * * [***] 64 * * * $ $ traceroute 208.68.240.20 traceroute to 208.68.240.20 (208.68.240.20), 64 hops max, 52 byte packets 1 73.85-200-224.bkkb.no (85.200.224.73) 0.996 ms 0.642 ms 0.498 ms 2 ba-f-gw1.bkkb.no (193.28.236.253) 12.408 ms 12.439 ms 12.434 ms 3 ba-f-gw1.bkkb.no (193.28.236.253) 12.423 ms 12.435 ms 12.435 ms 4 tengigabitethernet8-4.ar1.osl2.gblx.net (64.209.94.125) 12.381 ms 12.373 ms 12.370 ms 5 hurrican-electric-llc.port-channel100.ar3.sjc2.gblx.net (64.214.174.246) 191.132 ms 203.335 ms 191.473 ms 6 10gigabitethernet3-2.core1.pao1.he.net (72.52.92.69) 228.124 ms 194.639 ms 195.364 ms 7 64.71.140.42 (64.71.140.42) 191.332 ms 298.075 ms 307.279 ms 8 * 208.68.243.254 (208.68.243.254) 220.186 ms 220.153 ms 9 * * * [***] 64 * * * $


nslookup:

$ nslookup 208.68.240.13 Server: 195.159.0.100 Address: 195.159.0.100#53 Non-authoritative answer: 13.240.68.208.in-addr.arpa name = boinc2.ssl.berkeley.edu. Authoritative answers can be found from: 240.68.208.in-addr.arpa nameserver = adns1.berkeley.edu. 240.68.208.in-addr.arpa nameserver = adns2.berkeley.edu. adns1.berkeley.edu has AAAA address 2607:f140:ffff:fffe::3 adns2.berkeley.edu internet address = 128.32.136.14 adns2.berkeley.edu has AAAA address 2607:f140:ffff:fffe::e $ nslookup 208.68.240.16 Server: 195.159.0.100 Address: 195.159.0.100#53 Non-authoritative answer: 16.240.68.208.in-addr.arpa name = setiboincdata.ssl.berkeley.edu. Authoritative answers can be found from: 240.68.208.in-addr.arpa nameserver = adns1.berkeley.edu. 240.68.208.in-addr.arpa nameserver = adns2.berkeley.edu. adns1.berkeley.edu has AAAA address 2607:f140:ffff:fffe::3 adns2.berkeley.edu internet address = 128.32.136.14 adns2.berkeley.edu has AAAA address 2607:f140:ffff:fffe::e $ nslookup 208.68.240.18 Server: 195.159.0.100 Address: 195.159.0.100#53 Non-authoritative answer: 18.240.68.208.in-addr.arpa name = boinc2.ssl.berkeley.edu. Authoritative answers can be found from: 240.68.208.in-addr.arpa nameserver = adns2.berkeley.edu. 240.68.208.in-addr.arpa nameserver = adns1.berkeley.edu. adns1.berkeley.edu has AAAA address 2607:f140:ffff:fffe::3 adns2.berkeley.edu internet address = 128.32.136.14 adns2.berkeley.edu has AAAA address 2607:f140:ffff:fffe::e $ nslookup 208.68.240.20 Server: 195.159.0.100 Address: 195.159.0.100#53 Non-authoritative answer: 20.240.68.208.in-addr.arpa name = setiboinc.ssl.berkeley.edu. Authoritative answers can be found from: 240.68.208.in-addr.arpa nameserver = adns1.berkeley.edu. 240.68.208.in-addr.arpa nameserver = adns2.berkeley.edu. adns1.berkeley.edu has AAAA address 2607:f140:ffff:fffe::3 adns2.berkeley.edu internet address = 128.32.136.14 adns2.berkeley.edu has AAAA address 2607:f140:ffff:fffe::e

____________

Fanqua
Send message
Joined: 3 May 11
Posts: 2
Credit: 22,042
RAC: 0
Germany
Message 1123148 - Posted: 30 Jun 2011, 23:09:12 UTC

I'm from Hamburg, Germany. No communications since about the 15th of June.

1. Are you able to reach ANY of the upload, download, or scheduling servers?
No. I don't seem to be able to get any results form SETI at all. Nothing has been down- or uploaded since two weeks. BOINC-Client tells me, that the upload has failed and the project servers may be temporarily down.

2. When did you start having this problem?
About 15 June.

3. What is your ISP?
www.alice-dsl.de/

4. What is your geographic location?
Hamburg, Germany

5. What happens when you ping
208.68.240.13?
Request timed out
Request timed out
Request timed out
Request timed out
Ping statistics for 208.68.240.13
Packets: Sent = 4, Received = 0, Lost = 4 (100% loss).

All four do the same thing.

6. and 7.: Don't know, how to do these test...but I'm sure, they would fail as well...

Jaime Lima
Send message
Joined: 20 Jun 02
Posts: 2
Credit: 15,577,295
RAC: 8,507
Portugal
Message 1123174 - Posted: 1 Jul 2011, 0:22:59 UTC - in response to Message 1122104.

1. No
2. 15 June
3. Netcabo Portugal SA - 89.152.7.93
4. Portugal
5. Request Timed Out
____________

Profile Sergio Santos
Send message
Joined: 29 Dec 03
Posts: 2
Credit: 2,488,842
RAC: 2,500
Portugal
Message 1123547 - Posted: 1 Jul 2011, 21:37:51 UTC

Are there any measures, besides collecting information on affected people, being taken?

The problem still remains, for what i've read, it is clear the problem arose 15th/16th of June, and packets SEEM to stop within HE or immediatly after.
____________

Fanqua
Send message
Joined: 3 May 11
Posts: 2
Credit: 22,042
RAC: 0
Germany
Message 1123867 - Posted: 2 Jul 2011, 12:11:00 UTC

Is there any solution in sight? I mean, the problem still remains, I can't upload nor download anything! Could please someone tell us, what's going on???

reklov
Volunteer tester
Send message
Joined: 9 Apr 11
Posts: 1
Credit: 10,664
RAC: 0
Germany
Message 1123880 - Posted: 2 Jul 2011, 13:13:55 UTC - in response to Message 1122104.
Last modified: 2 Jul 2011, 13:29:42 UTC

1. Are you able to reach ANY of the upload, download, or scheduling servers?

The web pages I can reach with the browser. But BOINC manager reports:
02.07.2011 15:06:21 | SETI@home | update requested by user
02.07.2011 15:06:21 | SETI@home | Sending scheduler request: Requested by user.
02.07.2011 15:06:21 | SETI@home | Requesting new tasks for CPU and ATI GPU
02.07.2011 15:06:44 | SETI@home | Scheduler request failed: Couldn't connect to server

2. When did you start having this problem?

Last update of BOINC manager stats was on June 15th, 2011, for SETI@home and SETI@home beta

3. What is your ISP?

Alice https://www.alice-dsl.de, a Telefonica company

4. What is your geographic location?

Germany, Baden-Wuerttemberg, 48° N, 9° E

5. What happens when you ping 208.68.240.13? 208.68.240.16? 208.68.240.18? 208.68.240.20?

timeout, all packets lost - for all of the above 4 addresses

6. How about traceroutes of the above four addresses?

C:\>tracert 208.68.240.13

Routenverfolgung zu boinc2.ssl.berkeley.edu [208.68.240.13] über maximal 30 Absc
hnitte:

1 2 ms <1 ms <1 ms 10.0.0.1
2 28 ms 26 ms 26 ms lo1.br60.fra.de.hansenet.net [213.191.64.48]
3 75 ms 26 ms 27 ms ge-7-3-4-0.xd02.fra.de.hansenet.net [62.109.71.126]
4 26 ms 44 ms 26 ms ae1-0.pr03.decix.de.hansenet.net [213.191.66.142]
5 34 ms 28 ms 27 ms 20gigabitethernet4-3.core1.fra1.he.net [80.81.192.172]
6 37 ms 37 ms 37 ms 10gigabitethernet1-4.core1.par2.he.net [184.105.213.162]
7 116 ms 121 ms 124 ms 10gigabitethernet7-1.core1.ash1.he.net [184.105.213.93]
8 188 ms 197 ms 187 ms 10gigabitethernet7-4.core1.pao1.he.net [184.105.213.177]
9 * * * Zeitüberschreitung der Anforderung. (timeout)
10 * * * Zeitüberschreitung der Anforderung.

7. Or nslookups of the above four addresses?

a) Name: boinc2.ssl.berkeley.edu
Address: 208.68.240.13
b)Name: setiboincdata.ssl.berkeley.edu
Address: 208.68.240.16
c) Name: boinc2.ssl.berkeley.edu
Address: 208.68.240.18
d) Name: setiboinc.ssl.berkeley.edu
Address: 208.68.240.20

Profile Donald L. JohnsonProject donor
Avatar
Send message
Joined: 5 Aug 02
Posts: 6368
Credit: 800,376
RAC: 1,640
United States
Message 1123986 - Posted: 2 Jul 2011, 18:05:13 UTC - in response to Message 1123867.

Is there any solution in sight? I mean, the problem still remains, I can't upload nor download anything! Could please someone tell us, what's going on???

Please remember that it is a Holiday weekend in the United States.
ALL the Seti@Home staff are part-time employees, and are not usually allowed to work week-ends.
If any of the most-knowledgeable Volunteers (Joe S, or Richard H, among others) has knowledge to share, they would probably have done so already.

So please relax, and be patient.
Try the proxy server option provided in the other thread.
We may hear something on Tuesday.
Or maybe not, if there is nothing to report.
____________
Donald
Infernal Optimist / Submariner, retired

Profile Mike BaderProject donor
Volunteer tester
Avatar
Send message
Joined: 18 May 99
Posts: 176
Credit: 8,074,286
RAC: 1,993
Message 1123994 - Posted: 2 Jul 2011, 18:33:00 UTC - in response to Message 1123986.

You might want to google hurricane electric and see what other problems people are having. Not that SETI can do much about it.
http://www.yelp.com/biz/hurricane-electric-fremont

____________
Mike Bader
BOINC V7.4.37
http://setiathome.berkeley.edu/team_join_form.php?id=5 - Join Our International Team
[img]http://boinc.mundayweb.com/one/stats.php?

Profile Mike BaderProject donor
Volunteer tester
Avatar
Send message
Joined: 18 May 99
Posts: 176
Credit: 8,074,286
RAC: 1,993
Message 1124052 - Posted: 2 Jul 2011, 21:07:48 UTC - in response to Message 1123994.

I'm finding reports on other websites of current problems with HE DNS servers.
I assume they know that already and are working on it.
Guess we just have to wait.

____________
Mike Bader
BOINC V7.4.37
http://setiathome.berkeley.edu/team_join_form.php?id=5 - Join Our International Team
[img]http://boinc.mundayweb.com/one/stats.php?

Profile Geek@Play
Volunteer tester
Avatar
Send message
Joined: 31 Jul 01
Posts: 2467
Credit: 86,144,272
RAC: 279
United States
Message 1124062 - Posted: 2 Jul 2011, 21:29:17 UTC
Last modified: 2 Jul 2011, 21:29:36 UTC

Was the birdy able to escape from the cats??
____________
Boinc....Boinc....Boinc....Boinc....

dd3vm
Send message
Joined: 2 Jun 99
Posts: 2
Credit: 118,464
RAC: 54
Germany
Message 1124164 - Posted: 3 Jul 2011, 2:09:51 UTC - in response to Message 1122395.
Last modified: 3 Jul 2011, 2:27:24 UTC

I have them same problem and the same data (ISP / location).
For the test the win firewall was complete off (open).
Reset, delete and renew seti@home project and boinc installation
with no result.
All traces stops at the *.he.net (hurrican electric)

Communication with rosetta@home and poem@home is still working fine.

Please help.

Best regards
____________

Previous · 1 · 2 · 3 · 4 · 5 · 6 . . . 25 · Next

Message boards : Number crunching : HE connection problems thread

Copyright © 2014 University of California