Message boards :
Number crunching :
HE connection problems thread
Message board moderation
Previous · 1 . . . 5 · 6 · 7 · 8 · 9 · 10 · 11 . . . 25 · Next
Author | Message |
---|---|
Shane Meyer Send message Joined: 22 Jan 00 Posts: 126 Credit: 31,280,265 RAC: 42 |
Same Here cannot connect since Tuesday Outage appears not to be able to find HE.net in Cal. USA Last hit Hong Kong Tracing route to boinc2.ssl.berkeley.edu [208.68.240.13] over a maximum of 30 hops: 1 <1 ms <1 ms <1 ms edimax.com [192.168.2.1] 2 19 ms 19 ms 17 ms nexthop.sa.iinet.net.au [203.215.11.249] 3 18 ms 19 ms 17 ms po2.ade-pipe-bdr1.iinet.net.au [203.215.10.22] 4 41 ms 42 ms 41 ms ge-3-0-1-0.syd-mas-core1.iinet.net.au [203.215.2 0.70] 5 232 ms 234 ms 233 ms 34023.sydp06.cu.reach.com [134.159.160.57] 6 190 ms 190 ms 190 ms i-0-0-2-0.paix-core01.bx.reach.com [202.84.140.1 06] 7 189 ms 191 ms 192 ms i-1-1.paix01.bi.reach.com [202.84.251.70] 8 * * * Request timed out. 9 * * |
Richard Haselgrove Send message Joined: 4 Jul 99 Posts: 14649 Credit: 200,643,578 RAC: 874 |
Another failure has been reported to me by PM, regarding a German ISP: Tracing route to boinc2.ssl.berkeley.edu [208.68.240.18] No problems from my own ISP (British Telecom in the UK) |
Gundolf Jahn Send message Joined: 19 Sep 00 Posts: 3184 Credit: 446,358 RAC: 0 |
No problems via German Telekom: Routenverfolgung zu boinc2.ssl.berkeley.edu [208.68.240.13] über maximal 30 Abs chnitte: 1 86 ms 99 ms 99 ms speedtouch.lan [192.168.1.254] 2 46 ms 43 ms 43 ms 217.0.116.142 3 45 ms 46 ms 45 ms 217.0.73.202 4 65 ms 66 ms 66 ms 217.239.40.14 5 65 ms 64 ms 65 ms prs-b7-link.telia.net [213.248.96.209] 6 65 ms 66 ms 65 ms prs-bb1-link.telia.net [80.91.252.141] 7 144 ms 144 ms 145 ms ash-bb1-link.telia.net [80.91.251.98] 8 218 ms 218 ms 219 ms sjo-bb1-link.telia.net [213.155.130.213] 9 219 ms 218 ms 219 ms hurricane-113209-sjo-bb1.c.telia.net [213.248.86 .54] 10 219 ms 219 ms 219 ms 64.71.140.42 11 258 ms 260 ms 258 ms 208.68.243.254 12 284 ms 275 ms 271 ms boinc2.ssl.berkeley.edu [208.68.240.13] Ablaufverfolgung beendet. Routenverfolgung zu boinc2.ssl.berkeley.edu [208.68.240.18] über maximal 30 Abs chnitte: 1 32 ms 99 ms 100 ms speedtouch.lan [192.168.1.254] 2 43 ms 43 ms 43 ms 217.0.116.142 3 44 ms 44 ms 44 ms 217.0.73.194 4 66 ms 65 ms 65 ms 217.239.40.14 5 64 ms 136 ms 64 ms prs-b7-link.telia.net [213.248.96.209] 6 65 ms 64 ms 65 ms prs-bb1-link.telia.net [80.91.250.53] 7 143 ms 143 ms 152 ms ash-bb1-link.telia.net [80.91.252.36] 8 218 ms 218 ms 218 ms sjo-bb1-link.telia.net [80.91.252.220] 9 218 ms 232 ms 218 ms hurricane-113209-sjo-bb1.c.telia.net [213.248.86 .54] 10 219 ms 218 ms 219 ms 64.71.140.42 11 260 ms * 259 ms 208.68.243.254 12 260 ms 260 ms 260 ms boinc2.ssl.berkeley.edu [208.68.240.18] Ablaufverfolgung beendet. Gruß, Gundolf |
Bernd Noessler Send message Joined: 15 Nov 09 Posts: 99 Credit: 52,635,434 RAC: 0 |
This is my traceroute from Germany traceroute to 208.68.240.13 (208.68.240.13), 30 hops max, 60 byte packets 1 a6000.noessler.lan (192.168.101.65) 0.080 ms 2 access.de.kamp.net (195.62.99.234) 46.072 ms 3 bbr-ob-01.de.kamp.net (195.62.99.249) 46.079 ms 4 bbr-ob-02.de.kamp.net (212.110.97.18) 50.235 ms 5 bbr-f-01.de.kamp.net (195.62.101.2) 56.048 ms 6 20gigabitethernet4-3.core1.fra1.he.net (80.81.192.172) 68.065 ms 7 10gigabitethernet1-4.core1.par2.he.net (184.105.213.162) 72.050 ms 8 10gigabitethernet1-1.core1.par2.he.net (184.105.213.90) 74.138 ms 9 10gigabitethernet7-4.core1.pao1.he.net (184.105.213.177) 225.029 ms 10 10gigabitethernet7-4.core1.pao1.he.net (184.105.213.177) 227.031 ms 11 * 12 * 13 * 14 * 15 * 16 * 17 * 18 * 19 * No connection since the tuesday outage. Interesting : 184.105.213.177 is on hop 9 and 10 !! He forwards the packets to himself one time and then discards it. |
Bill Walker Send message Joined: 4 Sep 99 Posts: 3868 Credit: 2,697,267 RAC: 0 |
Here is a trace route from Canada. no uploads or downloads to this machine for 2 days now. If I understand this correctly, I'm reaching he.net (Hurricane Electric?) but not beyond? Tracing route to boinc2.ssl.berkeley.edu [208.68.240.13] over a maximum of 30 hops: 1 4 ms 8 ms 9 ms WIFALKER [192.168.1.1] 2 10 ms 18 ms 19 ms dsl2.ody.ca [216.240.3.22] 3 10 ms 10 ms 8 ms dsl2.ody.ca [216.240.3.21] 4 9 ms 9 ms 9 ms 204.101.4.201 5 25 ms 28 ms 29 ms bx5-chicagodt_xe3-1-0-0.net.bell.ca [64.230.186. 246] 6 30 ms 24 ms 29 ms 10gigabitethernet4-1.core1.chi1.he.net [206.223. 119.37] 7 79 ms 78 ms 80 ms 10gigabitethernet3-2.core1.den1.he.net [184.105. 213.86] 8 84 ms 99 ms 98 ms 10gigabitethernet4-4.core1.sjc2.he.net [184.105. 213.105] 9 90 ms 88 ms 98 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. ... and so on to 30 steps Very similar results for .16 |
Unknown Send message Joined: 17 Nov 99 Posts: 20 Credit: 27,512,627 RAC: 0 |
From Texas, unable to connect since the Tuesday outage. AT&T ISP Unable to ping IP address Tracing route to boinc2.ssl.berkeley.edu [208.68.240.18] over a maximum of 30 hops: 1 2 ms <1 ms <1 ms 205.203.34.251 2 <1 ms <1 ms <1 ms rrcs-24-173-14-65.sw.biz.rr.com [24.173.14.65] 3 1 ms <1 ms <1 ms xe-1-2-0.tmpltxdl1cw.tx.twcbiz.com [71.40.237.14] 4 19 ms 22 ms 59 ms xe-1-3-0.wacotxjb1cw.tx.twcbiz.com [24.73.243.28] 5 4 ms 4 ms 4 ms te1-1.wacotxmhe-p-rtr01.tx.twcbiz.com [24.73.243.56] 6 4 ms 4 ms 4 ms gig3-0-0.wacotxmhe-pe-rtr01.texas.rr.com [24.93.60.129] 7 5 ms 5 ms 4 ms gig2-0-1.dllatxl3-p-rtr01.texas.rr.com [24.93.35.11] 8 16 ms 11 ms 11 ms 24.93.60.69 9 5 ms 5 ms 5 ms ae-8-0.cr0.dfw10.tbone.rr.com [66.109.6.52] 10 45 ms 5 ms 5 ms ae-1-0.pr0.dfw10.tbone.rr.com [66.109.6.179] 11 5 ms 5 ms 5 ms dls-bb1-link.telia.net [213.248.89.197] 12 43 ms 43 ms 43 ms las-bb1-link.telia.net [213.155.131.77] 13 56 ms 56 ms 56 ms sjo-bb1-link.telia.net [213.248.80.16] 14 53 ms 53 ms 53 ms hurricane-113209-sjo-bb1.c.telia.net [213.248.86.54] 15 * * * Request timed out. 16 * * * Request timed out. 17 * * * Request timed out. |
perryjay Send message Joined: 20 Aug 02 Posts: 3377 Credit: 20,676,751 RAC: 0 |
Just to show you a good trace from Daytona Beach. I've not had any problems getting through. Microsoft Windows [Version 6.1.7601] Copyright (c) 2009 Microsoft Corporation. All rights reserved. C:\Users\perry>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 8 ms 8 ms 7 ms 10.109.80.1 3 8 ms 9 ms 9 ms ten0-3-0.orld43-ser1.bhn.net [72.31.194.88] 4 11 ms 10 ms 11 ms ten0-15-0-4-orld11-car1.bhn.net [97.69.193.76] 5 16 ms 15 ms 19 ms ten0-1-0-0.orld71-car1.bhn.net [97.69.193.136] 6 19 ms 19 ms 19 ms ae1.orld71-cbr1.bhn.net [72.31.194.8] 7 16 ms 15 ms 20 ms xe-11-2-0.bar1.Orlando1.Level3.net [4.79.116.145 ] 8 15 ms 15 ms 15 ms ae-0-11.bar2.Orlando1.Level3.net [4.69.137.146] 9 25 ms 35 ms 21 ms ae-5-5.ebr2.Miami1.Level3.net [4.69.148.209] 10 41 ms 22 ms 23 ms ae-2-52.edge1.Miami2.Level3.net [4.69.138.107] 11 50 ms 84 ms 67 ms mai-b1-link.telia.net [213.248.73.21] 12 47 ms 47 ms 48 ms dls-bb1-link.telia.net [80.91.252.61] 13 85 ms 86 ms 85 ms las-bb1-link.telia.net [213.155.131.77] 14 99 ms 99 ms 98 ms sjo-bb1-link.telia.net [213.248.80.16] 15 97 ms 96 ms 95 ms hurricane-113209-sjo-bb1.c.telia.net [213.248.86 .54] 16 97 ms 96 ms 96 ms 64.71.140.42 17 140 ms 137 ms * 208.68.243.254 18 138 ms 136 ms 133 ms boinc2.ssl.berkeley.edu [208.68.240.18] Trace complete. C:\Users\perry> PROUD MEMBER OF Team Starfire World BOINC |
Scarecrow Send message Joined: 15 Jul 00 Posts: 4520 Credit: 486,601 RAC: 0 |
I'll toss this in the mix, whether or not it's pertinent or helpful, I have no idea. First of all, I can't say as I've experienced any problems connecting, uploading or downloading. But bear in mind that I'm a very small fish in this big pond, so my volume of transfers is quite small. I did note the following when running traceroute from Linux (no Windows here). root@scarecrow:~# traceroute 208.68.240.13 traceroute to 208.68.240.13 (208.68.240.13), 30 hops max, 60 byte packets 1 vip72-196-1-1.cox.net (72.196.1.1) 9.785 ms 9.677 ms 9.601 ms 2 68.13.8.9 (68.13.8.9) 9.409 ms 9.356 ms 9.294 ms 3 68.13.9.21 (68.13.9.21) 9.997 ms 10.240 ms 10.164 ms 4 mtc1dsrj02-ae3.0.rd.om.cox.net (68.13.14.13) 9.554 ms 9.837 ms 9.804 ms 5 68.1.2.109 (68.1.2.109) 24.559 ms 24.636 ms 24.496 ms 6 10gigabitethernet1-2.core1.phx1.he.net (72.52.92.253) 50.633 ms 52.476 ms 52.550 ms 7 10gigabitethernet2-2.core1.lax1.he.net (72.52.92.249) 53.885 ms 53.886 ms 53.756 ms 8 10gigabitethernet1-3.core1.pao1.he.net (72.52.92.21) 76.833 ms 65.173 ms 68.585 ms 9 64.71.140.42 (64.71.140.42) 68.660 ms 68.643 ms 68.562 ms 10 208.68.243.254 (208.68.243.254) 74.295 ms 74.319 ms 74.334 ms 11 * * * 12 * * * 13 * * * 14 * * * 15 * * * 16 * * * 17 * * * 18 * * * 19 * * * 20 * * * 21 * * * 22 * * * 23 * * * 24 * * * 25 * * * 26 * * * 27 * * * 28 * * * 29 * * * 30 * * * Now, if I use the -I or -T switch in traceroute, using ICMP ECHO or TCP SYN for probes respectively, I get this: root@scarecrow:~# traceroute -I 208.68.240.13 traceroute to 208.68.240.13 (208.68.240.13), 30 hops max, 60 byte packets 1 vip72-196-1-1.cox.net (72.196.1.1) 8.611 ms 8.529 ms 9.318 ms 2 68.13.8.9 (68.13.8.9) 8.459 ms 8.604 ms 8.650 ms 3 68.13.9.21 (68.13.9.21) 9.194 ms * * 4 mtc1dsrj02-ae3.0.rd.om.cox.net (68.13.14.13) 8.956 ms 9.013 ms * 5 * * * 6 * * * 7 * * * 8 * * * 9 64.71.140.42 (64.71.140.42) 66.406 ms 66.395 ms * 10 * * * 11 * * * 12 * * * 13 * * * 14 * * * 15 * * * 16 * * * 17 * * * 18 * * * 19 * * * 20 boinc2.ssl.berkeley.edu (208.68.240.13) 184.415 ms 184.485 ms 184.487 ms The -T switch returns a similar successful trip. |
Dave Barstow Send message Joined: 14 May 99 Posts: 76 Credit: 15,064,044 RAC: 0 |
Same upload/reporting situation here in the Philippines... Been like this for at least 24 hours... DaBar-PC-HP6190 281 SETI@home 8/10/2011 8:28:01 PM Sending scheduler request: Requested by user. 282 SETI@home 8/10/2011 8:28:01 PM Reporting 44 completed tasks, not requesting new tasks 283 SETI@home 8/10/2011 8:31:04 PM Scheduler request failed: HTTP gateway timeout Ah Well... SOS, DD P.S.: I have run PingPlotter on all four servers, with the same result... 100% packet loss past HE |
KB7RZF Send message Joined: 15 Aug 99 Posts: 9549 Credit: 3,308,926 RAC: 2 |
Well, before the outage, I was fine. Now after the outage, I'm not able to upload, all pings to the 4 ip addresses time out, right now running the trace routes on them, and they are timing out as well. First a few lines from BOINC: 8/10/2011 8:19:21 AM SETI@home Started upload of 20mr11ae.29661.61438.11.10.108_0_0 8/10/2011 8:19:21 AM SETI@home Started upload of 20mr11ae.29661.61438.11.10.111_0_0 8/10/2011 8:19:43 AM Project communication failed: attempting access to reference site 8/10/2011 8:19:43 AM SETI@home Temporarily failed upload of 20mr11ae.29661.61438.11.10.108_0_0: connect() failed 8/10/2011 8:19:43 AM SETI@home Backing off 1 min 0 sec on upload of 20mr11ae.29661.61438.11.10.108_0_0 8/10/2011 8:19:43 AM SETI@home Temporarily failed upload of 20mr11ae.29661.61438.11.10.111_0_0: connect() failed 8/10/2011 8:19:43 AM SETI@home Backing off 1 min 0 sec on upload of 20mr11ae.29661.61438.11.10.111_0_0 8/10/2011 8:19:44 AM Internet access OK - project servers may be temporarily down. 8/10/2011 8:25:17 AM SETI@home Started upload of 20mr11ae.29661.61438.11.10.108_0_0 8/10/2011 8:25:17 AM SETI@home Started upload of 20mr11ae.29661.61438.11.10.111_0_0 8/10/2011 8:25:39 AM Project communication failed: attempting access to reference site 8/10/2011 8:25:39 AM SETI@home Temporarily failed upload of 20mr11ae.29661.61438.11.10.108_0_0: connect() failed 8/10/2011 8:25:39 AM SETI@home Backing off 1 min 0 sec on upload of 20mr11ae.29661.61438.11.10.108_0_0 8/10/2011 8:25:39 AM SETI@home Temporarily failed upload of 20mr11ae.29661.61438.11.10.111_0_0: connect() failed 8/10/2011 8:25:39 AM SETI@home Backing off 1 min 0 sec on upload of 20mr11ae.29661.61438.11.10.111_0_0 8/10/2011 8:25:40 AM Internet access OK - project servers may be temporarily down. 8/10/2011 8:29:13 AM SETI@home Beta Test Started upload of 21dc10aa.15423.6374.11.14.18_0_0 8/10/2011 8:29:35 AM Project communication failed: attempting access to reference site 8/10/2011 8:29:35 AM SETI@home Beta Test Temporarily failed upload of 21dc10aa.15423.6374.11.14.18_0_0: connect() failed 8/10/2011 8:29:35 AM SETI@home Beta Test Backing off 2 hr 8 min 14 sec on upload of 21dc10aa.15423.6374.11.14.18_0_0 8/10/2011 8:29:36 AM Internet access OK - project servers may be temporarily down. Now for the pings and trace routes: 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: 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), C:\Users\Home>ping 208.68.240.16 Pinging 208.68.240.16 with 32 bytes of data: Request timed out. Request timed out. Request timed out. Request timed out. Ping statistics for 208.68.240.16: Packets: Sent = 4, Received = 0, Lost = 4 (100% loss), C:\Users\Home>ping 208.68.240.18 Pinging 208.68.240.18 with 32 bytes of data: Request timed out. Request timed out. Request timed out. Request timed out. Ping statistics for 208.68.240.18: Packets: Sent = 4, Received = 0, Lost = 4 (100% loss), C:\Users\Home>ping 208.68.240.20 Pinging 208.68.240.20 with 32 bytes of data: Request timed out. Request timed out. Request timed out. Request timed out. Ping statistics for 208.68.240.20: Packets: Sent = 4, Received = 0, Lost = 4 (100% loss), C:\Users\Home>tracert 208.26.240.13 Tracing route to 208.26.240.13 over a maximum of 30 hops 1 1 ms 1 ms <1 ms 192.168.1.1 2 7 ms 6 ms 7 ms rno-atm0-mtu0.greatbasin.net [216.82.142.1] 3 108 ms 253 ms 265 ms rno-core0-ge.greatbasin.net [207.228.35.136] 4 136 ms 213 ms 207 ms 67.138.231.149 5 37 ms 231 ms 173 ms ge2-20.cr01.renonvmp.integra.net [209.63.99.169] 6 40 ms 27 ms 196 ms tg13-2.cr02.sntdcabl.integra.net [209.63.97.158] 7 15 ms 14 ms 14 ms tg1-1.br01.snjucacl.integra.net [209.63.81.66] 8 * * * Request timed out. 9 * * * Request timed out. 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:\Users\Home>tracert 208.26.240.16 Tracing route to 208.26.240.16 over a maximum of 30 hops 1 1 ms <1 ms 1 ms 192.168.1.1 2 11 ms 8 ms 8 ms rno-atm0-mtu0.greatbasin.net [216.82.142.1] 3 8 ms 9 ms 7 ms rno-core0-ge.greatbasin.net [207.228.35.136] 4 8 ms 7 ms 7 ms 67.138.231.149 5 15 ms 14 ms 14 ms ge2-20.cr01.renonvmp.integra.net [209.63.99.169] 6 24 ms 16 ms 16 ms tg13-2.cr02.sntdcabl.integra.net [209.63.97.158] 7 16 ms 14 ms 15 ms tg1-1.br01.snjucacl.integra.net [209.63.81.66] 8 * * * Request timed out. 9 * * * Request timed out. 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:\Users\Home>tracert 208.26.240.18 Tracing route to 208.26.240.18 over a maximum of 30 hops 1 1 ms 1 ms 1 ms 192.168.1.1 2 8 ms 11 ms 7 ms rno-atm0-mtu0.greatbasin.net [216.82.142.1] 3 9 ms 7 ms 7 ms rno-core0-ge.greatbasin.net [207.228.35.136] 4 8 ms 7 ms 7 ms 67.138.231.149 5 14 ms 14 ms 14 ms ge2-20.cr01.renonvmp.integra.net [209.63.99.169] 6 14 ms 14 ms 15 ms tg13-2.cr02.sntdcabl.integra.net [209.63.97.158] 7 14 ms 14 ms 14 ms tg1-1.br01.snjucacl.integra.net [209.63.81.66] 8 * * * Request timed out. 9 * * * Request timed out. 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:\Users\Home>tracert 208.26.240.20 Tracing route to 208.26.240.20 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 7 ms 6 ms 6 ms rno-core0-ge.greatbasin.net [207.228.35.136] 4 8 ms 7 ms 7 ms 67.138.231.149 5 111 ms 200 ms 199 ms ge2-20.cr01.renonvmp.integra.net [209.63.99.169] 6 15 ms 15 ms 16 ms tg13-2.cr02.sntdcabl.integra.net [209.63.97.158] 7 52 ms 27 ms 49 ms tg1-1.br01.snjucacl.integra.net [209.63.81.66] 8 * * * Request timed out. 9 * * * Request timed out. 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. |
Jim_S Send message Joined: 23 Feb 00 Posts: 4705 Credit: 64,560,357 RAC: 31 |
Microsoft Windows XP [Version 5.1.2600] (C) Copyright 1985-2001 Microsoft Corp. C:\Documents and Settings\ME>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 26 ms 26 ms 25 ms 66-38-56-1.static.bbtel.com [66.38.56.1] 3 26 ms 25 ms 25 ms bbtel-6509-g2-2.serial.blue.net [66.38.60.193] 4 27 ms 27 ms 27 ms rc-mlx8-ve31.serial.blue.net [66.38.58.169] 5 26 ms 26 ms 26 ms h1.126.55.139.static.ip.windstream.net [139.55.1 26.1] 6 30 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 59 ms h14.254.213.151.static.ip.windstream.net [151.21 3.254.14] 9 46 ms 46 ms 47 ms ip65-47-204-81.z204-47-65.customer.algx.net [65. 47.204.81] 10 50 ms 48 ms 49 ms v306.core1.dal1.he.net [64.71.189.217] 11 100 ms 100 ms 100 ms 10gigabitethernet1-2.core1.phx1.he.net [72.52.92 .253] 12 96 ms 96 ms 98 ms 10gigabitethernet2-2.core1.lax1.he.net [72.52.92 .249] 13 111 ms 110 ms 115 ms 10gigabitethernet1-3.core1.pao1.he.net [72.52.92 .21] 14 111 ms 110 ms 111 ms 64.71.140.42 15 * 147 ms 147 ms 208.68.243.254 16 * 180 ms 168 ms boinc2.ssl.berkeley.edu [208.68.240.13] Trace complete. First Success since June 15/16, Will check others now...Thanks for the hard Work Guys! *EDIT*All good now, A bit slow on last 4 hops...But all working.*/EDIT* I Desire Peace and Justice, Jim Scott (Mod-Ret.) |
Dave Barstow Send message Joined: 14 May 99 Posts: 76 Credit: 15,064,044 RAC: 0 |
Same upload/reporting situation here in the Philippines... Ping trace follows... Target Name: S@H SERVER IP: 208.68.240.13 Date/Time: 8/11/2011 12:48:38 AM to 8/11/2011 12:49:08 AM Hop Sent Err PL% Min Max Avg Host Name / [IP] 2 13 0 0.0 10 16 11 [172.22.0.1] 3 13 0 0.0 11 14 12 border1-f0-0-0.core1.CagayanDeOro.PH.cable21.net [203.177.75.254] 4 13 0 0.0 17 21 19 [203.177.160.177] 5 13 0 0.0 16 27 20 [120.28.0.165] 6 13 0 0.0 29 41 33 [120.28.0.26] 7 13 0 0.0 91 149 101 [120.28.0.134] 8 13 0 0.0 91 106 96 xe-0-1-0-xcr1.hkg.cw.net [203.169.57.37] 9 13 0 0.0 135 155 139 so-10-0-1-xcr1.tyo.cw.net [195.2.18.81] 10 13 0 0.0 238 252 242 xe-7-3-0-xcr1.lax.cw.net [195.2.10.217] 11 13 0 0.0 236 270 243 he.net.coresite.com [206.223.143.122] 12 13 0 0.0 246 277 251 10gigabitethernet7-3.core1.sjc2.he.net [184.105.213.5] 13 13 0 0.0 235 268 250 10gigabitethernet3-2.core1.pao1.he.net [72.52.92.69] 14 12 12 100.0 0 0 0 [-] 15 - 35 <clipped> (all the same as 14) Destination not reached in 35 hops |
Sutaru Tsureku Send message Joined: 6 Apr 07 Posts: 7105 Credit: 147,663,825 RAC: 5 |
O.K., since the last S@h server maintenance my machine (BOINC & Firefox) can't connect to the S@h server.. :-( I'm little bit surprised about the people that they post all the IP addresses. Is this not a little bit dangerous? E.g. the fist IP address at the traceroutes is the address of the PC in the home LAN network. The second is the IP address from/for the internet, correct? So at least this both addresses should be defaced (XXX.XXX.XXX.XXX), or not? And/or which addresses also? - Best regards! - Sutaru Tsureku, team seti.international founder. - Optimize your PC for higher RAC. - SETI@home needs your help. - |
Richard Haselgrove Send message Joined: 4 Jul 99 Posts: 14649 Credit: 200,643,578 RAC: 874 |
Unfortunately, in order to track down routing problems, IP adresses are needed. From what I see here, the first address in the list is the 'gateway' or router address, not the address of a PC. And mostly it's a Class C private, non-routable address - commonly the default address used by one of the major router manufacturers. 192.168.1.1 is commonest, both in the field installed routers I've come across, and in this list. The second address in the list is the gateway address of the next router upstream. That identifies your ISP, but it doesn't identify you. I've just tested here, and confirmed that my own external IP address - the only one which could be a security risk, if your firewall isn't up to scratch - is not included in a standard Windows tracert listing. |
Richard Haselgrove Send message Joined: 4 Jul 99 Posts: 14649 Credit: 200,643,578 RAC: 874 |
My external IP adress is included in a standard Windows tracert listing, even though I'm behind a router on all computers. It all depends upon your setup to and in your router, and your Windows firewall setup. Interesting. Mine definitely isn't - that's using PPPoA. Maybe PPPoE is different - or do you have a static IP? OK, revised advice - check your own listing before posting, and redact anything you're not happy with |
Highlander Send message Joined: 5 Oct 99 Posts: 167 Credit: 37,987,668 RAC: 16 |
and the connection problem is still going round the world, now here (Local Time):
This is UTC 19:40:41 for the last correct upload. Hope, this is only due to work in progress. And i hope, Seti Team can correlate the time with some of their changes. Like dr OM Iztok S52D, my connection-route stops at host: hurricane-113209-sjo-bb1.c.telia.net (213.248.86.54) PS: and it is the first time, this failing route happens here. edit2: uh, cricket graph now shows up completely traffic drop. Hope only this is the cause, due to reconfiguration... - Performance is not a simple linear function of the number of CPUs you throw at the problem. - |
Richard Haselgrove Send message Joined: 4 Jul 99 Posts: 14649 Credit: 200,643,578 RAC: 874 |
My external IP adress is included in a standard Windows tracert listing, even though I'm behind a router on all computers. It all depends upon your setup to and in your router, and your Windows firewall setup. It's not a bad idea to remind people to check. If your addresses are that similar, I could probably guess the IP from the Gateway. In my case, my gateway (listed) is 217.something, but my own IP is 86.something.else - with no similarity between the two. That gives an extra margin of safety. |
KB7RZF Send message Joined: 15 Aug 99 Posts: 9549 Credit: 3,308,926 RAC: 2 |
Just for info, my IP address is not in my trace route reports. :-) I made sure of that before I posted. :-) Just tried to use my cell phone as a wireless access point to upload as well, and still same problem. :-( Was hoping that would work. I'll try my work when I get there in about 2 hours and see if I can upload from there. If not, looks like I might have to go the proxy route to at least upload and report. |
Richard Haselgrove Send message Joined: 4 Jul 99 Posts: 14649 Credit: 200,643,578 RAC: 874 |
Just for info, my IP address is not in my trace route reports. :-) I made sure of that before I posted. :-) See the Panic thread first. Everything went completely flat on the Cricket graph, suddenly, about half an hour ago. I think somebody is disembowelling a router as we speak. |
KB7RZF Send message Joined: 15 Aug 99 Posts: 9549 Credit: 3,308,926 RAC: 2 |
Hey Richard, I saw that after I posted. I'm hoping thats what the cause is. I know when I first posted my trace routes and pings that things were up, so maybe this time it is due to that. I'm keeping my fingers crossed. I'll try things again later this afternoon, and we'll see what happens! :-) |
©2024 University of California
SETI@home and Astropulse are funded by grants from the National Science Foundation, NASA, and donations from SETI@home volunteers. AstroPulse is funded in part by the NSF through grant AST-0307956.