Hi all,

Using a looking glass can help to pin down if it's your provider thats at fault, or a problem with the detinations provider.

One such that I use when doing diagnostics is http://www.globalcrossing.com/network/network_looking_glass.aspx

Using the router to host traceroute is a pretty good test.

Regards

Kieran

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

Upload/Download works after some retries

3. What is your ISP?

German T-com

What is your geographic location?

50°55′38″N 11°35′10″E

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

ping for all address are working

6. How about traceroutes of the above four addresses?

faah@R2D2:~$ tcptraceroute 208.68.240.20
Selected device eth0, address 10.0.0.33, port 36110 for outgoing packets
Tracing the path to 208.68.240.20 on TCP port 80 (www), 30 hops max
 1  10.0.0.1  1.159 ms  0.794 ms  0.763 ms
 2  217.0.118.79  65.460 ms  62.744 ms  59.937 ms
 3  87.186.243.34  63.995 ms  62.958 ms  59.967 ms
 4  hh-ea4-i.HH.DE.NET.DTAG.DE (62.154.33.37)  71.869 ms  72.265 ms  75.684 ms
 5  80.156.161.122  71.839 ms  68.603 ms  71.686 ms
 6  hbg-bb2-link.telia.net (80.91.246.8)  72.082 ms  72.907 ms  75.836 ms
 7  nyk-bb2-link.telia.net (80.91.247.125)  155.914 ms  193.359 ms  155.793 ms
 8  sjo-bb1-link.telia.net (80.91.245.96)  231.934 ms  229.157 ms  231.995 ms
 9  hurricane-113209-sjo-bb1.c.telia.net (213.248.86.54)  239.929 ms  232.544 ms  251.953 ms
10  64.71.140.42  235.717 ms  231.171 ms  231.689 ms
11  208.68.243.254  235.961 ms  235.107 ms  235.840 ms
12  setiboinc.ssl.berkeley.edu (208.68.240.20) [open]  235.809 ms  236.481 ms  247.650 ms

faah@R2D2:~$ tcptraceroute 208.68.240.18
Selected device eth0, address 10.0.0.33, port 48217 for outgoing packets
Tracing the path to 208.68.240.18 on TCP port 80 (www), 30 hops max
 1  10.0.0.1  1.037 ms  0.824 ms  0.763 ms
 2  217.0.118.79  63.080 ms  65.643 ms  60.180 ms
 3  87.186.243.34  63.446 ms  66.193 ms  64.117 ms
 4  hh-ea4-i.HH.DE.NET.DTAG.DE (62.154.33.37)  75.165 ms  74.494 ms  75.744 ms
 5  80.156.161.122  71.564 ms  73.151 ms  74.920 ms
 6  hbg-bb2-link.telia.net (80.91.246.8)  71.838 ms  70.801 ms  72.052 ms
 7  nyk-bb2-link.telia.net (80.91.247.125)  151.520 ms  155.243 ms  159.851 ms
 8  sjo-bb1-link.telia.net (80.91.254.177)  227.814 ms  233.215 ms  231.995 ms
 9  hurricane-113209-sjo-bb1.c.telia.net (213.248.86.54)  239.624 ms  242.950 ms  231.568 ms
10  64.71.140.42  232.269 ms  230.712 ms  231.994 ms
11  208.68.243.254  235.779 ms  233.521 ms  236.053 ms
12  boinc2.ssl.berkeley.edu (208.68.240.18) [open]  231.933 ms  237.122 ms  243.622 ms

faah@R2D2:~$ tcptraceroute 208.68.240.16
Selected device eth0, address 10.0.0.33, port 56553 for outgoing packets
Tracing the path to 208.68.240.16 on TCP port 80 (www), 30 hops max
 1  10.0.0.1  1.129 ms  0.794 ms  0.763 ms
 2  217.0.118.79  63.080 ms  65.155 ms  59.539 ms
 3  87.186.243.34  63.599 ms  66.803 ms  63.965 ms
 4  hh-ea4-i.HH.DE.NET.DTAG.DE (62.154.33.34)  71.778 ms  68.817 ms  71.930 ms
 5  194.25.208.234  71.747 ms  70.892 ms  71.015 ms
 6  hbg-bb2-link.telia.net (80.91.249.202)  71.839 ms  73.029 ms  67.749 ms
 7  nyk-bb2-link.telia.net (80.91.247.123)  184.021 ms  156.097 ms  156.616 ms
 8  sjo-bb1-link.telia.net (213.155.130.131)  234.802 ms  233.093 ms  231.507 ms
 9  hurricane-113209-sjo-bb1.c.telia.net (213.248.86.54)  239.868 ms  230.408 ms  239.807 ms
10  64.71.140.42  232.361 ms  230.408 ms  235.474 ms
11  208.68.243.254  235.718 ms  234.863 ms  232.483 ms
12  * * *
13  * * *
14  * * *
^C

faah@R2D2:~$ tcptraceroute 208.68.240.13
Selected device eth0, address 10.0.0.33, port 43033 for outgoing packets
Tracing the path to 208.68.240.13 on TCP port 80 (www), 30 hops max
 1  10.0.0.1  1.068 ms  0.885 ms  0.763 ms
 2  217.0.118.79  60.639 ms  65.643 ms  59.051 ms
 3  87.186.243.42  63.721 ms  66.162 ms  63.965 ms
 4  hh-ea4-i.HH.DE.NET.DTAG.DE (62.154.33.37)  71.716 ms  73.487 ms  71.778 ms
 5  80.150.168.162  71.839 ms  72.419 ms  71.624 ms
 6  hbg-bb2-link.telia.net (80.91.246.8)  72.022 ms  122.315 ms  71.015 ms
 7  nyk-bb2-link.telia.net (80.91.247.125)  156.037 ms  154.419 ms  155.640 ms
 8  sjo-bb1-link.telia.net (213.155.130.131)  231.842 ms  230.408 ms  231.537 ms
 9  hurricane-113209-sjo-bb1.c.telia.net (213.248.86.54)  231.994 ms  234.253 ms  231.842 ms
10  64.71.140.42  231.568 ms  235.535 ms  231.873 ms
11  208.68.243.254  235.779 ms  233.459 ms  235.748 ms
12  boinc2.ssl.berkeley.edu (208.68.240.13) [open]  231.690 ms  236.603 ms  247.895 ms

7. Or nslookups of the above four addresses?

13.240.68.208.in-addr.arpa	name = boinc2.ssl.berkeley.edu
16.240.68.208.in-addr.arpa	name = setiboincdata.ssl.berkeley.edu
18.240.68.208.in-addr.arpa	name = boinc2.ssl.berkeley.edu
20.240.68.208.in-addr.arpa	name = setiboinc.ssl.berkeley.edu

---

1) Not quite sure if this is what you want, but I can't upload or download tasks

2) Last download at 08:31 4th july , upload failed at 08:34 4th july

3) Talk Talk

4) UK

5) Ping works - no losses

6) Tracert works but shows some latency from he 72.52.92.137 to he 75.52.92.29

7) Nslookups are fine.

ML1 got a data loss from 208.68.243.254, I'm not seeing the same, it responds fine not much incremental latency and no packet loss.



Does anyone know which ports are used to upload/download?
I did a netstat -a while trying to upload/download but I don't want to do a test telnet to all of the sockets which were reported.....

Thanks

Kieran

An update, most of my completed tasks just uploaded 21:05 4th July

hi matt,
at first i like to send you my thanks:
here my infos for you:
(more infos at the end after the answere of your questions)

1. Are you able to reach ANY of the upload, download, or scheduling servers?
SETI@home: download ok, upload not ok
Milkyway@home: download ok, upload ok
PrimeGrid: download ok, upload ok

2. When did you start having this problem?
at first:
26 Jun 2011 | 7:49:48 UTC

3. What is your ISP?
i59F731DB.versanet.de 89.247.hhh.iii 4.879ms

4. What is your geographic location?
Germany, town: Berlin

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

--- 208.68.240.13 ping statistics ---
4 packets transmitted, 4 received, 0% packet loss, time 3003ms
rtt min/avg/max/mdev = 202.651/203.695/205.080/1.114 ms
--- 208.68.240.16 ping statistics ---
4 packets transmitted, 4 received, 0% packet loss, time 3003ms
rtt min/avg/max/mdev = 200.306/202.881/207.999/3.041 ms
--- 208.68.240.18 ping statistics ---
4 packets transmitted, 4 received, 0% packet loss, time 3004ms
rtt min/avg/max/mdev = 202.914/208.700/220.635/7.172 ms
--- 208.68.240.20 ping statistics ---
4 packets transmitted, 4 received, 0% packet loss, time 3003ms
rtt min/avg/max/mdev = 202.174/203.807/208.198/2.558 ms

6. How about traceroutes of the above four addresses?

traceroute netzwerkdiagnostik: 208.68.240.13
Hop Host-Name IP Zeit 1 Zeit 2
1 i2c2g33.local aaa.bbb.ccc.ddd 0.117ms
1 Router aaa.bbb.ccc.eee 1.196ms
1 Router aaa.bbb.ccc.eee 1.253ms
2 fritz.box aaa.bbb.fff.ggg 6.112ms
3 i59F731DB.versanet.de 89.247.hhh.iii 4.879ms
3 ber022ibr001.versatel.de 62.214.64.185 31.616ms
4 v451.ber022isp005.versatel.de 62.214.108.89 32.625ms
5 10g-8-1.fra020isp005.versatel.de 62.214.110.50 46.485ms
6 dor2ip1.versatel.de 62.214.104.105 46.624ms
7 20gigabitethernet4-3.core1.fra1.he.net 80.81.192.172 51.879ms
8 10gigabitethernet1-4.core1.par2.he.net 184.105.213.162 57.411ms
9 10gigabitethernet7-1.core1.ash1.he.net 184.105.213.93 137.232ms
10 10gigabitethernet7-4.core1.pao1.he.net 184.105.213.177 208.621ms
11 10gigabitethernet1-4.core1.pao1.he.net 72.52.92.29 211.192ms
12 64.71.140.42 64.71.140.42 208.117ms
13 208.68.243.254 208.68.243.254 210.485ms
14 no reply *
15 no reply *
16 no reply *
17 no reply *
18 no reply *
19 no reply *
20 no reply *
21 no reply *
22 no reply *
23 no reply *
24 no reply *
25 no reply *
26 no reply *
27 no reply *
28 no reply *
29 no reply *
30 no reply *
31 no reply *

traceroute netzwerkdiagnostik: 208.68.240.16
1
.
3 ber022ibr001.versatel.de 62.214.64.185 34.180ms
4 v461.ber022isp005.versatel.de 62.214.108.105 173.430ms
5 10g-7-4.fra020isp005.versatel.de 62.214.110.190 46.492ms
6 dor2ip6.versatel.de 62.214.104.101 46.414ms
7 20gigabitethernet4-3.core1.fra1.he.net 80.81.192.172 46.709ms
8 10gigabitethernet1-4.core1.par2.he.net 184.105.213.162 56.297ms
9 10gigabitethernet7-1.core1.ash1.he.net 184.105.213.93 135.163ms
10 10gigabitethernet7-1.core1.ash1.he.net 184.105.213.93 136.868ms
11 10gigabitethernet1-4.core1.pao1.he.net 72.52.92.29 216.493ms
12 208.68.243.254 208.68.243.254 208.380ms
13 208.68.243.254 208.68.243.254 212.160ms
14 no reply *
.
31 no reply *


traceroute netzwerkdiagnostik: 208.68.240.18
1
.
3 ber022ibr001.versatel.de 62.214.64.185 31.615ms
4 v419.ber022isp005.versatel.de 62.214.108.121 31.202ms
5 10g-8-1.fra020isp005.versatel.de 62.214.110.50 45.296ms
6 dor2ip1.versatel.de 62.214.104.105 46.799ms
7 20gigabitethernet4-3.core1.fra1.he.net 80.81.192.172 51.364ms
8 10gigabitethernet1-2.core1.par1.he.net 72.52.92.89 61.478ms
9 10gigabitethernet7-1.core1.ash1.he.net 184.105.213.93 135.213ms
10 10gigabitethernet7-4.core1.pao1.he.net 184.105.213.177 214.107ms
11 64.71.140.42 64.71.140.42 204.051ms
12 208.68.243.254 208.68.243.254 312.159ms
13 208.68.243.254 208.68.243.254 216.667ms
14 no reply *
.
31 no reply *


traceroute netzwerkdiagnostik: 208.68.240.20
1
.
3 ber022ibr001.versatel.de 62.214.64.185 35.677ms
4 v461.ber022isp005.versatel.de 62.214.108.105 32.316ms
5 10g-7-4.fra020isp005.versatel.de 62.214.110.190 47.401ms
6 dor2ip1.versatel.de 62.214.104.105 47.262ms
7 20gigabitethernet4-3.core1.fra1.he.net 80.81.192.172 47.804ms
8 10gigabitethernet1-4.core1.par2.he.net 184.105.213.162 57.531ms
9 10gigabitethernet7-1.core1.ash1.he.net 184.105.213.93 146.390ms
10 10gigabitethernet7-1.core1.ash1.he.net 184.105.213.93 143.351ms
11 10gigabitethernet1-4.core1.pao1.he.net 72.52.92.29 217.041ms
12 64.71.140.42 64.71.140.42 208.685ms
13 208.68.243.254 208.68.243.254 211.286ms
14 no reply *
.
31 no reply *

7. Or nslookups of the above four addresses?

lookup 208.68.240.13
Quelle Zähler Adresstyp Record Type1 Auflösung
13.240.68.208.in-addr.arpa. 3256 IN PTR boinc2.ssl.berkeley.edu.

lookup 208.68.240.16
Quelle Zähler Adresstyp Record Type1 Auflösung
16.240.68.208.in-addr.arpa. 3297 IN PTR setiboincdata.ssl.berkeley.edu.

lookup 208.68.240.18
Quelle Zähler Adresstyp Record Type1 Auflösung
18.240.68.208.in-addr.arpa. 3600 IN PTR boinc2.ssl.berkeley.edu.

lookup 208.68.240.20
Quelle Zähler Adresstyp Record Type1 Auflösung
20.240.68.208.in-addr.arpa. 2868 IN PTR setiboinc.ssl.berkeley.edu.

greetings from
beso_berlin

More infos for you:

Zeige: Alle Computer | Nur aktive Computer der letzten 30 Tage

Computer ID Name Ort Durchschnittliches Guthaben Gesamtguthaben BOINC
Version CPU GPU Betriebssystem Letzter Kontakt
ID: 5542030
Details | Aufgaben
Projektübergreifende Statistiken:
BOINCstats.com Free-DC i2c2g33 47.76 32,531 6.10.17 GenuineIntel
Intel(R) Core(TM)2 Duo CPU E6550 @ 2.33GHz [Family 6 Model 15 Stepping 11]
(2 Prozessoren) --- Linux
2.6.32-32-generic 4 Jul 2011 | 16:44:52 UTC
ID: 5606787
Details | Aufgaben
Projektübergreifende Statistiken:
BOINCstats.com Free-DC beso-laptop 63.31 12,086 6.10.59 GenuineIntel
Intel(R) Core(TM)2 Duo CPU T5450 @ 1.66GHz [Family 6 Model 15 Stepping 13]
(2 Prozessoren) NVIDIA GeForce 8600M GS (255MB) Linux
2.6.38-8-generic 4 Jul 2011 | 15:32:26 UTC
ID: 5560512
Details | Aufgaben
Projektübergreifende Statistiken:
BOINCstats.com Free-DC Amd-3_Pc 0.05 3,850 6.10.58 AuthenticAMD
AMD Athlon(tm) [Family 6 Model 10 Stepping 0]
(1 Prozessoren) --- Microsoft Windows XP
Professional x86 Edition, Service Pack 3, (05.01.2600.00) 16 Jun 2011 | 19:06:32 UTC




Nächste 20
State: Alle (27) | In Bearbeitung (12) | Ausstehend (10) | Gültig (3) | Ungültig (0) | Fehler (2)
Anwendung: All (27) | Astropulse v5 (0) | Astropulse v505 (1) | SETI@home (0) | SETI@home Enhanced (26)

Task
anklicken für Einzelheiten
Zeige Namen Arbeitspaket
anklicken für Einzelheiten Computer Gesendet Meldezeit
oder Ablaufdatum
Erklärung Status Laufzeit
(sek) CPU Zeit
(sek) Punkte Anwendung
1980766938 766192915 5542030 4 Jul 2011 | 16:44:52 UTC 18 Jul 2011 | 11:01:32 UTC In Bearbeitung --- --- --- SETI@home Enhanced
Anonyme Plattform (CPU)
1980766937 766192909 5542030 4 Jul 2011 | 16:44:52 UTC 18 Jul 2011 | 11:01:32 UTC In Bearbeitung --- --- --- SETI@home Enhanced
Anonyme Plattform (CPU)
1980766936 766192903 5542030 4 Jul 2011 | 16:44:52 UTC 18 Jul 2011 | 11:01:32 UTC In Bearbeitung --- --- --- SETI@home Enhanced
Anonyme Plattform (CPU)
1980766934 766192891 5542030 4 Jul 2011 | 16:44:52 UTC 18 Jul 2011 | 11:01:32 UTC In Bearbeitung --- --- --- SETI@home Enhanced
Anonyme Plattform (CPU)
1980766933 766192885 5542030 4 Jul 2011 | 16:44:52 UTC 18 Jul 2011 | 11:01:32 UTC In Bearbeitung --- --- --- SETI@home Enhanced
Anonyme Plattform (CPU)
1980766932 766192879 5542030 4 Jul 2011 | 16:44:52 UTC 18 Jul 2011 | 11:01:32 UTC In Bearbeitung --- --- --- SETI@home Enhanced
Anonyme Plattform (CPU)
1980069891 774685764 5542030 3 Jul 2011 | 15:24:14 UTC 17 Jul 2011 | 9:40:54 UTC In Bearbeitung --- --- --- SETI@home Enhanced
Anonyme Plattform (CPU)
1980069890 774801447 5542030 3 Jul 2011 | 15:24:14 UTC 17 Jul 2011 | 9:40:54 UTC In Bearbeitung --- --- --- SETI@home Enhanced
Anonyme Plattform (CPU)
1980069868 774851650 5542030 3 Jul 2011 | 15:24:14 UTC 4 Jul 2011 | 5:19:26 UTC Fertig, Warte auf Bestätigung 11,492.48 6,389.75 ausstehend SETI@home Enhanced
Anonyme Plattform (CPU)
1980069867 774690985 5542030 3 Jul 2011 | 15:24:14 UTC 17 Jul 2011 | 9:40:54 UTC In Bearbeitung --- --- --- SETI@home Enhanced
Anonyme Plattform (CPU)
1979946265 775678085 5606787 3 Jul 2011 | 12:59:47 UTC 21 Aug 2011 | 23:23:37 UTC In Bearbeitung --- --- --- SETI@home Enhanced v5.28
1979946264 775677987 5606787 3 Jul 2011 | 12:59:47 UTC 17 Jul 2011 | 7:16:27 UTC In Bearbeitung --- --- --- SETI@home Enhanced v5.28
1979404414 775424030 5606787 3 Jul 2011 | 3:47:34 UTC 18 Aug 2011 | 15:54:14 UTC In Bearbeitung --- --- --- SETI@home Enhanced v5.28
1977117340 774357850 5542030 2 Jul 2011 | 0:44:43 UTC 3 Jul 2011 | 5:43:03 UTC Fertig, Warte auf Bestätigung 11,723.18 6,120.54 ausstehend SETI@home Enhanced
Anonyme Plattform (CPU)
1977117337 774357857 5542030 2 Jul 2011 | 0:44:43 UTC 3 Jul 2011 | 11:11:34 UTC Fertig und Bestätigt 12,174.69 6,174.34 19.92 SETI@home Enhanced
Anonyme Plattform (CPU)
1977117335 774357844 5542030 2 Jul 2011 | 0:44:43 UTC 3 Jul 2011 | 17:10:53 UTC Fertig, Warte auf Bestätigung 10,212.12 6,140.33 ausstehend SETI@home Enhanced
Anonyme Plattform (CPU)
1974270281 773014265 5606787 30 Jun 2011 | 13:29:58 UTC 3 Jul 2011 | 3:47:34 UTC Fertig und Bestätigt 37,986.81 27,314.74 100.47 SETI@home Enhanced v5.28
1973239131 772518222 5542030 30 Jun 2011 | 3:23:47 UTC 30 Jun 2011 | 13:03:09 UTC Fertig, Warte auf Bestätigung 9,104.52 6,163.89 ausstehend SETI@home Enhanced
Anonyme Plattform (CPU)
1973239128 772518210 5542030 30 Jun 2011 | 3:23:47 UTC 30 Jun 2011 | 19:23:01 UTC Fertig, Warte auf Bestätigung 7,465.84 6,660.65 ausstehend SETI@home Enhanced
Anonyme Plattform (CPU)
1971488328 771723001 5542030 28 Jun 2011 | 7:45:04 UTC 29 Jun 2011 | 0:22:32 UTC Fertig und Bestätigt 8,139.05 6,127.38 21.66 SETI@home Enhanced
Anonyme Plattform (CPU)




Vorherige 20
State: Alle (27) | In Bearbeitung (12) | Ausstehend (10) | Gültig (3) | Ungültig (0) | Fehler (2)
Anwendung: All (27) | Astropulse v5 (0) | Astropulse v505 (1) | SETI@home (0) | SETI@home Enhanced (26)

Task
anklicken für Einzelheiten
Zeige Namen Arbeitspaket
anklicken für Einzelheiten Computer Gesendet Meldezeit
oder Ablaufdatum
Erklärung Status Laufzeit
(sek) CPU Zeit
(sek) Punkte Anwendung
1970316609 771162134 5606787 27 Jun 2011 | 19:29:55 UTC 28 Jun 2011 | 6:41:12 UTC Fertig, Warte auf Bestätigung 6,825.75 5,452.14 ausstehend SETI@home Enhanced v5.28
1968075670 770126322 5542030 26 Jun 2011 | 8:07:11 UTC 29 Jun 2011 | 16:12:30 UTC Fertig, Warte auf Bestätigung 49,571.84 39,585.01 ausstehend SETI@home Enhanced
Anonyme Plattform (CPU)
1968075662 770126524 5542030 26 Jun 2011 | 8:07:11 UTC 28 Jun 2011 | 7:45:04 UTC Fertig, Warte auf Bestätigung 46,648.86 41,186.80 ausstehend SETI@home Enhanced
Anonyme Plattform (CPU)
1966628665 769457394 5606787 25 Jun 2011 | 6:10:37 UTC 26 Jun 2011 | 18:04:21 UTC Fertig, Warte auf Bestätigung 31,090.51 24,846.80 ausstehend SETI@home Enhanced v5.28
1965931355 769141353 5542030 24 Jun 2011 | 18:03:14 UTC 26 Jun 2011 | 7:49:48 UTC Fertig, Warte auf Bestätigung 31,770.34 28,956.26 ausstehend SETI@home Enhanced
Anonyme Plattform (CPU)
1952367901 762876925 5606787 15 Jun 2011 | 8:41:09 UTC 15 Jun 2011 | 8:46:18 UTC Fehler beim Berechnen 1.27 0.00 --- Astropulse v505 v5.06
1937706422 756158339 5542030 4 Jun 2011 | 22:16:47 UTC 7 Jun 2011 | 7:03:04 UTC Fehler beim Berechnen 34,569.39 32,278.53 --- SETI@home Enhanced
Anonyme Plattform (CPU)



Mo 04 Jul 2011 16:38:21 CEST SETI@home Message from server: Your app_info.xml file doesn't have a usable version of Astropulse v505.




Mo 04 Jul 2011 18:32:21 CEST SETI@home Started upload of 31mr11ai.17472.22971.4.10.51_2_0
Mo 04 Jul 2011 18:32:21 CEST SETI@home Started upload of 29ap11aj.2599.7429.4.10.86_4_0
Mo 04 Jul 2011 18:32:44 CEST Project communication failed: attempting access to reference site
Mo 04 Jul 2011 18:32:44 CEST SETI@home Temporarily failed upload of 31mr11ai.17472.22971.4.10.51_2_0: connect() failed
Mo 04 Jul 2011 18:32:44 CEST SETI@home Backing off 1 hr 23 min 43 sec on upload of 31mr11ai.17472.22971.4.10.51_2_0
Mo 04 Jul 2011 18:32:44 CEST SETI@home Temporarily failed upload of 29ap11aj.2599.7429.4.10.86_4_0: connect() failed
Mo 04 Jul 2011 18:32:44 CEST SETI@home Backing off 1 hr 44 min 7 sec on upload of 29ap11aj.2599.7429.4.10.86_4_0
Mo 04 Jul 2011 18:32:47 CEST Internet access OK - project servers may be temporarily down.
Mo 04 Jul 2011 18:34:24 CEST SETI@home update requested by user
Mo 04 Jul 2011 18:34:28 CEST SETI@home Sending scheduler request: Requested by user.
Mo 04 Jul 2011 18:34:28 CEST SETI@home Requesting new tasks
Mo 04 Jul 2011 18:34:33 CEST SETI@home Scheduler request completed: got 0 new tasks
Mo 04 Jul 2011 18:34:33 CEST SETI@home Message from server: Project has no tasks available
Mo 04 Jul 2011 18:39:38 CEST SETI@home Sending scheduler request: To fetch work.
Mo 04 Jul 2011 18:39:38 CEST SETI@home Requesting new tasks
Mo 04 Jul 2011 18:39:43 CEST SETI@home Scheduler request completed: got 0 new tasks
Mo 04 Jul 2011 18:39:43 CEST SETI@home Message from server: Project has no tasks available



Mo 04 Jul 2011 20:05:46 CEST SETI@home Sending scheduler request: To fetch work.
Mo 04 Jul 2011 20:05:46 CEST SETI@home Requesting new tasks
Mo 04 Jul 2011 20:05:51 CEST SETI@home Scheduler request completed: got 1 new tasks
Mo 04 Jul 2011 20:05:53 CEST SETI@home Started download of 27ap11ae.24271.11928.6.10.229
Mo 04 Jul 2011 20:05:57 CEST SETI@home Finished download of 27ap11ae.24271.11928.6.10.229


beso@i2c2g33:~$ ping -c 4 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=1 ttl=52 time=205 ms
64 bytes from 208.68.240.13: icmp_seq=2 ttl=52 time=202 ms
64 bytes from 208.68.240.13: icmp_seq=3 ttl=52 time=204 ms
64 bytes from 208.68.240.13: icmp_seq=4 ttl=52 time=202 ms

--- 208.68.240.13 ping statistics ---
4 packets transmitted, 4 received, 0% packet loss, time 3003ms
rtt min/avg/max/mdev = 202.651/203.695/205.080/1.114 ms


beso@i2c2g33:~$ ping -c 4 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=1 ttl=52 time=200 ms
64 bytes from 208.68.240.16: icmp_seq=2 ttl=52 time=201 ms
64 bytes from 208.68.240.16: icmp_seq=3 ttl=52 time=207 ms
64 bytes from 208.68.240.16: icmp_seq=4 ttl=52 time=202 ms

--- 208.68.240.16 ping statistics ---
4 packets transmitted, 4 received, 0% packet loss, time 3003ms
rtt min/avg/max/mdev = 200.306/202.881/207.999/3.041 ms


beso@i2c2g33:~$ ping -c 4 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=1 ttl=52 time=203 ms
64 bytes from 208.68.240.18: icmp_seq=2 ttl=52 time=207 ms
64 bytes from 208.68.240.18: icmp_seq=3 ttl=52 time=202 ms
64 bytes from 208.68.240.18: icmp_seq=4 ttl=52 time=220 ms

--- 208.68.240.18 ping statistics ---
4 packets transmitted, 4 received, 0% packet loss, time 3004ms
rtt min/avg/max/mdev = 202.914/208.700/220.635/7.172 ms


beso@i2c2g33:~$ ping -c 4 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=202 ms
64 bytes from 208.68.240.20: icmp_seq=2 ttl=53 time=202 ms
64 bytes from 208.68.240.20: icmp_seq=3 ttl=53 time=202 ms
64 bytes from 208.68.240.20: icmp_seq=4 ttl=53 time=208 ms

--- 208.68.240.20 ping statistics ---
4 packets transmitted, 4 received, 0% packet loss, time 3003ms
rtt min/avg/max/mdev = 202.174/203.807/208.198/2.558 ms

---

Still SOS. ;))

---

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

Hello all,

I was following solutions given in above threads. Nothing worked out. Just now I disabled the proxy [217.196.235.18], and could upload/download tasks.

All is well!

... and my best wishes to SETI community!!!

Regards,
+Vinay

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?

sometimes but nothing goes thru says "BOINC" server may be down

2. When did you start having this problem?

15 June 2011

3. What is your ISP?

216.127.140.6
216.127.140.7
216.127.140.8

4. What is your geographic location?

Baltimore Maryland USA

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

nada. goes into the ether and gets no response


6. How about traceroutes of the above four addresses?

as above

7. Or nslookups of the above four addresses?

have not done

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.

I keep trying to send completed work and requests new work but keeps getting a timeout error after a few minutes, occasionally says your server is down, and/or that contact has been made but server is not responding


Thanks!

- Matt

accessys@smart.net
Bob

And I just change to even this proxy (217.196.235.18) and it worked - the download for now. JUHU

---

Not really having problems, except no new work, but perhaps this will be data for a "control group":


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

Yes, as far as I can tell, I can reach them. But I get "server has no results to send".

2. When did you start having this problem?

06 July 2011

3. What is your ISP?

ATT Uverse

4. What is your geographic location?

San Jose, CA 95129 USA

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

I get good answers from all of them shown in the text below:
C:\Documents and Settings\Dad>ping 208.68.240.13

Pinging 208.68.240.13 with 32 bytes of data:

Reply from 208.68.240.13: bytes=32 time=26ms TTL=53
Reply from 208.68.240.13: bytes=32 time=27ms TTL=53
Reply from 208.68.240.13: bytes=32 time=28ms TTL=53
Reply from 208.68.240.13: bytes=32 time=27ms TTL=53

Ping statistics for 208.68.240.13:
Packets: Sent = 4, Received = 4, Lost = 0 (0% loss),
Approximate round trip times in milli-seconds:
Minimum = 26ms, Maximum = 28ms, Average = 27ms

C:\Documents and Settings\Dad>ping 208.68.240.16

Pinging 208.68.240.16 with 32 bytes of data:

Reply from 208.68.240.16: bytes=32 time=26ms TTL=53
Reply from 208.68.240.16: bytes=32 time=26ms TTL=53
Reply from 208.68.240.16: bytes=32 time=27ms TTL=53
Reply from 208.68.240.16: bytes=32 time=26ms TTL=53

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

C:\Documents and Settings\Dad>ping 208.68.240.18

Pinging 208.68.240.18 with 32 bytes of data:

Reply from 208.68.240.18: bytes=32 time=26ms TTL=53
Reply from 208.68.240.18: bytes=32 time=27ms TTL=53
Reply from 208.68.240.18: bytes=32 time=27ms TTL=53
Reply from 208.68.240.18: bytes=32 time=26ms TTL=53

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

C:\Documents and Settings\Dad>ping 208.68.240.20

Pinging 208.68.240.20 with 32 bytes of data:

Reply from 208.68.240.20: bytes=32 time=26ms TTL=53
Reply from 208.68.240.20: bytes=32 time=26ms TTL=53
Reply from 208.68.240.20: bytes=32 time=27ms TTL=53
Reply from 208.68.240.20: bytes=32 time=26ms TTL=53

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

C:\Documents and Settings\Dad>


6. How about traceroutes of the above four addresses?
Have not done but expect no problems.

7. Or nslookups of the above four addresses?

have not done

---

SOSDD on all.

---

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

Matt,
Post per recommendation:
Log:
7/6/2011 6:08:40 PM SETI@home update requested by user
7/6/2011 6:08:41 PM SETI@home Sending scheduler request: Requested by user.
7/6/2011 6:08:41 PM SETI@home Reporting 1 completed tasks, requesting new tasks for CPU and GPU
7/6/2011 6:09:03 PM Project communication failed: attempting access to reference site
7/6/2011 6:09:03 PM SETI@home Scheduler request failed: Couldn't connect to server
7/6/2011 6:09:04 PM Internet access OK - project servers may be temporarily down.
1. Are you able to reach ANY of the upload, download, or scheduling servers? No
2. When did you start having this problem? 19 June 2011
3. What is your ISP? Bellsouth\AT&T
4. What is your geographic location? Nashville TN
5. What happens when you ping 208.68.240.13? 208.68.240.16? 208.68.240.18? 208.68.240.20? See below
6. How about traceroutes of the above four addresses? See below
7. Or nslookups of the above four addresses? See below
Microsoft Windows [Version 6.1.7601]
Copyright (c) 2009 Microsoft Corporation. All rights reserved.


C:\>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:\>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:\>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:\>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:\>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 13 ms 12 ms 13 ms 70.159.248.16
3 13 ms 17 ms 13 ms 70.159.210.41
4 14 ms 13 ms 13 ms 12.81.32.132
5 12 ms 13 ms 14 ms 12.81.32.41
6 13 ms 17 ms 13 ms 74.175.192.150
7 23 ms 22 ms 22 ms cr1.nsvtn.ip.att.net [12.122.148.14]
8 22 ms 22 ms 22 ms cr2.attga.ip.att.net [12.122.28.105]
9 21 ms 22 ms 20 ms attga01jt.ip.att.net [12.122.80.221]
10 21 ms 21 ms 21 ms 192.205.37.82
11 102 ms 99 ms 99 ms Hurrican-Electric-LLC.Port-channel100.ar3.SJC2.g
blx.net [64.214.174.246]
12 94 ms 94 ms 97 ms 10gigabitethernet3-2.core1.pao1.he.net [72.52.92
.69]
13 * * * Request timed out.
14 * * * Request timed out.
15 ^C
C:\>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 192.168.1.1
2 12 ms 12 ms 12 ms 70.159.248.16
3 14 ms 13 ms 14 ms 70.159.210.97
4 14 ms 14 ms 14 ms 12.81.32.52
5 14 ms 14 ms 13 ms 12.81.32.39
6 53 ms 61 ms 13 ms 74.175.192.162
7 23 ms 23 ms 22 ms cr1.nsvtn.ip.att.net [12.122.148.14]
8 22 ms 22 ms 22 ms cr2.attga.ip.att.net [12.122.28.105]
9 21 ms 21 ms 21 ms attga01jt.ip.att.net [12.122.80.221]
10 21 ms 21 ms 20 ms 192.205.32.10
11 92 ms 96 ms 99 ms Hurrican-Electric-LLC.Port-channel100.ar3.SJC2.g
blx.net [64.214.174.246]
12 93 ms 121 ms 94 ms 10gigabitethernet3-2.core1.pao1.he.net [72.52.92
.69]
13 * * * Request timed out.
14 * ^C
C:\>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 13 ms 12 ms 12 ms 70.159.248.16
3 14 ms 13 ms 13 ms 70.159.210.97
4 15 ms 14 ms 13 ms 12.81.32.132
5 14 ms 14 ms 13 ms 12.81.32.37
6 13 ms 13 ms 14 ms 74.175.192.134
7 23 ms 22 ms 23 ms cr1.nsvtn.ip.att.net [12.122.148.14]
8 23 ms 22 ms 22 ms cr2.attga.ip.att.net [12.122.28.105]
9 20 ms 21 ms 21 ms attga01jt.ip.att.net [12.122.80.221]
10 21 ms 21 ms 21 ms 192.205.37.82
11 92 ms 127 ms 92 ms Hurrican-Electric-LLC.Port-channel100.ar3.SJC2.g
blx.net [64.214.174.246]
12 101 ms 99 ms 99 ms 10gigabitethernet3-2.core1.pao1.he.net [72.52.92
.69]
13 * * * Request timed out.
14 ^C
C:\>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 12 ms 12 ms 12 ms 70.159.248.16
3 13 ms 13 ms 13 ms 70.159.210.97
4 15 ms 14 ms 13 ms 12.81.32.132
5 13 ms 13 ms 13 ms 12.81.32.47
6 14 ms 13 ms 13 ms 74.175.192.198
7 23 ms 22 ms 22 ms cr1.nsvtn.ip.att.net [12.122.148.14]
8 22 ms 22 ms 21 ms cr2.attga.ip.att.net [12.122.28.105]
9 21 ms 21 ms 21 ms attga01jt.ip.att.net [12.122.80.221]
10 21 ms 21 ms 22 ms 192.205.35.90
11 102 ms 99 ms 99 ms Hurrican-Electric-LLC.Port-channel100.ar3.SJC2.g
blx.net [64.214.174.246]
12 94 ms 94 ms 96 ms 10gigabitethernet3-2.core1.pao1.he.net [72.52.92
.69]
13 * * * Request timed out.
14 * ^C

C:\>nslookup 208.68.240.13
Server: dns.bna.bellsouth.net
Address: 205.152.150.23

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


C:\>nslookup 208.68.240.16
Server: dns.bna.bellsouth.net
Address: 205.152.150.23

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


C:\>nslookup 208.68.240.18
Server: dns.bna.bellsouth.net
Address: 205.152.150.23

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


C:\>nslookup 208.68.240.20
Server: dns.bna.bellsouth.net
Address: 205.152.150.23

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

---

As per your request, please see the information below. Please note: Considering this has been an ongoing issue for so many participants and for such a relatively long period of time (nearly a month) should it not be considered "newsworthy" enough to be posted on the main S@h page?


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

2. When did you start having this problem? Aprox 16 June 2011

3. What is your ISP? NetZero (thru Verizon)

4. What is your geographic location? Monmouth County, New Jersey

5. What happens when you ping 208.68.240.13? 208.68.240.16? 208.68.240.18? 208.68.240.20? (See below)

6. How about traceroutes of the above four addresses? (See below)

7. Or nslookups of the above four addresses? (See below)


C:\>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:\>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:\>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:\>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:\>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 gateway.netzero.net [XXX.XXX.X.XXX]
2 34 ms 37 ms 35 ms XX.X.X.X
3 34 ms 35 ms 37 ms so-0-1-3-0.NWRK-CORE-RTR1.verizon-gni.net [130.8
1.13.41]
4 36 ms 37 ms 33 ms so-7-2-0-0.NWRK-BB-RTR1.verizon-gni.net [130.81.
20.160]
5 39 ms 35 ms 37 ms 0.so-7-0-0.XL3.EWR6.ALTER.NET [152.63.19.177]
6 39 ms 39 ms 41 ms 0.xe-2-1-0.XL3.NYC4.ALTER.NET [152.63.18.58]
7 36 ms 35 ms 39 ms GigabitEthernet6-0-0.GW1.NYC4.ALTER.NET [152.63.
20.49]
8 38 ms 39 ms 39 ms teliasonera-test.customer.alter.net [157.130.255
.206]
9 38 ms 37 ms 39 ms nyk-bb2-link.telia.net [213.155.130.244]
10 114 ms 114 ms 114 ms sjo-bb1-link.telia.net [80.91.254.177]
11 116 ms 118 ms 124 ms hurricane-113209-sjo-bb1.c.telia.net [213.248.86
.54]
12 * * * Request timed out.
13 * * * Request timed out.
14 * * * Request timed out.

30 * * * Request timed out.

Trace complete.

C:\>tracert 208.68.240.16

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

1 2 ms 1 ms <1 ms gateway.netzero.net [XXX.XXX.X.XXX]
2 34 ms 37 ms 35 ms XX.X.XX.X
3 35 ms 37 ms 35 ms so-0-1-3-0.NWRK-CORE-RTR2.verizon-gni.net [130.8
1.13.45]
4 33 ms 37 ms 37 ms so-7-2-0-0.NWRK-BB-RTR2.verizon-gni.net [130.81.
20.162]
5 33 ms 37 ms 37 ms 0.so-7-1-0.XL4.EWR6.ALTER.NET [152.63.16.129]
6 40 ms 39 ms 37 ms 0.so-1-0-3.XL4.NYC4.ALTER.NET [152.63.17.110]
7 38 ms 35 ms 41 ms GigabitEthernet7-0-0.GW1.NYC4.ALTER.NET [152.63.
20.53]
8 39 ms 41 ms 61 ms teliasonera-gw.customer.alter.net [157.130.60.14
]
9 107 ms 41 ms 39 ms nyk-bb2-link.telia.net [80.91.248.161]
10 111 ms 114 ms 114 ms sjo-bb1-link.telia.net [80.91.254.177]
11 126 ms 125 ms 124 ms hurricane-113209-sjo-bb1.c.telia.net [213.248.86
.54]
12 * * * Request timed out.
13 * * * Request timed out.
14 * * * Request timed out.

30 * * * Request timed out.

Trace complete.

C:\>tracert 208.68.240.18

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

1 2 ms 1 ms 1 ms gateway.netzero.net [XXX.XXX.X.XXX]
2 37 ms 35 ms 37 ms XX.X.XX.X
3 34 ms 37 ms 37 ms so-0-1-3-0.NWRK-CORE-RTR2.verizon-gni.net [130.8
1.13.45]
4 36 ms 37 ms 37 ms so-7-2-0-0.NWRK-BB-RTR2.verizon-gni.net [130.81.
20.162]
5 36 ms 35 ms 37 ms 0.so-7-0-0.XL4.EWR6.ALTER.NET [152.63.20.13]
6 93 ms 104 ms 60 ms 0.so-1-0-3.XL4.NYC4.ALTER.NET [152.63.17.110]
7 37 ms 37 ms 39 ms GigabitEthernet7-0-0.GW1.NYC4.ALTER.NET [152.63.
20.53]
8 38 ms 39 ms 41 ms teliasonera-gw.customer.alter.net [157.130.60.14
]
9 102 ms 60 ms 39 ms nyk-bb2-link.telia.net [80.91.248.161]
10 115 ms 116 ms 118 ms sjo-bb1-link.telia.net [213.155.130.131]
11 116 ms 116 ms 120 ms hurricane-113209-sjo-bb1.c.telia.net [213.248.86
.54]
12 * * * Request timed out.
13 * * * Request timed out.
14 * * * Request timed out.

30 * * * Request timed out.

Trace complete.


C:\>nslookup 208.68.240.13
Server: gateway.netzero.net
Address: XXX.XXX.X.XXX

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



C:\>nslookup 208.68.240.16
Server: gateway.netzero.net
Address: XXX.XXX.X.XXX

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



C:\>nslookup 208.68.240.18
Server: gateway.netzero.net
Address: XXX.XXX.X.XXX

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



C:\>nslookup 208.68.240.20
Server: gateway.netzero.net
Address: XXX.XXX.X.XXX

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

(ISP Alice/Hansenet in Hamburg/Germany. I'm living in Berlin.)

After my initial complaint on June 24th because of connection problems since about June 16th, leading to this thread, I'm connected again to SETI since two days!

This happened after configuring my client to use 217.196.235.18:80 as proxy.
("ddv3m" here wrote about. - Before, I never had a proxy.)

For another BOINC project (PrimeGrid) it did and does work all the time; I assume that the _un_defined SOCKS proxy option in client configuration is allowing this.
I do not fully understand this, but it works.

Could it be that the problem has to do (partly) with the proxy config at Seti side?

---

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

My thanks to Dr. Sperber for the suggestion to use a proxy server to circumvent the problem(s). I managed to find a free one that worked here:

http://www.checker.freeproxy.ru/checker/last_checked_proxies.php

After reconfiguring Boinc to use the proxy I was able to upload the 25 "ancient" W/Us that have been lingering for a month now.

Of course, there's no work currently available, but at least I can get it (I hope!)

---

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

Fr 8 Jul 11:40:55 2011 | SETI@home | Requesting new tasks for CPU
Fr 8 Jul 11:40:58 2011 | SETI@home | Scheduler request completed: got 0 new tasks
Fr 8 Jul 11:40:58 2011 | SETI@home | Project has no tasks available

2. When did you start having this problem?
Several days ago

3. What is your ISP?
German Telecom, DTAG

4. What is your geographic location?
Oldenburg, Germany; 53,8N 8,12E

5. What happens when you ping

--- 208.68.240.13 ping statistics ---
10 packets transmitted, 10 packets received, 0.0% packet loss
round-trip min/avg/max/stddev = 203.888/225.151/249.704/13.032 ms

--- 208.68.240.16 ping statistics ---
10 packets transmitted, 10 packets received, 0.0% packet loss
round-trip min/avg/max/stddev = 202.810/223.814/232.522/10.864 ms

--- 208.68.240.18 ping statistics ---
10 packets transmitted, 10 packets received, 0.0% packet loss
round-trip min/avg/max/stddev = 201.807/219.718/231.660/10.193 ms

--- 208.68.240.20 ping statistics ---
10 packets transmitted, 10 packets received, 0.0% packet loss
round-trip min/avg/max/stddev = 195.088/198.693/211.079/4.682 ms

6. How about traceroutes of the above four addresses?

traceroute to 208.68.240.20 (208.68.240.20), 64 hops max, 52 byte packets
1 fritz.box (192.168.178.1) 1.559 ms 1.088 ms 0.802 ms
2 87.186.224.127 (87.186.224.127) 21.627 ms 22.120 ms 21.713 ms
3 87.190.178.2 (87.190.178.2) 30.897 ms 21.072 ms 21.631 ms
4 hh-ea4-i.hh.de.net.dtag.de (62.154.33.34) 24.043 ms
hh-ea4-i.hh.de.net.dtag.de (62.154.33.37) 23.819 ms
hh-ea4-i.hh.de.net.dtag.de (62.154.33.34) 24.125 ms
5 80.150.168.162 (80.150.168.162) 24.615 ms
hbg-b2-link.telia.net (213.248.103.165) 24.845 ms
194.25.208.234 (194.25.208.234) 24.188 ms
6 hbg-bb1-link.telia.net (80.91.251.77) 23.691 ms
hbg-bb2-link.telia.net (80.91.251.81) 24.259 ms
hbg-bb1-link.telia.net (80.91.251.77) 24.307 ms
7 nyk-bb2-link.telia.net (80.91.247.123) 115.258 ms
nyk-bb1-link.telia.net (80.91.247.127) 115.201 ms 116.600 ms
8 sjo-bb1-link.telia.net (213.155.130.131) 204.903 ms
sjo-bb1-link.telia.net (213.155.130.129) 190.991 ms
sjo-bb1-link.telia.net (213.155.130.131) 190.572 ms
9 hurricane-113209-sjo-bb1.c.telia.net (213.248.86.54) 190.472 ms 190.421 ms 192.662 ms
10 64.71.140.42 (64.71.140.42) 369.776 ms 190.989 ms 191.458 ms
11 208.68.243.254 (208.68.243.254) 193.484 ms 194.972 ms 209.425 ms
12 * * *
13 * * *
14 * * *
15 * * *
16 * * *
17 * * *
18 * * *
19 * * *
20 * * *
21 * * *
22 * * *
23 * * *
24 * * *
25 * * *
26 * * *
27 * * *
28 * * *
29 * * *
30 * * *
31 * * *
32 * * *
33 * * *
34 * * *
35 * * *
36 * * *
37 * * *
38 * * *
I stopped it here ...

traceroute to 208.68.240.18 (208.68.240.18), 64 hops max, 52 byte packets
1 fritz.box (192.168.178.1) 1.441 ms 1.096 ms 0.863 ms
2 87.186.224.127 (87.186.224.127) 21.204 ms 21.339 ms 21.747 ms
3 87.190.178.10 (87.190.178.10) 21.608 ms 22.260 ms 21.427 ms
4 hh-ea4-i.hh.de.net.dtag.de (62.154.33.37) 24.053 ms
hh-ea4-i.hh.de.net.dtag.de (62.154.33.34) 35.514 ms
hh-ea4-i.hh.de.net.dtag.de (62.154.33.37) 23.916 ms
5 80.150.168.162 (80.150.168.162) 24.067 ms
80.156.161.122 (80.156.161.122) 23.657 ms
194.25.208.234 (194.25.208.234) 24.310 ms
6 hbg-bb2-link.telia.net (80.91.246.8) 178.675 ms
hbg-bb1-link.telia.net (80.91.251.77) 24.280 ms
hbg-bb1-link.telia.net (80.91.249.197) 24.286 ms
7 nyk-bb1-link.telia.net (80.91.247.127) 115.429 ms
nyk-bb2-link.telia.net (80.91.247.123) 114.984 ms 146.232 ms
8 sjo-bb1-link.telia.net (80.91.254.177) 190.883 ms
sjo-bb1-link.telia.net (80.91.252.153) 190.383 ms 190.837 ms
9 hurricane-113209-sjo-bb1.c.telia.net (213.248.86.54) 191.616 ms 190.355 ms 197.880 ms
10 64.71.140.42 (64.71.140.42) 192.069 ms 191.043 ms 191.166 ms
11 208.68.243.254 (208.68.243.254) 199.177 ms 216.213 ms 225.677 ms
12 * * *
13 * * *

traceroute to 208.68.240.16 (208.68.240.16), 64 hops max, 52 byte packets
1 fritz.box (192.168.178.1) 1.464 ms 1.110 ms 0.829 ms
2 87.186.224.127 (87.186.224.127) 22.033 ms 21.415 ms 20.666 ms
3 87.190.178.2 (87.190.178.2) 21.381 ms 21.742 ms 20.912 ms
4 hh-ea4-i.hh.de.net.dtag.de (62.154.33.34) 23.857 ms
hh-ea4-i.hh.de.net.dtag.de (62.154.33.37) 24.130 ms
hh-ea4-i.hh.de.net.dtag.de (62.154.33.34) 23.054 ms
5 80.150.168.162 (80.150.168.162) 24.925 ms
194.25.208.234 (194.25.208.234) 23.766 ms
hbg-b2-link.telia.net (213.248.103.165) 24.624 ms
6 hbg-bb1-link.telia.net (80.91.251.77) 23.971 ms
hbg-bb2-link.telia.net (80.91.251.81) 23.837 ms
hbg-bb1-link.telia.net (80.91.249.197) 24.588 ms
7 nyk-bb1-link.telia.net (80.91.247.127) 124.597 ms
nyk-bb1-link.telia.net (80.91.247.129) 114.249 ms
nyk-bb2-link.telia.net (80.91.247.123) 145.064 ms
8 sjo-bb1-link.telia.net (213.248.80.1) 190.009 ms
sjo-bb1-link.telia.net (213.155.130.129) 190.188 ms
sjo-bb1-link.telia.net (213.155.130.131) 190.416 ms
9 hurricane-113209-sjo-bb1.c.telia.net (213.248.86.54) 190.945 ms 192.912 ms 199.818 ms
10 64.71.140.42 (64.71.140.42) 190.392 ms 191.094 ms 190.626 ms
11 208.68.243.254 (208.68.243.254) 225.973 ms 213.858 ms 197.603 ms
12 * * *
13 * * *

traceroute to 208.68.240.13 (208.68.240.13), 64 hops max, 52 byte packets
1 fritz.box (192.168.178.1) 1.468 ms 1.074 ms 0.836 ms
2 87.186.224.127 (87.186.224.127) 21.618 ms 21.576 ms 21.550 ms
3 87.190.178.6 (87.190.178.6) 21.431 ms 22.157 ms 96.935 ms
4 hh-ea4-i.hh.de.net.dtag.de (62.154.33.34) 23.984 ms
hh-ea4-i.hh.de.net.dtag.de (62.154.33.37) 24.138 ms
hh-ea4-i.hh.de.net.dtag.de (62.154.33.34) 23.337 ms
5 hbg-b2-link.telia.net (213.248.103.165) 24.453 ms
80.150.168.162 (80.150.168.162) 24.520 ms 24.103 ms
6 hbg-bb2-link.telia.net (80.91.249.202) 24.069 ms
hbg-bb1-link.telia.net (80.91.246.6) 24.039 ms 24.237 ms
7 nyk-bb2-link.telia.net (80.91.247.125) 114.678 ms
nyk-bb1-link.telia.net (80.91.247.127) 115.435 ms
nyk-bb2-link.telia.net (80.91.247.125) 184.320 ms
8 sjo-bb1-link.telia.net (80.91.254.177) 190.949 ms 190.482 ms
sjo-bb1-link.telia.net (213.155.130.131) 190.369 ms
9 hurricane-113209-sjo-bb1.c.telia.net (213.248.86.54) 193.617 ms 199.041 ms 200.070 ms
10 64.71.140.42 (64.71.140.42) 191.053 ms 191.125 ms 191.682 ms
11 208.68.243.254 (208.68.243.254) 206.492 ms 195.824 ms 199.760 ms
12 * * *
13 *

7. Or nslookups of the above four addresses?

; <<>> DiG 9.6.0-APPLE-P2 <<>> -x 208.68.240.13 any +multiline +nocomments +nocmd +noquestion +nostats +search
;; global options: +cmd
13.240.68.208.in-addr.arpa. 86377 IN PTR boinc2.ssl.berkeley.edu.

; <<>> DiG 9.6.0-APPLE-P2 <<>> -x 208.68.240.16 any +multiline +nocomments +nocmd +noquestion +nostats +search
;; global options: +cmd
16.240.68.208.in-addr.arpa. 86400 IN PTR setiboincdata.ssl.berkeley.edu.

; <<>> DiG 9.6.0-APPLE-P2 <<>> -x 208.68.240.18 any +multiline +nocomments +nocmd +noquestion +nostats +search
;; global options: +cmd
18.240.68.208.in-addr.arpa. 86400 IN PTR boinc2.ssl.berkeley.edu.

; <<>> DiG 9.6.0-APPLE-P2 <<>> -x 208.68.240.20 any +multiline +nocomments +nocmd +noquestion +nostats +search
;; global options: +cmd
20.240.68.208.in-addr.arpa. 86268 IN PTR setiboinc.ssl.berkeley.edu.


Just my 2 cents

Edit: only SETI does not run. My other projects are doing well

Edit: only SETI does not run. My other projects are doing well

But SETI does "run"; you got an answer from the scheduler:

Fr  8 Jul 11:40:58 2011 | SETI@home | Scheduler request completed: got 0 new tasks
Fr  8 Jul 11:40:58 2011 | SETI@home | Project has no tasks available

Gruß,
Gundolf

Still no connection with or without PROXY.

---

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

FYI - As of 19:38 EDT I was able to connect (and connect faster) without using a proxy. Just thought you'd like to know.

---

FYI - As of 19:38 EDT I was able to connect (and connect faster) without using a proxy. Just thought you'd like to know.

Not Me...Still no connection with or without PROXY.

---

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

Still down, No good Traces or Pings.


7/11/2011 9:35:33 PM | SETI@home | Sending scheduler request: To fetch work.
7/11/2011 9:35:33 PM | SETI@home | Requesting new tasks for CPU
7/11/2011 9:35:55 PM | | Project communication failed: attempting access to reference site
7/11/2011 9:35:55 PM | SETI@home | Scheduler request failed: Couldn't connect to server
7/11/2011 9:35:57 PM | | Internet access OK - project servers may be temporarily down.

---

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