HE connection problems thread


log in

Advanced search

Message boards : Number crunching : HE connection problems thread

1 · 2 · 3 · 4 . . . 25 · Next
Author Message
Profile Matt Lebofsky
Volunteer moderator
Project administrator
Project developer
Project scientist
Avatar
Send message
Joined: 1 Mar 99
Posts: 1384
Credit: 74,079
RAC: 0
United States
Message 1122104 - Posted: 27 Jun 2011, 18:58:13 UTC

Hey all - I'm trying to characterize this current problem where some users are unable to reach any of our servers through Hurricane Electric. If possible please answer in this thread the following questions (feel free to leave out anything you want to keep private, or don't understand):

1. Are you able to reach ANY of the upload, download, or scheduling servers?
2. When did you start having this problem?
3. What is your ISP?
4. What is your geographic location?
5. What happens when you ping 208.68.240.13? 208.68.240.16? 208.68.240.18? 208.68.240.20?
6. How about traceroutes of the above four addresses?
7. Or nslookups of the above four addresses?

Or if you know what the exact problem is (or if there isn't really a single problem but a set of problems) that would be useful, too.

Thanks!

- Matt

____________
-- BOINC/SETI@home network/web/science/development person
-- "Any idiot can have a good idea. What is hard is to do it." - Jeanne-Claude

Profile ML1
Volunteer tester
Send message
Joined: 25 Nov 01
Posts: 7945
Credit: 4,011,543
RAC: 862
United Kingdom
Message 1122121 - Posted: 27 Jun 2011, 19:17:00 UTC
Last modified: 27 Jun 2011, 19:20:19 UTC

OK, from the UK I'm seeing 13% to 33% ping packet loss...

I'm connecting ok but I could well see some clients giving up:


ping -c 30 208.68.240.13
PING 208.68.240.13 (208.68.240.13) 56(84) bytes of data.
64 bytes from 208.68.240.13: icmp_seq=2 ttl=53 time=222 ms

[...]

--- 208.68.240.13 ping statistics ---
30 packets transmitted, 21 received, 30% packet loss, time 30038ms
rtt min/avg/max/mdev = 215.788/244.430/313.496/21.444 ms


ping -c 30 208.68.240.16
PING 208.68.240.16 (208.68.240.16) 56(84) bytes of data.
64 bytes from 208.68.240.16: icmp_seq=2 ttl=53 time=182 ms

[...]

--- 208.68.240.16 ping statistics ---
30 packets transmitted, 23 received, 23% packet loss, time 30004ms
rtt min/avg/max/mdev = 182.939/214.952/228.070/8.545 ms


ping -c 30 208.68.240.18
PING 208.68.240.18 (208.68.240.18) 56(84) bytes of data.
64 bytes from 208.68.240.18: icmp_seq=3 ttl=53 time=212 ms

[...]

--- 208.68.240.18 ping statistics ---
30 packets transmitted, 20 received, 33% packet loss, time 30035ms
rtt min/avg/max/mdev = 176.886/213.438/259.689/14.310 ms


ping -c 30 208.68.240.20
PING 208.68.240.20 (208.68.240.20) 56(84) bytes of data.
64 bytes from 208.68.240.20: icmp_seq=1 ttl=53 time=215 ms

[...]

--- 208.68.240.20 ping statistics ---
30 packets transmitted, 26 received, 13% packet loss, time 30030ms
rtt min/avg/max/mdev = 175.044/215.254/231.320/9.996 ms



The s@h website is fine.

ping -c 30 setiathome.berkeley.edu
PING setiathome.berkeley.edu (128.32.18.150) 56(84) bytes of data.
64 bytes from thinman.ssl.berkeley.edu (128.32.18.150): icmp_seq=1 ttl=46 time=160 ms

[...]

--- setiathome.berkeley.edu ping statistics ---
30 packets transmitted, 30 received, 0% packet loss, time 29200ms
rtt min/avg/max/mdev = 158.496/161.911/180.077/4.584 ms



And tracing one example:

traceroute -I 208.68.240.13
traceroute to 208.68.240.13 (208.68.240.13), 30 hops max, 60 byte packets


5 tele-ic-1-as0-0.network.virginmedia.net (62.253.184.2) 12.881 ms 12.913 ms 12.930 ms
6 10gigabitethernet1-1.core1.lon1.he.net (195.66.224.21) 20.120 ms 17.300 ms 17.248 ms
7 10gigabitethernet6-3.core1.ash1.he.net (72.52.92.137) 93.906 ms 92.609 ms 93.855 ms
8 10gigabitethernet7-4.core1.pao1.he.net (184.105.213.177) 170.092 ms 177.067 ms 176.996 ms
9 64.71.140.42 (64.71.140.42) 175.866 ms 175.750 ms 170.731 ms
10 * * *
11 * * *
12 * * *
13 * boinc2.ssl.berkeley.edu (208.68.240.13) 233.103 ms *



Hope that helps.

Something congested or overheated?

Good luck,
Martin
____________
See new freedom: Mageia4
Linux Voice See & try out your OS Freedom!
The Future is what We make IT (GPLv3)

Profile [seti.international] Dirk Sadowski
Volunteer tester
Avatar
Send message
Joined: 6 Apr 07
Posts: 6970
Credit: 57,117,241
RAC: 22,012
Germany
Message 1122123 - Posted: 27 Jun 2011, 19:22:16 UTC
Last modified: 27 Jun 2011, 19:22:51 UTC

Maybe an easy explanation for noobs how to ping, traceroutes and nslookups?

;-)


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



>Das Deutsche Cafe. The German Cafe.<

Profile ML1
Volunteer tester
Send message
Joined: 25 Nov 01
Posts: 7945
Credit: 4,011,543
RAC: 862
United Kingdom
Message 1122126 - Posted: 27 Jun 2011, 19:25:23 UTC
Last modified: 27 Jun 2011, 19:30:46 UTC

OK, you've got data loss at:

208.68.243.254

or between:

64.71.140.42 and 208.68.243.254

Regards,
Martin


[edit]
After a few more traceroutes, looks like 208.68.243.254 is repeatedly going offline or is just not responding for a few seconds at a time. Inbound port problem or node problem? Or outbound problem for 64.71.140.42? Or problem with the link between those two?

Anyone else seeing that?
[/edit]
____________
See new freedom: Mageia4
Linux Voice See & try out your OS Freedom!
The Future is what We make IT (GPLv3)

Profile Cliff Harding
Volunteer tester
Avatar
Send message
Joined: 18 Aug 99
Posts: 825
Credit: 46,520,670
RAC: 14,272
United States
Message 1122129 - Posted: 27 Jun 2011, 19:27:49 UTC - in response to Message 1122104.
Last modified: 27 Jun 2011, 20:16:07 UTC

1) Can up reach d/l servers, cannot reach scheduler server.
2) First noticed at 07:30 eastern time
3) ISP - Earthlink/ Domain - Verizon
4) Mid-Atlantic (Philadelphia, Pa)
5) ping 208.68.240.13 - Request Timed out 4 pacs sent 2 pacs rec (50% loss)
208.68.240.16 - 4 pacs sent 4 pacs received (0% loss)
208.68.240.18 - 4 pacs sent 4 pacs received (0% loss)
208.68.240.1620 - 4 pacs sent 4 pacs received (0% loss)
6) Trace route
Microsoft Windows [Version 6.1.7601]
Copyright (c) 2009 Microsoft Corporation. All rights reserved.

C:\Users\Cliff Harding>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 Wireless_Broadband_Router.home [192.168.1.1]
2 8 ms 4 ms 4 ms L100.PHLAPA-VFTTP-156.verizon-gni.net [108.2.126
.1]
3 57 ms 7 ms 9 ms G0-3-3-4.PHLAPA-LCR-21.verizon-gni.net [130.81.1
78.14]
4 10 ms 6 ms 9 ms so-9-0-0-0.PHIL-BB-RTR1.verizon-gni.net [130.81.
22.58]
5 64 ms 28 ms 12 ms 0.xe-3-0-1.XL3.IAD8.ALTER.NET [152.63.3.61]
6 17 ms 13 ms 15 ms TenGigE0-6-0-0.GW1.IAD8.ALTER.NET [152.63.36.45]

7 15 ms 14 ms 14 ms teliasonera-gw.customer.alter.net [63.125.125.42
]
8 88 ms 85 ms 88 ms sjo-bb1-link.telia.net [80.91.248.204]
9 96 ms 105 ms 93 ms hurricane-113209-sjo-bb1.c.telia.net [213.248.86
.54]
10 87 ms 88 ms 87 ms 64.71.140.42
11 130 ms 130 ms 127 ms 208.68.243.254
12 * * * Request timed out.
13 176 ms 152 ms 462 ms boinc2.ssl.berkeley.edu [208.68.240.13]

Trace complete.

C:\Users\Cliff Harding>tracert 208.68.240.16

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

1 <1 ms <1 ms <1 ms Wireless_Broadband_Router.home [192.168.1.1]
2 14 ms 8 ms 8 ms L100.PHLAPA-VFTTP-156.verizon-gni.net [108.2.126
.1]
3 8 ms 8 ms 9 ms G0-3-3-4.PHLAPA-LCR-22.verizon-gni.net [130.81.1
78.138]
4 10 ms 8 ms 9 ms so-3-1-0-0.PHIL-BB-RTR2.verizon-gni.net [130.81.
22.60]
5 7 ms 7 ms 9 ms 0.ge-7-3-0.XL4.PHL6.ALTER.NET [152.63.3.41]
6 14 ms 14 ms 14 ms 0.so-6-0-1.XL4.IAD8.ALTER.NET [152.63.36.209]
7 14 ms 14 ms 13 ms 0.TenGigE0-5-4-0.GW1.IAD8.ALTER.NET [152.63.33.4
5]
8 17 ms 14 ms 13 ms teliasonera-test-gw.customer.alter.net [63.65.76
.190]
9 91 ms 88 ms 91 ms sjo-bb1-link.telia.net [80.91.252.220]
10 88 ms 94 ms 99 ms hurricane-113209-sjo-bb1.c.telia.net [213.248.86
.54]
11 89 ms 87 ms 87 ms 64.71.140.42
12 129 ms * * 208.68.243.254
13 129 ms 129 ms 129 ms setiboincdata.ssl.berkeley.edu [208.68.240.16]

Trace complete.

C:\Users\Cliff Harding>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 Wireless_Broadband_Router.home [192.168.1.1]
2 6 ms 9 ms 4 ms L100.PHLAPA-VFTTP-156.verizon-gni.net [108.2.126
.1]
3 8 ms 7 ms 9 ms G0-3-3-4.PHLAPA-LCR-22.verizon-gni.net [130.81.1
78.138]
4 7 ms 9 ms 14 ms so-3-1-0-0.PHIL-BB-RTR2.verizon-gni.net [130.81.
22.60]
5 6 ms 10 ms 8 ms 0.ge-7-3-0.XL4.PHL6.ALTER.NET [152.63.3.41]
6 18 ms 14 ms 13 ms 0.so-6-0-1.XL4.IAD8.ALTER.NET [152.63.36.209]
7 14 ms 14 ms 12 ms TenGigE0-7-2-0.GW1.IAD8.ALTER.NET [152.63.35.153
]
8 15 ms 15 ms 13 ms teliasonera-gw.customer.alter.net [63.125.125.42
]
9 89 ms 88 ms 87 ms sjo-bb1-link.telia.net [80.91.252.220]
10 87 ms 95 ms 85 ms hurricane-113209-sjo-bb1.c.telia.net [213.248.86
.54]
11 163 ms 282 ms 355 ms 64.71.140.42
12 124 ms * 126 ms 208.68.243.254
13 127 ms 129 ms * boinc2.ssl.berkeley.edu [208.68.240.18]
14 * 130 ms 130 ms boinc2.ssl.berkeley.edu [208.68.240.18]

Trace complete.

C:\Users\Cliff Harding>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 Wireless_Broadband_Router.home [192.168.1.1]
2 5 ms 4 ms 4 ms L100.PHLAPA-VFTTP-156.verizon-gni.net [108.2.126
.1]
3 8 ms 6 ms 9 ms G0-3-3-4.PHLAPA-LCR-22.verizon-gni.net [130.81.1
78.138]
4 6 ms 9 ms 9 ms so-3-1-0-0.PHIL-BB-RTR2.verizon-gni.net [130.81.
22.60]
5 7 ms 9 ms 9 ms 0.so-7-0-0.XL4.PHL6.ALTER.NET [152.63.3.81]
6 17 ms 13 ms 14 ms 0.so-6-0-1.XL4.IAD8.ALTER.NET [152.63.36.209]
7 13 ms 14 ms 13 ms TenGigE0-7-2-0.GW1.IAD8.ALTER.NET [152.63.35.153
]
8 17 ms 13 ms 14 ms teliasonera-gw.customer.alter.net [63.125.125.42
]
9 89 ms 86 ms 96 ms sjo-bb1-link.telia.net [80.91.248.188]
10 89 ms 99 ms 129 ms hurricane-113209-sjo-bb1.c.telia.net [213.248.86
.54]
11 85 ms 88 ms 87 ms 64.71.140.42
12 127 ms 126 ms 127 ms 208.68.243.254
13 124 ms 125 ms 128 ms setiboinc.ssl.berkeley.edu [208.68.240.20]

Trace complete.

C:\Users\Cliff Harding>




7) nslookup 208.68.240.13 - boinc2.ssl.berekely.edu
208.68.240.16 - setiboincdata.ssl.berekely.edu
208.68.240.18 - boinc2.ssl.berekely.edu
208.68.240.13 - boinc.ssl.berekely.edu

Profile dnolan
Avatar
Send message
Joined: 30 Aug 01
Posts: 1245
Credit: 43,714,708
RAC: 42,113
United States
Message 1122131 - Posted: 27 Jun 2011, 19:28:59 UTC - in response to Message 1122123.
Last modified: 27 Jun 2011, 19:30:39 UTC

Maybe an easy explanation for noobs how to ping, traceroutes and nslookups?



For Windows users, go to
Accessories -> Command Prompt
and in the terminal screen that opens, one can type
ping XXX.YYY.ZZZ.123
tracert XXX.YYY.ZZZ.123
nslookup XXX.YYY.ZZZ.123

[edit] Where XXX.YYY.ZZZ.123 is the IP, for example,
ping 208.68.240.18
[/edit]

-Dave
____________

Profile ML1
Volunteer tester
Send message
Joined: 25 Nov 01
Posts: 7945
Credit: 4,011,543
RAC: 862
United Kingdom
Message 1122136 - Posted: 27 Jun 2011, 19:37:28 UTC - in response to Message 1122126.
Last modified: 27 Jun 2011, 19:39:29 UTC

OK, you've got data loss at:

208.68.243.254

or between:

64.71.140.42 and 208.68.243.254

Regards,
Martin


[edit]
After a few more traceroutes, looks like 208.68.243.254 is repeatedly going offline or is just not responding for a few seconds at a time. Inbound port problem or node problem? Or outbound problem for 64.71.140.42? Or problem with the link between those two?

Anyone else seeing that?
[/edit]

Best case (works ok-ish) is:

traceroute -I 208.68.240.13
traceroute to 208.68.240.13 (208.68.240.13), 30 hops max, 60 byte packets

5 tele-ic-1-as0-0.network.virginmedia.net (62.253.184.2) 12.748 ms 12.782 ms 12.780 ms
6 10gigabitethernet1-1.core1.lon1.he.net (195.66.224.21) 22.597 ms 18.336 ms 18.270 ms
7 10gigabitethernet6-3.core1.ash1.he.net (72.52.92.137) 104.924 ms 104.902 ms 104.760 ms
8 10gigabitethernet7-4.core1.pao1.he.net (184.105.213.177) 179.723 ms 179.739 ms 179.891 ms
9 64.71.140.42 (64.71.140.42) 174.886 ms 172.619 ms 172.515 ms
10 208.68.243.254 (208.68.243.254) 217.558 ms * 216.050 ms
11 boinc2.ssl.berkeley.edu (208.68.240.13) 221.252 ms * *



Worst case seen is:

traceroute -I 208.68.240.13
traceroute to 208.68.240.13 (208.68.240.13), 30 hops max, 60 byte packets

5 tele-ic-1-as0-0.network.virginmedia.net (62.253.184.2) 13.993 ms 14.044 ms 14.062 ms
6 10gigabitethernet1-1.core1.lon1.he.net (195.66.224.21) 18.173 ms 42.386 ms 42.223 ms
7 10gigabitethernet6-3.core1.ash1.he.net (72.52.92.137) 126.265 ms 126.247 ms 126.215 ms
8 10gigabitethernet7-4.core1.pao1.he.net (184.105.213.177) 199.395 ms 198.686 ms 198.538 ms
9 64.71.140.42 (64.71.140.42) 197.372 ms 196.550 ms 199.715 ms
10 208.68.243.254 (208.68.243.254) 238.127 ms 238.010 ms *
11 * * *
12 * * *
13 * * *
14 * * *
15 boinc2.ssl.berkeley.edu (208.68.240.13) 234.994 ms 234.895 ms *


(That last case shows about a 13 seconds pause before the next ping is returned.)


Hope that helps.

Keep searchin'
Martin
____________
See new freedom: Mageia4
Linux Voice See & try out your OS Freedom!
The Future is what We make IT (GPLv3)

Profile ML1
Volunteer tester
Send message
Joined: 25 Nov 01
Posts: 7945
Credit: 4,011,543
RAC: 862
United Kingdom
Message 1122153 - Posted: 27 Jun 2011, 19:58:30 UTC - in response to Message 1122136.
Last modified: 27 Jun 2011, 19:59:46 UTC

OK, you've got data loss at:

208.68.243.254

or between:

64.71.140.42 and 208.68.243.254


Note: That's just for my one example and my 'guess'. Other examples for Berkeley to diagnose from elsewhere are still needed to compare/confirm or to find whatever else might be a problem...


Keep searchin'
Martin
____________
See new freedom: Mageia4
Linux Voice See & try out your OS Freedom!
The Future is what We make IT (GPLv3)

Profile HAL9000
Volunteer tester
Avatar
Send message
Joined: 11 Sep 99
Posts: 3571
Credit: 98,101,158
RAC: 77,173
United States
Message 1122155 - Posted: 27 Jun 2011, 20:16:05 UTC

Normally I see a lot of these connections issues, or they are minor enough I don't notice them.

1. At the moment downloads are slow and/or timing out. However, The connection graph looks a bit busy right now.
2. N/A
3. Home: Comcast
3. Work: Verizon, level3, & AT&T (We have lines form all 3 so my source IP could be from any one of those.)
4. Philadelphia / S. NJ area.
I did these tests at work in my software test lab on a dirty Win 7 box.
5. Percent loss for 30 pings to: .13-30%, .16-25%, .18-26%, .20-30%.
6. I got one good one.
This is the first hop after the public IP address


6 2 ms 2 ms 2 ms 500.Serial3-7.GW4.PHL1.ALTER.NET [157.130.19.53]
7 3 ms 3 ms 3 ms 0.so-5-1-1.XL3.PHL6.ALTER.NET [152.63.33.150]
8 10 ms 6 ms 6 ms 0.xe-4-1-3.XL3.IAD8.ALTER.NET [152.63.3.142]
9 12 ms 7 ms 7 ms TenGigE0-6-0-0.GW1.IAD8.ALTER.NET [152.63.36.45]
10 13 ms 16 ms 15 ms teliasonera-test-gw.customer.alter.net [63.65.76.190]
11 86 ms 83 ms 81 ms sjo-bb1-link.telia.net [80.91.252.220]
12 82 ms 83 ms 97 ms hurricane-113209-sjo-bb1.c.telia.net [213.248.86.54]
13 82 ms 93 ms 91 ms 64.71.140.42
14 122 ms 124 ms 125 ms 208.68.243.254
15 128 ms 135 ms 132 ms boinc2.ssl.berkeley.edu [208.68.240.13]
Then the others were a bit wonky.

13 197 ms 335 ms 319 ms 64.71.140.42
14 124 ms 124 ms 124 ms 208.68.243.254
15 * * * Request timed out.
16 122 ms 121 ms 122 ms setiboincdata.ssl.berkeley.edu [208.68.240.16]

13 95 ms 87 ms 83 ms 64.71.140.42
14 127 ms * 126 ms 208.68.243.254
15 124 ms 124 ms * boinc2.ssl.berkeley.edu [208.68.240.18]
16 126 ms * 127 ms boinc2.ssl.berkeley.edu [208.68.240.18]

13 83 ms 83 ms 84 ms 64.71.140.42
14 * * * Request timed out.
15 123 ms 128 ms * setiboinc.ssl.berkeley.edu [208.68.240.20]
16 125 ms 131 ms 129 ms setiboinc.ssl.berkeley.edu [208.68.240.20]

7. This looks as expected.
Name: boinc2.ssl.berkeley.edu Address: 208.68.240.13
Name: setiboincdata.ssl.berkeley.edu Address: 208.68.240.16
Name: boinc2.ssl.berkeley.edu Address: 208.68.240.18
Name: setiboinc.ssl.berkeley.edu Address: 208.68.240.20
____________
SETI@home classic workunits: 93,865 CPU time: 863,447 hours

Join the BP6/VP6 User Group today!

Shoes&Glasses
Send message
Joined: 12 Feb 00
Posts: 1
Credit: 636,270
RAC: 0
United States
Message 1122156 - Posted: 27 Jun 2011, 20:17:58 UTC

Hi,
I have been crunching for Seti since 2000 and gave up in 2006. I finally reinstalled today and could not download any data. However, I was getting a trickle of info but at .5K download speed. Here are some answers from my neck of the woods:

1: unkown. I am not sure how to test this. (newbie to boink) But my answer is maybe. Some intermitant contact happens, but very very little.

2: 11 am CST

3: Badger internet

4: Southern WI, USA

5: All Pings to the mentioned IP's return a "Request Times Out."

6: Trace RT: all routing dies at my ISP's outbound gateway. (all other web and internet access is up and running fine.)

7: NsLookup:
.13: boinc2.ssl.berkeley.edu
.16: setiboincdata.ssl.berkeley.edu
.18: boinc2.ssl.berkeley.edu
.20: setiboinc.ssl.berkeley.edu

Still I am gettin intermittent blips of data but again at under .5kBps. Runs for a few seconds, then stalls and indicates "Download pending(project backoff: (time)) If I try to restart, it goes for a few seconds and stops. Rinse, repeat.

Hope that may help
____________

rob smith
Volunteer moderator
Send message
Joined: 7 Mar 03
Posts: 7679
Credit: 44,925,952
RAC: 76,254
United Kingdom
Message 1122161 - Posted: 27 Jun 2011, 20:26:29 UTC
Last modified: 27 Jun 2011, 20:32:28 UTC

UK
Virgin Media (was NTL...)
Have had intermittent reports like this:

Mon 27 Jun 2011 20:00:08 BST SETI@home Sending scheduler request: To report completed tasks.
Mon 27 Jun 2011 20:00:08 BST SETI@home Reporting 3 completed tasks, requesting new tasks for CPU
Mon 27 Jun 2011 20:00:11 BST Project communication failed: attempting access to reference site
Mon 27 Jun 2011 20:00:11 BST SETI@home Scheduler request failed: Couldn't connect to server
Mon 27 Jun 2011 20:00:14 BST Internet access OK - project servers may be temporarily down.



Ping all addresses get through with occasional loss of data


Traceroute
208.68.240.13
last three hops:
170ms 168ms 179ms 64.71.140.42
* 218ms 217ms 208.68.243.254
* 246ms 225ms boinc2.ssl.berkeley.edu [208.68.240.13]

208.68.240.16
last three hops:
237ms 257ms 170ms 64.71.140.42
217ms 219ms 216ms 208.68.243.254
* 225ms 217ms boinc2.ssl.berkeley.edu [208.68.240.16]

208.68.240.18
last three hops:
195ms 183ms 171ms 64.71.140.42
229ms 230ms 215ms 208.68.243.254
212ms 227ms 217ms boinc2.ssl.berkeley.edu [208.68.240.18]

208.68.240.20
last three hops:
183ms 168ms 179ms 64.71.140.42
212ms 217ms 228ms 208.68.243.254
* 209ms 225ms boinc2.ssl.berkeley.edu [208.68.240.20]




nslookup, using nameserver cache1.service.virginmedia.net
address: 194.168.4.100


208.68.240.13:
name seti.ssl.berkeley.edu
address 208.68.240.13

208.68.240.16:
name seti.ssl.berkeley.edu
address 208.68.240.16

208.68.240.18:
name seti.ssl.berkeley.edu
address 208.68.240.18

208.68.240.20:
name seti.ssl.berkeley.edu
address 208.68.240.20

which look good and dandy to me.
____________
Bob Smith
Member of Seti PIPPS (Pluto is a Planet Protest Society)
Somewhere in the (un)known Universe?

Profile Skywalker66 @ Berlin
Send message
Joined: 31 Jan 01
Posts: 78
Credit: 27,531,840
RAC: 0
Germany
Message 1122187 - Posted: 27 Jun 2011, 21:38:27 UTC

tracert 208.68.240.13

Routenverfolgung zu boinc2.ssl.berkeley.edu [208.68.240.13] über maximal 30 Abs
chnitte:

1 21 ms 18 ms 17 ms lo1.br08.ber.de.hansenet.net [xxx.xxx.xx.xx]
2 17 ms 17 ms 19 ms ae1-102.cr02.ber.de.hansenet.net [62.109.108.126
]
3 34 ms 38 ms 34 ms so-0-2-0-0.cr01.fra.de.hansenet.net [213.191.87.
189]
4 37 ms 36 ms 43 ms ae1-0.xd01.fra.de.hansenet.net [62.109.69.6]
5 38 ms 37 ms 35 ms ae0-0.pr03.decix.de.hansenet.net [213.191.66.138
]
6 43 ms 36 ms 38 ms 20gigabitethernet4-3.core1.fra1.he.net [80.81.19
2.172]
7 58 ms 55 ms 55 ms 10gigabitethernet1-2.core1.par1.he.net [72.52.92
.89]
8 55 ms 55 ms 56 ms 10gigabitethernet1-1.core1.par2.he.net [184.105.
213.90]
9 129 ms 128 ms 142 ms 10gigabitethernet7-1.core1.ash1.he.net [184.105.
213.93]
10 211 ms 199 ms 203 ms 10gigabitethernet7-4.core1.pao1.he.net [184.105.
213.177]
11 * * * Zeitüberschreitung der Anforderung.
12 * * * Zeitüberschreitung der Anforderung.
13 * * * Zeitüberschreitung der Anforderung.
14 * * * Zeitüberschreitung der Anforderung.
15 * * * Zeitüberschreitung der Anforderung.
16 * * * Zeitüberschreitung der Anforderung.
17 * * * Zeitüberschreitung der Anforderung.


nslookup 208.68.240.13
Server: dnsp03.hansenet.de
Address: 213.191.74.12

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


Location : Germany
ISP : Alice / O2
Start: 15.06.2011
no adress can pinged or tracert
____________

Dr. Wolfram Sperber
Send message
Joined: 4 Jul 99
Posts: 8
Credit: 698,618
RAC: 180
Germany
Message 1122190 - Posted: 27 Jun 2011, 22:04:50 UTC - in response to Message 1122104.

Well, after missing this sudden activities first :-),
I'll contribute this:

1. Till now I'm not reaching any of your servers!
2. As I wrote initially on June 24th, this all began about June 16th...
3. Alice (Hansenet), Germany
4. Berlin, Germany
5. All four servers don't respond at all (s.b.)
6. As shown below, it stops after
10gigabitethernet1-4.core1.pao1.he.net [72.52.92.29]
OR
10gigabitethernet7-4.core1.pao1.he.net [184.105.213.177]
7. nslookup: addresses seem to be resolved correctly

---
Microsoft Windows [Version 6.1.7601]
Copyright (c) 2009 Microsoft Corporation. Alle Rechte vorbehalten.

C:\Users\admin>ping 208.68.240.13

Ping wird ausgeführt für 208.68.240.13 mit 32 Bytes Daten:
Zeitüberschreitung der Anforderung.
Zeitüberschreitung der Anforderung.
Zeitüberschreitung der Anforderung.
Zeitüberschreitung der Anforderung.

Ping-Statistik für 208.68.240.13:
Pakete: Gesendet = 4, Empfangen = 0, Verloren = 4
(100% Verlust),

C:\Users\admin>ping 208.68.240.16

Ping wird ausgeführt für 208.68.240.16 mit 32 Bytes Daten:
Zeitüberschreitung der Anforderung.
Zeitüberschreitung der Anforderung.
Zeitüberschreitung der Anforderung.
Zeitüberschreitung der Anforderung.

Ping-Statistik für 208.68.240.16:
Pakete: Gesendet = 4, Empfangen = 0, Verloren = 4
(100% Verlust),

C:\Users\admin>ping 208.68.240.18

Ping wird ausgeführt für 208.68.240.18 mit 32 Bytes Daten:
Zeitüberschreitung der Anforderung.
Zeitüberschreitung der Anforderung.
Zeitüberschreitung der Anforderung.
Zeitüberschreitung der Anforderung.

Ping-Statistik für 208.68.240.18:
Pakete: Gesendet = 4, Empfangen = 0, Verloren = 4
(100% Verlust),

C:\Users\admin>ping 208.68.240.20

Ping wird ausgeführt für 208.68.240.20 mit 32 Bytes Daten:
Zeitüberschreitung der Anforderung.
Zeitüberschreitung der Anforderung.
Zeitüberschreitung der Anforderung.
Zeitüberschreitung der Anforderung.

Ping-Statistik für 208.68.240.20:
Pakete: Gesendet = 4, Empfangen = 0, Verloren = 4
(100% Verlust),

C:\Users\admin>tracert 208.68.240.13

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

1 <1 ms <1 ms <1 ms fritz.slwlan.box [192.168.xxx.xxx]
2 14 ms 13 ms 23 ms lo1.br08.ber.de.hansenet.net [213.191.89.13]
3 14 ms 14 ms 13 ms ae1-102.cr02.ber.de.hansenet.net [62.109.108.126]
4 33 ms 32 ms 32 ms so-0-2-0-0.cr01.fra.de.hansenet.net [213.191.87.189]
5 33 ms 32 ms 33 ms ae1-0.xd01.fra.de.hansenet.net [62.109.69.6]
6 32 ms 33 ms 32 ms ae0-0.pr03.decix.de.hansenet.net [213.191.66.138]
7 36 ms 33 ms 41 ms 20gigabitethernet4-3.core1.fra1.he.net [80.81.192.172]
8 52 ms 53 ms 50 ms 10gigabitethernet1-2.core1.par1.he.net [72.52.92.89]
9 48 ms 48 ms 48 ms 10gigabitethernet1-1.core1.par2.he.net [184.105.213.90]
10 127 ms 127 ms 126 ms 10gigabitethernet7-1.core1.ash1.he.net [184.105.213.93]
11 204 ms 200 ms 226 ms 10gigabitethernet1-4.core1.pao1.he.net [72.52.92.29]
12 * * * Zeitüberschreitung der Anforderung.
...
30 * * * Zeitüberschreitung der Anforderung.

Ablaufverfolgung beendet.

C:\Users\admin>tracert 208.68.240.16

Routenverfolgung zu setiboincdata.ssl.berkeley.edu [208.68.240.16] über maximal
30 Abschnitte:

1 <1 ms <1 ms <1 ms fritz.slwlan.box [192.168.xxx.xxx]
2 13 ms 14 ms 13 ms lo1.br08.ber.de.hansenet.net [213.191.89.13]
3 15 ms 13 ms 13 ms ae0-101.cr02.ber.de.hansenet.net [62.109.108.62]

4 32 ms 31 ms 31 ms so-0-0-0-0.cr01.fra.de.hansenet.net [213.191.66.25]
5 32 ms 33 ms 32 ms ae1-0.xd01.fra.de.hansenet.net [62.109.69.6]
6 33 ms 32 ms 32 ms ae1-0.pr03.decix.de.hansenet.net [213.191.66.142]
7 38 ms 33 ms 40 ms 20gigabitethernet4-3.core1.fra1.he.net [80.81.192.172]
8 49 ms 50 ms 53 ms 10gigabitethernet1-2.core1.par1.he.net [72.52.92.89]
9 47 ms 50 ms 48 ms 10gigabitethernet1-1.core1.par2.he.net [184.105.213.90]
10 132 ms 125 ms 124 ms 10gigabitethernet7-1.core1.ash1.he.net [184.105.213.93]
11 198 ms 199 ms 198 ms 10gigabitethernet7-4.core1.pao1.he.net [184.105.213.177]
12 * * * Zeitüberschreitung der Anforderung.
...
30 * * * Zeitüberschreitung der Anforderung.

Ablaufverfolgung beendet.

C:\Users\admin>tracert 208.68.240.18

Routenverfolgung zu boinc2.ssl.berkeley.edu [208.68.240.18] über maximal 30 Abschnitte:

1 <1 ms <1 ms <1 ms fritz.slwlan.box [192.168.xxx.xxx]
2 14 ms 24 ms 14 ms lo1.br08.ber.de.hansenet.net [213.191.89.13]
3 14 ms 13 ms 13 ms ae0-101.cr01.ber.de.hansenet.net [62.109.108.61]

4 32 ms 31 ms 31 ms so-0-2-0-0.cr01.fra.de.hansenet.net [213.191.87.173]
5 33 ms 32 ms 32 ms ae0-0.xd01.fra.de.hansenet.net [62.109.69.2]
6 32 ms 32 ms 31 ms ae1-0.pr03.decix.de.hansenet.net [213.191.66.142]
7 36 ms 33 ms 41 ms 20gigabitethernet4-3.core1.fra1.he.net [80.81.192.172]
8 50 ms 50 ms 50 ms 10gigabitethernet1-2.core1.par1.he.net [72.52.92.89]
9 50 ms 49 ms 50 ms 10gigabitethernet1-1.core1.par2.he.net [184.105.213.90]
10 133 ms 124 ms 125 ms 10gigabitethernet7-1.core1.ash1.he.net [184.105.213.93]
11 211 ms 228 ms 203 ms 10gigabitethernet1-4.core1.pao1.he.net [72.52.92.29]
12 * * * Zeitüberschreitung der Anforderung.
...
30 * * * Zeitüberschreitung der Anforderung.

Ablaufverfolgung beendet.

C:\Users\admin>tracert 208.68.240.20

Routenverfolgung zu setiboinc.ssl.berkeley.edu [208.68.240.20] über maximal 30 Abschnitte:

1 <1 ms <1 ms <1 ms fritz.slwlan.box [192.168.xxx.xxx]
2 14 ms 14 ms 14 ms lo1.br08.ber.de.hansenet.net [213.191.89.13]
3 14 ms 13 ms 13 ms ae0-101.cr02.ber.de.hansenet.net [62.109.108.62]

4 49 ms 32 ms 31 ms so-0-1-0-0.cr01.fra.de.hansenet.net [213.191.87.225]
5 32 ms 35 ms 32 ms ae1-0.xd01.fra.de.hansenet.net [62.109.69.6]
6 33 ms 32 ms 32 ms ae0-0.pr03.decix.de.hansenet.net [213.191.66.138]
7 33 ms 33 ms 32 ms 20gigabitethernet4-3.core1.fra1.he.net [80.81.192.172]
8 49 ms 49 ms 49 ms 10gigabitethernet1-2.core1.par1.he.net [72.52.92.89]
9 50 ms 50 ms 51 ms 10gigabitethernet1-1.core1.par2.he.net [184.105.213.90]
10 129 ms * 124 ms 10gigabitethernet7-1.core1.ash1.he.net [184.105.213.93]
11 201 ms 201 ms 202 ms 10gigabitethernet1-4.core1.pao1.he.net [72.52.92.29]
12 * * * Zeitüberschreitung der Anforderung.
...
30 * * * Zeitüberschreitung der Anforderung.

Ablaufverfolgung beendet.

C:\Users\admin>



C:\Users\admin>nslookup 208.68.240.13
...
Name: boinc2.ssl.berkeley.edu
Address: 208.68.240.13
...
Name: setiboincdata.ssl.berkeley.edu
Address: 208.68.240.16
...
Name: boinc2.ssl.berkeley.edu
Address: 208.68.240.18
...
Name: setiboinc.ssl.berkeley.edu
Address: 208.68.240.20

-------------------------------------------
Good luck!
And thanks in advance, Matt

____________
<a href="http://allprojectstats.com/showuser.php?id=622594"><img src="http://allprojectstats.com/su622594n3-2a12-1-0.png" border=0>

Profile Gary Charpentier
Volunteer tester
Avatar
Send message
Joined: 25 Dec 00
Posts: 11732
Credit: 5,969,877
RAC: 0
United States
Message 1122193 - Posted: 27 Jun 2011, 22:16:21 UTC - in response to Message 1122104.
Last modified: 27 Jun 2011, 23:02:31 UTC

1. Are you able to reach ANY of the upload, download, or scheduling servers?
2. When did you start having this problem?
3. What is your ISP?
4. What is your geographic location?
5. What happens when you ping 208.68.240.13? 208.68.240.16? 208.68.240.18? 208.68.240.20?
6. How about traceroutes of the above four addresses?
7. Or nslookups of the above four addresses?

Haven't noticed internet issues from this location. Many project has no work.
Los Angeles, CA, DSL Extreme

Ping 208.68.240.13
Packets sent 4, Received 3, Lost 1 <25% loss>
Min = 112 ms, max 134 ms, av = 123 ms

Ping 208.68.240.16
Packets sent 4, Received 2, Lost 2 <50% loss>
Min = 91ms, max = 108ms, av = 99ms

Ping 206.68.240.18
Packets sent 4, Received 4, Lost 0 <0% loss>
Min = 92ms, Max = 96ms, av = 94ms

Ping 208.68.240.20
Packets sent 4, Received 3, Lost 1 <25% loss>
Min = 92 ms, Max = 93ms, av = 92ms


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 44 ms 45 ms 44 ms netblock-208-127-94-1.dslextreme.com [208.127.94
.1]
3 44 ms 45 ms 45 ms lax1_cr1_gig_10_0_120.dslextreme.com [66.218.48.
145]
4 53 ms 47 ms 50 ms he.net.coresite.com [206.223.143.122]
5 54 ms 53 ms 61 ms 10gigabitethernet7-3.core1.sjc2.he.net [184.105.
213.5]
6 55 ms 55 ms 61 ms 10gigabitethernet3-2.core1.pao1.he.net [72.52.92
.69]
7 53 ms 55 ms 54 ms 64.71.140.42
8 94 ms 96 ms 92 ms 208.68.243.254
9 110 ms 118 ms * boinc2.ssl.berkeley.edu [208.68.240.13]
10 98 ms 109 ms 110 ms boinc2.ssl.berkeley.edu [208.68.240.13]

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 46 ms 45 ms 45 ms netblock-208-127-94-1.dslextreme.com [208.127.94
.1]
3 44 ms 47 ms 44 ms lax1_cr1_gig_10_0_120.dslextreme.com [66.218.48.
145]
4 45 ms 45 ms 46 ms he.net.coresite.com [206.223.143.122]
5 55 ms 53 ms 54 ms 10gigabitethernet7-3.core1.sjc2.he.net [184.105.
213.5]
6 63 ms 54 ms 54 ms 10gigabitethernet3-2.core1.pao1.he.net [72.52.92
.69]
7 54 ms 56 ms 54 ms 64.71.140.42
8 * 95 ms * 208.68.243.254
9 95 ms 96 ms 94 ms setiboincdata.ssl.berkeley.edu [208.68.240.16]

Trace complete.


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 43 ms 44 ms 44 ms netblock-208-127-94-1.dslextreme.com [208.127.94
.1]
3 45 ms 46 ms 45 ms lax1_cr1_gig_10_0_120.dslextreme.com [66.218.48.
145]
4 46 ms 46 ms 46 ms he.net.coresite.com [206.223.143.122]
5 61 ms 53 ms 54 ms 10gigabitethernet7-3.core1.sjc2.he.net [184.105.
213.5]
6 63 ms 54 ms 54 ms 10gigabitethernet3-2.core1.pao1.he.net [72.52.92
.69]
7 55 ms 55 ms 55 ms 64.71.140.42
8 96 ms * 95 ms 208.68.243.254
9 94 ms 95 ms 97 ms boinc2.ssl.berkeley.edu [208.68.240.18]

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 56 ms 52 ms 47 ms netblock-208-127-94-1.dslextreme.com [208.127.94
.1]
3 69 ms 68 ms 66 ms lax1_cr1_gig_10_0_120.dslextreme.com [66.218.48.
145]
4 46 ms 46 ms 45 ms he.net.coresite.com [206.223.143.122]
5 113 ms 54 ms 60 ms 10gigabitethernet7-3.core1.sjc2.he.net [184.105.
213.5]
6 62 ms 57 ms 56 ms 10gigabitethernet3-2.core1.pao1.he.net [72.52.92
.69]
7 84 ms 86 ms 89 ms 64.71.140.42
8 113 ms 99 ms 95 ms 208.68.243.254
9 96 ms * 97 ms setiboinc.ssl.berkeley.edu [208.68.240.20]

Trace complete.


nslookup 208.68.240.13
Server: dns1.dslextreme.com
Address: 66.51.205.100

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


nslookup 208.68.240.16
Server: dns1.dslextreme.com
Address: 66.51.205.100

DNS request timed out.
timeout was 2 seconds.
*** Request to dns1.dslextreme.com timed-out

nslookup 208.68.240.18
Server: dns1.dslextreme.com
Address: 66.51.205.100

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


nslookup 208.68.240.20
Server: dns1.dslextreme.com
Address: 66.51.205.100

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

Thanks for the copy/paste info, found it about the same time.
____________

Profile perryjay
Volunteer tester
Avatar
Send message
Joined: 20 Aug 02
Posts: 3377
Credit: 13,709,926
RAC: 12,419
United States
Message 1122197 - Posted: 27 Jun 2011, 22:35:31 UTC - in response to Message 1122193.
Last modified: 27 Jun 2011, 22:40:35 UTC

In the top left corner is a little icon that looks sort of like a camera. Click that, then go down to edit and select all, click the camera thing again, go to edit and copy should be clickable. Select it and then paste to where ever you want it.

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

C:\Users\perry>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 7 ms 7 ms 7 ms 10.109.80.1
3 15 ms 14 ms 7 ms ten0-3-0.orld43-ser1.bhn.net [72.31.194.88]
4 11 ms 8 ms 9 ms ten0-6-0-4-orld11-car1.bhn.net [71.44.60.54]
5 20 ms 15 ms 15 ms ten0-1-0-0.orld71-car1.bhn.net [97.69.193.136]
6 19 ms 23 ms 19 ms ae1.orld71-cbr1.bhn.net [72.31.194.8]
7 18 ms 20 ms 18 ms ae0-0.orld71-cbr2.bhn.net [24.95.228.77]
8 23 ms 29 ms 26 ms ae-4-11.cr1.atl20.tbone.rr.com [66.109.10.14]
9 27 ms 33 ms 31 ms ae-1-0.pr0.atl20.tbone.rr.com [66.109.6.177]
10 23 ms 22 ms 23 ms 64.209.106.17
11 84 ms 85 ms 94 ms Hurrican-Electric-LLC.Port-channel100.ar3.SJC2.g
blx.net [64.214.174.246]
12 123 ms 93 ms 87 ms 10gigabitethernet3-2.core1.pao1.he.net [72.52.92
.69]
13 84 ms 82 ms 86 ms 64.71.140.42
14 122 ms 124 ms 123 ms 208.68.243.254
15 129 ms 127 ms 139 ms boinc2.ssl.berkeley.edu [208.68.240.13]

Trace complete.

C:\Users\perry>



EDIT: Well, anyway, someone asked so that's how I do it. If anyone has an easier way to copy from the command window let us know.
____________


PROUD MEMBER OF Team Starfire World BOINC

Brkovip
Avatar
Send message
Joined: 18 May 99
Posts: 274
Credit: 142,877,307
RAC: 4,061
United States
Message 1122200 - Posted: 27 Jun 2011, 22:44:15 UTC

1. Are you able to reach ANY of the upload, download, or scheduling servers? Yes at times, just a lot of retries.
2. When did you start having this problem? Almost 6 months ago
3. What is your ISP? Vector internet services
4. What is your geographic location? Minnesota
5. What happens when you ping 208.68.240.13? 208.68.240.16? 208.68.240.18? 208.68.240.20?
6. How about traceroutes of the above four addresses?

--- 208.68.240.13 ping statistics ---
20 packets transmitted, 12 received, 40% packet loss, time 19014ms
rtt min/avg/max/mdev = 148.072/191.071/462.702/82.891 ms

--- 208.68.240.16 ping statistics ---
15 packets transmitted, 11 received, 26% packet loss, time 14011ms
rtt min/avg/max/mdev = 140.134/142.701/144.084/1.013 ms

--- 208.68.240.18 ping statistics ---
15 packets transmitted, 9 received, 40% packet loss, time 14002ms
rtt min/avg/max/mdev = 141.810/143.058/144.063/0.845 ms

--- 208.68.240.20 ping statistics ---
15 packets transmitted, 11 received, 26% packet loss, time 14013ms
rtt min/avg/max/mdev = 142.652/143.134/144.086/0.542 ms


traceroute to 208.68.240.13 (208.68.240.13), 30 hops max, 60 byte packets
2 edge-6.stpaul.visi.com (208.42.0.20) 47.985 ms 49.077 ms 50.600 ms
3 edge-3.mn2.visi.com (208.42.31.82) 51.381 ms 52.281 ms 53.758 ms
4 64.214.150.217 (64.214.150.217) 55.254 ms 56.230 ms 57.193 ms
5 te4-3-10G.ar3.SJC2.gblx.net (67.17.105.34) 106.290 ms 106.714 ms 107.958 ms
6 Hurrican-Electric-LLC.Port-channel100.ar3.SJC2.gblx.net (64.214.174.246) 122.029 ms 107.994 ms 107.985 ms
7 10gigabitethernet3-2.core1.pao1.he.net (72.52.92.69) 104.771 ms 101.119 ms 112.086 ms
8 64.71.140.42 (64.71.140.42) 116.055 ms 116.233 ms 116.708 ms
9 208.68.243.254 (208.68.243.254) 148.824 ms * 150.700 ms
10 * * *
11 * * *

traceroute to 208.68.240.16 (208.68.240.16), 30 hops max, 60 byte packets
2 edge-6.stpaul.visi.com (208.42.0.20) 47.652 ms 49.084 ms 50.546 ms
3 core-2.mn2.visi.com (208.42.31.66) 51.830 ms 52.704 ms 53.508 ms
4 gi5-1.edge-3.mn2.visi.com (208.42.1.18) 54.253 ms 55.437 ms 56.406 ms
5 64.214.150.217 (64.214.150.217) 57.965 ms 59.118 ms 59.832 ms
6 te4-3-10G.ar3.SJC2.gblx.net (67.17.105.34) 132.118 ms 95.662 ms 96.865 ms
7 Hurrican-Electric-LLC.Port-channel100.ar3.SJC2.gblx.net (64.214.174.246) 107.295 ms 102.408 ms 102.155 ms
8 10gigabitethernet3-2.core1.pao1.he.net (72.52.92.69) 104.953 ms 104.779 ms 102.533 ms
9 64.71.140.42 (64.71.140.42) 104.277 ms 105.614 ms 106.653 ms
10 * 208.68.243.254 (208.68.243.254) 149.857 ms *
11 * * *
12 * * *

traceroute to 208.68.240.18 (208.68.240.18), 30 hops max, 60 byte packets
2 edge-6.stpaul.visi.com (208.42.0.20) 48.256 ms 49.170 ms 50.379 ms
3 core-2.mn2.visi.com (208.42.31.66) 51.411 ms 52.323 ms 53.066 ms
4 gi5-1.edge-3.mn2.visi.com (208.42.1.18) 55.579 ms 56.092 ms 56.480 ms
5 64.214.150.217 (64.214.150.217) 57.839 ms 58.952 ms 59.428 ms
6 te4-3-10G.ar3.SJC2.gblx.net (67.17.105.34) 117.906 ms 108.876 ms 108.869 ms
7 Hurrican-Electric-LLC.Port-channel100.ar3.SJC2.gblx.net (64.214.174.246) 104.697 ms 110.892 ms 110.693 ms
8 10gigabitethernet3-2.core1.pao1.he.net (72.52.92.69) 108.404 ms 106.825 ms 106.730 ms
9 64.71.140.42 (64.71.140.42) 103.979 ms 101.719 ms 104.321 ms
10 208.68.243.254 (208.68.243.254) 145.377 ms 143.670 ms 145.327 ms
11 * * *
12 * * *

traceroute to 208.68.240.20 (208.68.240.20), 30 hops max, 60 byte packets
2 edge-6.stpaul.visi.com (208.42.0.20) 48.437 ms 49.322 ms 50.295 ms
3 core-2.mn2.visi.com (208.42.31.66) 51.588 ms 52.905 ms 53.990 ms
4 gi5-1.edge-3.mn2.visi.com (208.42.1.18) 55.340 ms 56.627 ms 57.098 ms
5 64.214.150.217 (64.214.150.217) 58.474 ms 59.359 ms 60.115 ms
6 te4-3-10G.ar3.SJC2.gblx.net (67.17.105.34) 108.718 ms 95.884 ms 97.073 ms
7 Hurrican-Electric-LLC.Port-channel100.ar3.SJC2.gblx.net (64.214.174.246) 115.133 ms 104.354 ms 104.516 ms
8 10gigabitethernet3-2.core1.pao1.he.net (72.52.92.69) 103.938 ms 108.798 ms 103.211 ms
9 64.71.140.42 (64.71.140.42) 102.740 ms 102.501 ms 103.000 ms
10 208.68.243.254 (208.68.243.254) 144.480 ms 143.400 ms 143.584 ms
11 * * *
12 * * *
____________

Profile Gary Charpentier
Volunteer tester
Avatar
Send message
Joined: 25 Dec 00
Posts: 11732
Credit: 5,969,877
RAC: 0
United States
Message 1122247 - Posted: 28 Jun 2011, 0:32:00 UTC - in response to Message 1122104.

1. Are you able to reach ANY of the upload, download, or scheduling servers?
2. When did you start having this problem?
3. What is your ISP?
4. What is your geographic location?
5. What happens when you ping 208.68.240.13? 208.68.240.16? 208.68.240.18? 208.68.240.20?
6. How about traceroutes of the above four addresses?
7. Or nslookups of the above four addresses?


No internet issues from this location.
Verizon, Pasadena, CA

$ ping 208.68.240.13
PING 208.68.240.13 (208.68.240.13): 56 data bytes
64 bytes from 208.68.240.13: icmp_seq=0 ttl=54 time=118.324 ms
64 bytes from 208.68.240.13: icmp_seq=1 ttl=54 time=123.815 ms
64 bytes from 208.68.240.13: icmp_seq=4 ttl=54 time=182.993 ms
64 bytes from 208.68.240.13: icmp_seq=6 ttl=54 time=437.999 ms
64 bytes from 208.68.240.13: icmp_seq=7 ttl=54 time=119.903 ms
^C
--- 208.68.240.13 ping statistics ---
8 packets transmitted, 5 packets received, 37% packet loss
round-trip min/avg/max/stddev = 118.324/196.607/437.999/123.098 ms

$ ping 208.68.240.16
PING 208.68.240.16 (208.68.240.16): 56 data bytes
64 bytes from 208.68.240.16: icmp_seq=0 ttl=54 time=74.446 ms
64 bytes from 208.68.240.16: icmp_seq=1 ttl=54 time=75.512 ms
64 bytes from 208.68.240.16: icmp_seq=2 ttl=54 time=74.719 ms
64 bytes from 208.68.240.16: icmp_seq=3 ttl=54 time=76.152 ms
64 bytes from 208.68.240.16: icmp_seq=4 ttl=54 time=75.117 ms
^C
--- 208.68.240.16 ping statistics ---
5 packets transmitted, 5 packets received, 0% packet loss
round-trip min/avg/max/stddev = 74.446/75.189/76.152/0.602 ms

$ ping 208.68.240.18
PING 208.68.240.18 (208.68.240.18): 56 data bytes
64 bytes from 208.68.240.18: icmp_seq=1 ttl=54 time=78.565 ms
64 bytes from 208.68.240.18: icmp_seq=3 ttl=54 time=79.092 ms
64 bytes from 208.68.240.18: icmp_seq=4 ttl=54 time=74.856 ms
64 bytes from 208.68.240.18: icmp_seq=5 ttl=54 time=77.979 ms
^C
--- 208.68.240.18 ping statistics ---
7 packets transmitted, 4 packets received, 42% packet loss
round-trip min/avg/max/stddev = 74.856/77.623/79.092/1.645 ms

$ ping 208.68.240.20
PING 208.68.240.20 (208.68.240.20): 56 data bytes
64 bytes from 208.68.240.20: icmp_seq=0 ttl=54 time=77.181 ms
64 bytes from 208.68.240.20: icmp_seq=1 ttl=54 time=75.791 ms
64 bytes from 208.68.240.20: icmp_seq=2 ttl=54 time=77.631 ms
64 bytes from 208.68.240.20: icmp_seq=4 ttl=54 time=77.236 ms
64 bytes from 208.68.240.20: icmp_seq=6 ttl=54 time=77.638 ms
^C
--- 208.68.240.20 ping statistics ---
7 packets transmitted, 5 packets received, 28% packet loss
round-trip min/avg/max/stddev = 75.791/77.095/77.638/0.680 ms

$ nslookup 208.68.240.13
Server: 192.168.1.1
Address: 192.168.1.1#53

Non-authoritative answer:
13.240.68.208.in-addr.arpa name = boinc2.ssl.berkeley.edu.

Authoritative answers can be found from:


$ nslookup 208.68.240.16
Server: 192.168.1.1
Address: 192.168.1.1#53

Non-authoritative answer:
16.240.68.208.in-addr.arpa name = setiboincdata.ssl.berkeley.edu.

Authoritative answers can be found from:


$ nslookup 208.68.240.18
Server: 192.168.1.1
Address: 192.168.1.1#53

Non-authoritative answer:
18.240.68.208.in-addr.arpa name = boinc2.ssl.berkeley.edu.

Authoritative answers can be found from:


$ nslookup 208.68.240.20
Server: 192.168.1.1
Address: 192.168.1.1#53

Non-authoritative answer:
20.240.68.208.in-addr.arpa name = setiboinc.ssl.berkeley.edu.

Authoritative answers can be found from:


$ traceroute 208.68.240.13
traceroute to 208.68.240.13 (208.68.240.13), 64 hops max, 40 byte packets
1 * * *
2 L100.LSANCA-DSL-20.verizon-gni.net (71.108.177.1) 22.606 ms 23.360 ms 23.166 ms
3 P11-0.LSANCA-LCR-02.verizon-gni.net (130.81.44.160) 22.854 ms 23.396 ms 22.998 ms
4 so-7-1-3-0.LAX01-BB-RTR2.verizon-gni.net (130.81.28.221) 24.000 ms 67.541 ms 74.961 ms
5 0.so-6-0-0.XT2.LAX9.ALTER.NET (152.63.10.157) 26.189 ms 25.780 ms 26.011 ms
6 0.so-7-1-0.XL4.LAX15.ALTER.NET (152.63.1.242) 25.660 ms 25.685 ms 25.993 ms
7 TenGigE0-5-4-0.GW4.LAX15.ALTER.NET (152.63.115.246) 26.427 ms 26.247 ms 26.196 ms
8 teliasonera-gw.customer.alter.net (152.179.21.42) 25.659 ms 25.795 ms 26.108 ms
9 sjo-bb1-link.telia.net (80.91.247.171) 39.286 ms 38.989 ms 39.804 ms
10 hurricane-113209-sjo-bb1.c.telia.net (213.248.86.54) 41.343 ms 40.422 ms 49.694 ms
11 64.71.140.42 (64.71.140.42) 38.946 ms 44.254 ms 38.948 ms
12 208.68.243.254 (208.68.243.254) 78.172 ms 78.620 ms *
13 * * *
14 * * *
15 * * *
16 * * *
^C

$ traceroute 208.68.240.16
traceroute to 208.68.240.16 (208.68.240.16), 64 hops max, 40 byte packets
1 * * *
2 L100.LSANCA-DSL-20.verizon-gni.net (71.108.177.1) 23.663 ms 32.417 ms 22.635 ms
3 P11-0.LSANCA-LCR-01.verizon-gni.net (130.81.44.162) 22.963 ms 23.450 ms 23.393 ms
4 so-7-3-0-0.LAX01-BB-RTR1.verizon-gni.net (130.81.28.217) 23.991 ms 23.815 ms 23.754 ms
5 0.so-6-3-0.XT1.LAX9.ALTER.NET (152.63.10.153) 25.188 ms 25.514 ms 25.256 ms
6 0.so-7-0-0.XL3.LAX15.ALTER.NET (152.63.112.53) 24.897 ms 25.478 ms 25.477 ms
7 TenGigE0-6-2-0.GW4.LAX15.ALTER.NET (152.63.114.213) 25.453 ms TenGigE0-6-1-0.GW4.LAX15.ALTER.NET (152.63.114.209) 25.729 ms 25.820 ms
8 teliasonera-gw.customer.alter.net (152.179.21.42) 35.835 ms 25.233 ms 25.497 ms
9 sjo-bb1-link.telia.net (80.91.247.171) 38.716 ms 38.470 ms 38.431 ms
10 hurricane-113209-sjo-bb1.c.telia.net (213.248.86.54) 39.260 ms 47.095 ms 39.159 ms
11 64.71.140.42 (64.71.140.42) 37.739 ms 38.631 ms 38.453 ms
12 208.68.243.254 (208.68.243.254) 79.767 ms 79.513 ms 79.805 ms
13 * * *
14 * * *
^C

$ traceroute 208.68.240.18
traceroute to 208.68.240.18 (208.68.240.18), 64 hops max, 40 byte packets
1 * * *
2 L100.LSANCA-DSL-20.verizon-gni.net (71.108.177.1) 23.667 ms 22.880 ms 23.378 ms
3 P2-0.LSANCA-LCR-01.verizon-gni.net (130.81.35.32) 23.093 ms 23.224 ms 23.473 ms
4 so-7-3-0-0.LAX01-BB-RTR1.verizon-gni.net (130.81.28.217) 147.314 ms 75.077 ms 55.378 ms
5 0.so-6-3-0.XT1.LAX9.ALTER.NET (152.63.10.153) 25.429 ms 29.432 ms 25.437 ms
6 0.so-7-0-0.XL3.LAX15.ALTER.NET (152.63.112.53) 25.227 ms 24.933 ms 25.430 ms
7 TenGigE0-6-1-0.GW4.LAX15.ALTER.NET (152.63.114.209) 28.392 ms TenGigE0-6-2-0.GW4.LAX15.ALTER.NET (152.63.114.213) 25.442 ms 25.830 ms
8 teliasonera-gw.customer.alter.net (152.179.21.42) 25.306 ms 28.514 ms 25.441 ms
9 sjo-bb1-link.telia.net (80.91.247.171) 38.627 ms 38.749 ms 38.395 ms
10 hurricane-113209-sjo-bb1.c.telia.net (213.248.86.54) 38.704 ms 47.946 ms 49.397 ms
11 64.71.140.42 (64.71.140.42) 41.562 ms 38.667 ms 38.159 ms
12 * * 208.68.243.254 (208.68.243.254) 80.241 ms
13 * * *
14 * * *
^C

$ traceroute 208.68.240.20
traceroute to 208.68.240.20 (208.68.240.20), 64 hops max, 40 byte packets
1 * * *
2 L100.LSANCA-DSL-20.verizon-gni.net (71.108.177.1) 23.215 ms 23.377 ms 22.603 ms
3 P11-0.LSANCA-LCR-01.verizon-gni.net (130.81.44.162) 22.869 ms 25.436 ms 23.379 ms
4 so-7-3-0-0.LAX01-BB-RTR1.verizon-gni.net (130.81.28.217) 23.818 ms 23.322 ms 23.975 ms
5 0.so-6-2-0.XT1.LAX7.ALTER.NET (152.63.112.45) 29.836 ms 23.992 ms 24.036 ms
6 0.ge-2-0-0.XL3.LAX15.ALTER.NET (152.63.2.66) 24.465 ms 67.114 ms 24.264 ms
7 TenGigE0-6-0-0.GW4.LAX15.ALTER.NET (152.63.114.205) 27.586 ms TenGigE0-4-4-0.GW4.LAX15.ALTER.NET (152.63.115.242) 25.072 ms 24.912 ms
8 teliasonera-gw.customer.alter.net (152.179.21.42) 26.763 ms 24.888 ms 28.408 ms
9 sjo-bb1-link.telia.net (213.248.80.16) 35.635 ms 36.002 ms 36.283 ms
10 hurricane-113209-sjo-bb1.c.telia.net (213.248.86.54) 39.151 ms 46.509 ms 37.801 ms
11 64.71.140.42 (64.71.140.42) 37.981 ms 36.127 ms 35.860 ms
12 * 208.68.243.254 (208.68.243.254) 79.149 ms *
13 * * *
14 * * *
^C


I note that for all the traces above, up through and including the 10th hop the printout was fast on the screen, the 11 hop and beyond took a lot of time to print so that is where there is congestion.


____________

tbret
Volunteer tester
Avatar
Send message
Joined: 28 May 99
Posts: 2390
Credit: 164,323,323
RAC: 68,615
United States
Message 1122285 - Posted: 28 Jun 2011, 2:58:23 UTC
Last modified: 28 Jun 2011, 3:00:28 UTC

1 - Are you able to reach ANY of the upload, download, or scheduling servers?
I seem to be able to today.

2 - When did you start having this problem?
First sign of any problem was June 1 or 2.

3 - What is your ISP?
Comcast & Bellsouth (two locations)

4 - What is your geographic location?
Central MS

5 - What happens when you ping 208.68.240.13? 208.68.240.16? 208.68.240.18? 208.68.240.20?
Success tonight with no more than 25% packet loss. Earlier today, up to 75% packet losses via Comcast.

6- How about traceroutes of the above four addresses?

__________________________________________________________

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

1 1 ms 2 ms 1 ms WRT610N
2 9 ms 8 ms 9 ms 75.66.74.1
3 13 ms 14 ms 13 ms ge-1-6-ur01.rankin.ms.malt.comcast.net [68.85.55.65]
4 6 ms 7 ms 7 ms te-9-3-ur03.jacksonnorth.ms.malt.comcast.net [68.86.241.37]
5 12 ms 30 ms 12 ms te-7-1-ar01.dannythomas.tn.malt.comcast.net [68.86.240.133]
6 23 ms 22 ms 23 ms te-1-1-0-1-cr01.dallas.tx.ibone.comcast.net [68.86.94.201]
7 24 ms 25 ms 23 ms tengigabitethernet6-2.ar3.dal2.gblx.net [67.17.157.221]
8 68 ms 68 ms 68 ms hurrican-electric-llc.port-channel100.ar3.sjc2.gblx.net [64.214.174.246]
9 94 ms 71 ms 69 ms 10gigabitethernet3-2.core1.pao1.he.net [72.52.92.69]
10 69 ms 68 ms 69 ms 64.71.140.42
11 111 ms * 111 ms 208.68.243.254
12 * * * Request timed out.
13 110 ms * 109 ms boinc2.ssl.berkeley.edu [208.68.240.18]

Trace complete.

_________________________________________________________________________

Time between #8 and #9 may be anywhere from 10 to 20 seconds reporting. Subsequent hops report either instantly or take 10 to 15 seconds to respond.

xxx.18 and xxx.20 seem to be the slowest.


7 - Or nslookups of the above four addresses?

Almost instant success on all.

Thanks for looking into this Matt. In my case individual computers on the same router (no matter which router for two different routers in different locations) seem to have trouble which resolves itself over a period of multiple days. A single computer might not connect for three or four days and then for no reason at all will connect. Meanwhile, others on the same router will have no trouble connecting multiple times per day. But which computer is "stuck" changes without rhyme or reason.

Also, you might note that in one other person's case he switched internet connections (from a land-based to wireless) and still could not get through.

It is as though something is denying access to specific computers, although I can't imagine why that would be true.

I hoped to be of more help, but my latest "stuck" computer (two days) magically fixed itself before I could get to run the tests this evening.

I'm afraid that's not much help.

Profile David Anderson (not *that* DA)
Avatar
Send message
Joined: 5 Dec 09
Posts: 103
Credit: 20,818,373
RAC: 19,849
United States
Message 1122296 - Posted: 28 Jun 2011, 3:49:45 UTC

This is from just across San Francisco Bay (SF Peninsula).
Data point. Not a complaint.

I've been getting work from Seti, but not as much as I'd want.
Many reports in Messages (in boinc Manager) about network must be down.
Or temporarily failed download or there is no work (over the last few
weeks, not so much the last few days).

On the other hand, there is often some work. And right now I'm
actually running 7 cores as Seti (and 7 Einstein) though
I've configured BOINC for a higher Seti percentage than I ever get.

q2 697: traceroute boinc2.ssl.berkeley.edu
\traceroute to boinc2.ssl.berkeley.edu (208.68.240.13), 30 hops max, 60 byte packets

1 192.168.1.1 (192.168.1.1) 2.880 ms 3.843 ms 4.106 ms
2 24.23.156.1 (24.23.156.1) 19.706 ms 24.618 ms 45.871 ms
3 te-5-1-ur01.sanmateo.ca.sfba.comcast.net (68.86.248.209) 24.931 ms 25.056 ms 25.169 ms
4 te-1-3-0-1-ar01.sfsutro.ca.sfba.comcast.net (68.87.226.246) 25.857 ms 26.101 ms 26.216 ms
5 pos-1-5-0-0-cr01.sanjose.ca.ibone.comcast.net (68.86.90.93) 27.506 ms 27.749 ms 27.864 ms
6 pos-0-1-0-0-pe01.11greatoaks.ca.ibone.comcast.net (68.86.86.50) 34.587 ms 44.542 ms 17.719 ms
7 208.178.58.5 (208.178.58.5) 27.147 ms 28.490 ms 28.685 ms
8 po4-20G.ar2.SJC2.gblx.net (67.16.142.214) 29.208 ms te6-2-10G.ar4.SJC2.gblx.net (67.16.142.201) 29.550 ms po4-20G.ar4.SJC2.gblx.net (67.16.142.209) 29.783 ms
9 po6-20G.ar3.SJC2.gblx.net (67.17.70.253) 66.623 ms 67.074 ms po1-20G.ar3.SJC2.gblx.net (67.16.134.26) 66.919 ms
10 Hurrican-Electric-LLC.Port-channel100.ar3.SJC2.gblx.net (64.214.174.246) 30.736 ms 30.985 ms 31.088 ms
11 10gigabitethernet3-2.core1.pao1.he.net (72.52.92.69) 30.254 ms 29.841 ms 30.080 ms
12 64.71.140.42 (64.71.140.42) 17.272 ms 61.937 ms 17.263 ms
13 * 208.68.243.254 (208.68.243.254) 67.390 ms 68.173 ms
14 * * *
15 * * *

Profile David Anderson (not *that* DA)
Avatar
Send message
Joined: 5 Dec 09
Posts: 103
Credit: 20,818,373
RAC: 19,849
United States
Message 1122299 - Posted: 28 Jun 2011, 3:55:45 UTC

ISP is Comcast, (see previous post for traceroute).
Burlingame, CA, across Bay from Berkeley.

+ ping -c 3 208.68.240.13
PING 208.68.240.13 (208.68.240.13) 56(84) bytes of data.
64 bytes from 208.68.240.13: icmp_req=1 ttl=51 time=97.0 ms
64 bytes from 208.68.240.13: icmp_req=3 ttl=51 time=84.5 ms

--- 208.68.240.13 ping statistics ---
3 packets transmitted, 2 received, 33% packet loss, time 2007ms
rtt min/avg/max/mdev = 84.574/90.831/97.089/6.264 ms
+ ping -c 3 208.68.240.16
PING 208.68.240.16 (208.68.240.16) 56(84) bytes of data.
64 bytes from 208.68.240.16: icmp_req=1 ttl=51 time=71.2 ms
64 bytes from 208.68.240.16: icmp_req=3 ttl=51 time=57.2 ms

--- 208.68.240.16 ping statistics ---
3 packets transmitted, 2 received, 33% packet loss, time 2001ms
rtt min/avg/max/mdev = 57.267/64.247/71.228/6.985 ms
+ ping -c 3 208.68.240.18
PING 208.68.240.18 (208.68.240.18) 56(84) bytes of data.
64 bytes from 208.68.240.18: icmp_req=1 ttl=51 time=60.4 ms
64 bytes from 208.68.240.18: icmp_req=2 ttl=51 time=92.2 ms
64 bytes from 208.68.240.18: icmp_req=3 ttl=51 time=82.0 ms

--- 208.68.240.18 ping statistics ---
3 packets transmitted, 3 received, 0% packet loss, time 2002ms
rtt min/avg/max/mdev = 60.413/78.223/92.219/13.261 ms
+ ping -c 3 208.68.240.20
PING 208.68.240.20 (208.68.240.20) 56(84) bytes of data.
64 bytes from 208.68.240.20: icmp_req=1 ttl=51 time=79.9 ms
64 bytes from 208.68.240.20: icmp_req=2 ttl=51 time=98.1 ms

--- 208.68.240.20 ping statistics ---
3 packets transmitted, 2 received, 33% packet loss, time 2002ms
rtt min/avg/max/mdev = 79.913/89.017/98.122/9.109 ms

1 · 2 · 3 · 4 . . . 25 · Next

Message boards : Number crunching : HE connection problems thread

Copyright © 2014 University of California