I sent a report to he.net and got this reply:

The problem appears to be within seti@home. The pao hop is the last hop
before we hand traffic off to them. After that is where things are dying.

You would need to contact seti@home about the issue.

Regards,

So... back to seti...

Not sure if this is at all useful but ...

Answers to your questions

1 Not able to upload or download
2 Mon night/Tues am 22/23 August 2011 UTC
3 BT.net
4 UK
5 All pings result in Request timed out
6 Traceroutes all fail after 10gigabitethernet7-4.core1.pau1.he.net (184.105.213.177)
7 All nslookups resolve to seti/boinc servers

People, I'm sorry that I don't understand all the things you are talking about, but I want to say that I live in the Northern Part of West Virginia, and I have not had any problems connecting to SETI. I'm having problems getting work, as there is NO WORK to get at the moment, but I am connecting to the SETI Servers. I am on Comcast Cable. Don't know if this may help, but wanted to let you know.

Hello Matt,

Just to help you with the network problems.

1. No upload or download.
2. After 4 Aug 2011 8:37:48 UTC.
3. solcon.nl
4. The Netherlands
5. All 4 server gave 100% drop.
6. How about traceroutes of the above four addresses?
1 1 ms 1 ms 1 ms 192.168.32.254
2 19 ms 18 ms 18 ms 212.45.33.234
3 18 ms 19 ms 19 ms 212.45.33.179
4 19 ms 19 ms 19 ms 212.45.33.1
5 19 ms 19 ms 19 ms 195.69.145.150
6 29 ms 29 ms 29 ms 184.105.213.102
7 117 ms 107 ms 116 ms 184.105.213.93
8 183 ms 179 ms 177 ms 184.105.213.177
9 * * * Request timed out.
10 * * * Request timed out.
11 * * * Request timed out.
12 * * * Request timed out.
13 * * * Request timed out.
14 * * * Request timed out.
10gigabitethernet7-4.core1.pao1.he.net is dropping the connections....
7. All nsloopups are working

Regards,

Pascal

---

It's 100% certain. There is no intelligent life in this universe.

Still no connection as of 8/28/2011. I'm located in Northern California, and my ISP is Succeed.net.

Here are ping results:

PING 208.68.240.16 (208.68.240.16) 56(84) bytes of data.
^C
--- 208.68.240.16 ping statistics ---
9 packets transmitted, 0 received, 100% packet loss, time 8064ms

PING 208.68.240.18 (208.68.240.18) 56(84) bytes of data.
^C
--- 208.68.240.18 ping statistics ---
9 packets transmitted, 0 received, 100% packet loss, time 8064ms

PING 208.68.240.20 (208.68.240.20) 56(84) bytes of data.
^C
--- 208.68.240.20 ping statistics ---
13 packets transmitted, 0 received, 100% packet loss, time 12096ms

NSlookup give this, with similar results for the other three addresses:
bbeeman@zeus:~$ nslookup 208.68.240.16
Server: 127.0.0.1
Address: 127.0.0.1#53

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

Authoritative answers can be found from:
240.68.208.in-addr.arpa nameserver = adns1.berkeley.edu.
240.68.208.in-addr.arpa nameserver = adns2.berkeley.edu.
adns1.berkeley.edu internet address = 128.32.136.3
adns1.berkeley.edu has AAAA address 2607:f140:ffff:fffe::3
adns2.berkeley.edu internet address = 128.32.136.14
adns2.berkeley.edu has AAAA address 2607:f140:ffff:fffe::e

Traceroute fails:
traceroute to 208.68.240.20 (208.68.240.20), 30 hops max, 60 byte packets
1 192.168.1.1 (192.168.1.1) 0.562 ms 0.797 ms 0.868 ms
2 192.168.100.1 (192.168.100.1) 2.129 ms 2.127 ms *
3 * * *
4 * * *
5 * * *
6 * fiber.succeed.net (75.101.108.29) 14.337 ms 16.497 ms
7 gig2-0.gw2.scrmca01.sonic.net (75.101.108.1) 16.884 ms 17.102 ms 21.872 ms
8 0.so-3-1-0.gw3.200p-sf.sonic.net (64.142.0.253) 30.385 ms * *
9 * * *
10 * * *
11 * * *
12 * * *
13 * * *
14 * * *
15 * * *
16 * * *
17 * * *
18 * * *
19 * * *
20 * * *
21 * * *
22 * * *
23 * * *
24 * * *
25 * * *
26 * * *
27 * * *
28 * * *
29 * * *
30 * * *

I had a small window in which one machine was able to upload on Wednesday, Aug. 24, but have been out of work on all machines for over a week.

---

After weeks of not being able to connect from IP 187.140.205.102 in Mexico (I used Hotspot shield to get a trickle of work) I can connect just fine, but there IS no work to get, according to the message I receive and "project status" on BOINC. This is unfortunate, as I miss crunching SETI.

Doesn't look like much is coming out of Seti right now. My Rosetta work units are keeping my computer busy while I wait for Seti to start sending out WU again.

Doesn't look like much is coming out of Seti right now. My Rosetta work units are keeping my computer busy while I wait for Seti to start sending out WU again.

Is this the general consensus? I hope so because it has been frustrating trying to figure out what I did wrong.

Doesn't look like much is coming out of Seti right now. My Rosetta work units are keeping my computer busy while I wait for Seti to start sending out WU again.

Is this the general consensus? I hope so because it has been frustrating trying to figure out what I did wrong.

Yes that is the general consensus, look at the Status page, there is no work being split, and look at the Cricket graph, there is little work being downloaded.

Claggy

Since all Spitters are down, no work is available, but UPLoads aren't
a problem, over here, the Netherlands.
And the Cricket Graph is clear and now shows some download 'spikes'.
Download servers are UP.
SERVER Page .
From my Laptop:

28-8-2011 20:36:46 | SETI@home | Started upload of 12ap11af.15167.263940.13.10.44_1_0
28-8-2011 20:36:50 | SETI@home | Finished upload of 12ap11af.15167.263940.13.10.44_1_0
28-8-2011 20:36:52 | SETI@home | Sending scheduler request: To fetch work.
28-8-2011 20:36:52 | SETI@home | Reporting 1 completed tasks, requesting new tasks for CPU
28-8-2011 20:36:54 | SETI@home | Scheduler request completed: got 0 new tasks
28-8-2011 20:36:54 | SETI@home | Project has no tasks available
Only my 'production rig', has no SETI work, but my I7-2600+
2 EAH5870s are crunching 3 VLAR MB WUs and 1 AstroPulse. Which are
for SETI Bêta though. And Forum Web Pages are UP, but no down
or UPLoads, atm..
Also 4(+) 500+ hours of CPU CPDN work.... (Turned HT off as an experiment
cause of instabillity of the GPUs and a (too) high CPU use for loading/unloading
GPUs, CPU use sometimes rose to 50%!)(Also a high ~4.8GByte RAM use).

Could be tuesday, maintenance day, before someone can do something
about it?
By the way, something odd about the actual time, 9 minutes ahead
of my 'system-time'?

---

Doesn't look like much is coming out of Seti right now. My Rosetta work units are keeping my computer busy while I wait for Seti to start sending out WU again.

Is this the general consensus? I hope so because it has been frustrating trying to figure out what I did wrong.

Yes that is the general consensus, look at the Status page, there is no work being split, and look at the Cricket graph, there is little work being downloaded.

Claggy

Thanks Claggy.

@ all

If your BOINC can't connect to the S@h server, and you can't see the test pages if you click in your browser there:

http://208.68.240.16 (upload)
http://208.68.240.13 (download #1)
http://208.68.240.18 (download #2)
http://208.68.240.20 (scheduler)

..you should go back to the first message of this thread and answer Matt's questions.


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

---

Still no change, so upon request:

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

No, only erratic via HTTP-Proxy 95.166.206.2:8080


2. When did you start having this problem?

24th of August evening (local time)


3. What is your ISP?

upc cablecom


4. What is your geographic location?

Switzerland, Zurich region.


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

All four requests timed out with 100% packet loss.


6. How about traceroutes of the above four addresses?

C:\>tracert -h 15 -4 208.68.240.13

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

1 <1 ms <1 ms <1 ms CHAS01 [192.168.62.1]
2 8 ms 9 ms 9 ms 217-162-191-1.dynamic.hispeed.ch [217.162.191.1]
3 8 ms 7 ms 9 ms 217-168-54-61.static.cablecom.ch [217.168.54.61]
4 10 ms 11 ms 9 ms 172.31.208.69
5 120 ms 120 ms 129 ms 84-116-130-49.aorta.net [84.116.130.49]
6 118 ms 117 ms 119 ms us-was03a-rd1-xe-0-3-0.aorta.net [84.116.130.66]
7 119 ms 121 ms 119 ms us-nyc01c-rd1-ge-15-0-0.aorta.net [84.116.130.161]
8 120 ms 120 ms 119 ms us-nyc01b-ri1-xe-4-1-0.aorta.net [213.46.190.98]
9 126 ms 136 ms 122 ms core1.nyc4.he.net [198.32.118.57]
10 200 ms 206 ms 193 ms 10gigabitethernet10-2.core1.sjc2.he.net [184.105.213.197]
11 196 ms 199 ms 198 ms 10gigabitethernet3-2.core1.pao1.he.net [72.52.92.69]
12 * * * Zeitüberschreitung der Anforderung.
13 * * * Zeitüberschreitung der Anforderung.
14 * * * Zeitüberschreitung der Anforderung.
15 * * * Zeitüberschreitung der Anforderung.

Ablaufverfolgung beendet.

C:\>tracert -h 20 -4 208.68.240.16

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

1 <1 ms <1 ms <1 ms CHAS01 [192.168.62.1]
2 9 ms 7 ms 7 ms 217-162-191-1.dynamic.hispeed.ch [217.162.191.1]
3 9 ms 9 ms 9 ms 217-168-54-61.static.cablecom.ch [217.168.54.61]
4 72 ms 9 ms 9 ms 172.31.208.69
5 120 ms 120 ms 121 ms 84-116-130-49.aorta.net [84.116.130.49]
6 119 ms 117 ms 117 ms us-was03a-rd1-xe-0-3-0.aorta.net [84.116.130.66]
7 120 ms 121 ms 119 ms us-nyc01c-rd1-ge-15-0-0.aorta.net [84.116.130.161]
8 120 ms 120 ms 121 ms us-nyc01b-ri1-xe-4-1-0.aorta.net [213.46.190.98]
9 128 ms 124 ms 124 ms core1.nyc4.he.net [198.32.118.57]
10 201 ms 199 ms 199 ms 10gigabitethernet10-1.core1.sjc2.he.net [184.105.213.173]
11 201 ms 200 ms 199 ms 10gigabitethernet3-2.core1.pao1.he.net [72.52.92.69]
12 * * * Zeitüberschreitung der Anforderung.
13 * * * Zeitüberschreitung der Anforderung.
14 * * * Zeitüberschreitung der Anforderung.
15 * * * Zeitüberschreitung der Anforderung.

Ablaufverfolgung beendet.

C:\>tracert -h 15 -4 208.68.240.18

Routenverfolgung zu boinc2.ssl.berkeley.edu [208.68.240.18] über maximal 15 Absc
hnitte:

1 <1 ms <1 ms <1 ms CHAS01 [192.168.62.1]
2 9 ms 8 ms 9 ms 217-162-191-1.dynamic.hispeed.ch [217.162.191.1]
3 8 ms 9 ms 8 ms 217-168-54-61.static.cablecom.ch [217.168.54.61]
4 9 ms 9 ms 10 ms 172.31.208.69
5 119 ms 119 ms 160 ms 84.116.134.25
6 118 ms 119 ms 119 ms us-was03a-rd1-xe-1-3-0.aorta.net [84.116.130.70]
7 119 ms 119 ms 122 ms us-nyc01c-rd1-ge-15-0-0.aorta.net [84.116.130.161]
8 119 ms 120 ms 119 ms us-nyc01b-ri1-xe-4-1-0.aorta.net [213.46.190.98]
9 120 ms 119 ms 123 ms core1.nyc4.he.net [198.32.118.57]
10 189 ms 190 ms 199 ms 10gigabitethernet10-2.core1.sjc2.he.net [184.105.213.197]
11 189 ms 189 ms 193 ms 10gigabitethernet3-2.core1.pao1.he.net [72.52.92.69]
12 * * * Zeitüberschreitung der Anforderung.
13 * * * Zeitüberschreitung der Anforderung.
14 * * * Zeitüberschreitung der Anforderung.
15 * * * Zeitüberschreitung der Anforderung.

Ablaufverfolgung beendet.

C:\>tracert -h 15 -4 208.68.240.20

Routenverfolgung zu setiboinc.ssl.berkeley.edu [208.68.240.20] über maximal 15 A
bschnitte:

1 <1 ms <1 ms <1 ms CHAS01 [192.168.62.1]
2 10 ms 8 ms 9 ms 217-162-191-1.dynamic.hispeed.ch [217.162.191.1]
3 8 ms 7 ms 9 ms 217-168-54-61.static.cablecom.ch [217.168.54.61]
4 12 ms 11 ms 39 ms 172.31.208.69
5 118 ms 118 ms 118 ms 84-116-130-53.aorta.net [84.116.130.53]
6 120 ms 118 ms 119 ms us-was03a-rd1-xe-1-3-0.aorta.net [84.116.130.70]
7 119 ms 121 ms 119 ms us-nyc01c-rd1-ge-15-0-0.aorta.net [84.116.130.161]
8 119 ms 119 ms 121 ms us-nyc01b-ri1-xe-4-1-0.aorta.net [213.46.190.98]
9 126 ms 124 ms 125 ms core1.nyc4.he.net [198.32.118.57]
10 189 ms 189 ms 196 ms 10gigabitethernet10-2.core1.sjc2.he.net [184.105.213.197]
11 197 ms 198 ms 199 ms 10gigabitethernet3-2.core1.pao1.he.net [72.52.92.69]
12 * * * Zeitüberschreitung der Anforderung.
13 * * * Zeitüberschreitung der Anforderung.
14 * * * Zeitüberschreitung der Anforderung.
15 * * * Zeitüberschreitung der Anforderung.

Ablaufverfolgung beendet.

C:\>


7. Or nslookups of the above four addresses?

C:\>nslookup 208.68.240.13
Server: UnKnown
Address: fe80::224:b2ff:fed8:324a

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


C:\>nslookup 208.68.240.16
Server: UnKnown
Address: fe80::224:b2ff:fed8:324a

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


C:\>nslookup 208.68.240.18
Server: UnKnown
Address: fe80::224:b2ff:fed8:324a

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


C:\>nslookup 208.68.240.20
Server: UnKnown
Address: fe80::224:b2ff:fed8:324a

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


Hope it helps, keep fingers crossed ;-)

---

OK, wanted to let you all know, that I DID get one little work unit last night. There seemed to be no problem downloading it. After crunching it, it uploaded without a hitch. Haven't received any work since.
Location, Northern Panhandle of West Virginia
ISP Comcast Cable Internet Service.

All I can say is, it seems to be working for me. Don't know if anyone else in this area is having problems or not.
To be honest, I've never had any problems uploading or downloading to the SETI servers, but I know that there are a lot of people that can't connect. If I had any brains like you guys, I'd try to help you figure it out, but No brains here. Hope this all gets fixed soon.

Still no change here...


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

2. When did you start having this problem?
on or about 24th August

3. What is your ISP?
Actrix.co.nz

4. What is your geographic location?
New Zealand

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

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),

6. How about traceroutes of the above four addresses?

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 33 ms 32 ms 33 ms wn-cisco-r5-lo-5.connections.net.nz [202.49.152.169]
3 34 ms 34 ms 33 ms wn-sum-1-wnlan7.connections.net.nz [202.49.152.161]
4 63 ms 34 ms 36 ms 192.168.100.45
5 72 ms 95 ms 73 ms p1-telstra-int-pri.connections.net.nz [192.100.53.45]
6 74 ms 70 ms 70 ms 203.167.233.10
7 204 ms 201 ms 205 ms unknown.net.reach.com [202.84.142.110]
8 201 ms 200 ms 194 ms i-0-5-1-0.paix-core01.bi.reach.com [202.84.140.90]
9 246 ms 194 ms 196 ms i-3-1.paix01.bi.reach.com [202.84.251.34]
10 210 ms 207 ms 214 ms paix.he.net [198.32.176.20]
11 * * * Request timed out.
12 * * * Request timed out.
13 * * * Request timed out.
14 * * * Request timed out.

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 33 ms 32 ms 33 ms wn-cisco-r5-lo-5.connections.net.nz [202.49.152.169]
3 34 ms 34 ms 33 ms wn-sum-1-wnlan7.connections.net.nz [202.49.152.165]
4 63 ms 34 ms 36 ms 192.168.100.37
5 72 ms 95 ms 73 ms p1-telstra-int-pri.connections.net.nz [192.100.53.45]
6 74 ms 70 ms 70 ms 203.167.233.10
7 204 ms 201 ms 205 ms unknown.net.reach.com [202.84.142.106]
8 201 ms 200 ms 194 ms i-0-5-1-0.paix-core01.bi.reach.com [202.84.140.90]
9 246 ms 194 ms 196 ms i-3-1.paix01.bi.reach.com [202.84.251.74]
10 210 ms 207 ms 214 ms paix.he.net [198.32.176.20]
11 * * * Request timed out.
12 * * * Request timed out.
13 * * * Request timed out.
14 * * * Request timed out.

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 33 ms 32 ms 33 ms wn-cisco-r5-lo-5.connections.net.nz [202.49.152.169]
3 34 ms 34 ms 33 ms wn-sum-1-wnlan7.connections.net.nz [202.49.152.161]
4 63 ms 34 ms 36 ms 192.168.100.33
5 72 ms 95 ms 73 ms p1-telstra-int-pri.connections.net.nz [192.100.53.45]
6 74 ms 70 ms 70 ms 203.167.233.10
7 204 ms 201 ms 205 ms unknown.net.reach.com [202.84.142.110]
8 201 ms 200 ms 194 ms i-0-5-1-0.paix-core01.bi.reach.com [202.84.143.62]
9 246 ms 194 ms 196 ms i-3-1.paix01.bi.reach.com [202.84.251.70]
10 210 ms 207 ms 214 ms paix.he.net [198.32.176.20]
11 * * * Request timed out.
12 * * * Request timed out.
13 * * * Request timed out.
14 * * * Request timed out.

C:\>tracert 208.68.240.20

Tracing route to boinc2.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 33 ms 32 ms 33 ms wn-cisco-r5-lo-5.connections.net.nz [202.49.152.169]
3 34 ms 34 ms 33 ms wn-sum-1-wnlan6.connections.net.nz [202.49.152.165]
4 63 ms 34 ms 36 ms 192.168.100.37
5 72 ms 95 ms 73 ms p1-telstra-int-pri.connections.net.nz [192.100.53.45]
6 74 ms 70 ms 70 ms 203.167.233.10
7 204 ms 201 ms 205 ms unknown.net.reach.com [202.84.142.114]
8 201 ms 200 ms 194 ms i-0-5-1-0.paix-core01.bi.reach.com [202.84.143.62]
9 246 ms 194 ms 196 ms i-3-1.paix01.bi.reach.com [202.84.251.74]
10 210 ms 207 ms 214 ms paix.he.net [198.32.176.20]
11 * * * Request timed out.
12 * * * Request timed out.
13 * * * Request timed out.
14 * * * Request timed out.

7. Or nslookups of the above four addresses?

C:\>nslookup 208.68.240.13
Server: ns1.actrix.co.nz
Address: 203.96.16.35

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

C:\>nslookup 208.68.240.16
Server: ns1.actrix.co.nz
Address: 203.96.16.35

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

C:\>nslookup 208.68.240.18
Server: ns1.actrix.co.nz
Address: 203.96.16.35

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

C:\>nslookup 208.68.240.20
Server: ns1.actrix.co.nz
Address: 203.96.16.35

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

Hope this helps resolve issues

---

I also have not been able to connect to setiboincdata,ssl.berkeley.edu since about 24th August.

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

2. When did you start having this problem?
on or about 24th August

3. What is your ISP?
xtra.co.nz

4. What is your geographic location?
New Zealand

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

In all 4 cases I get as follows

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),


6. How about traceroutes of the above four addresses?

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

1 1 ms 1 ms 27 ms "my router address"
2 30 ms 29 ms 29 ms 219-89-57-1.dialup.xtra.co.nz [219.89.57.1]
3 1206 ms 1416 ms 1340 ms mdr-fid-int.akbr5.global-gateway.net.nz [202.37.244.222]
4 31 ms 31 ms 31 ms ae4-10.akbr5.global-gateway.net.nz [202.37.244.221]
5 31 ms 31 ms 31 ms ae1-2.akbr4.global-gateway.net.nz [202.50.232.77]
6 31 ms 31 ms 39 ms ae1-10.tkbr9.global-gateway.net.nz [202.50.232.37]
7 130 ms 157 ms 157 ms so6-1-1.labr5.global-gateway.net.nz [122.56.127.62]
8 188 ms 186 ms 187 ms ae1-3.sjbr2.global-gateway.net.nz [203.96.120.94]
9 189 ms 189 ms 215 ms ae0.pabr4.global-gateway.net.nz [203.96.120.74]
10 193 ms 187 ms 189 ms paix.he.net [198.32.176.20]
11 * * * Request timed out.
12

The other addresses give the same result.

7. Or nslookups of the above four addresses?

C:\>nslookup 208.68.240.13
A message explaining that it cannot find a server name or domain for my router address followed by:
Name: boinc2.ssl.berkeley.edu
Address: 208.68.240.13

C:\>nslookup 208.68.240.16
A message explaining that it cannot find a server name or domain for my router address followed by:
Name: setiboincdata.ssl.berkeley.edu
Address: 208.68.240.16

C:\>nslookup 208.68.240.18
A message explaining that it cannot find a server name or domain for my router address followed by:
Name: setiboincdata.ssl.berkeley.edu
Address: 208.68.240.18

C:\>nslookup 208.68.240.20
A message explaining that it cannot find a server name or domain for my router address followed by:
Name: setiboincdata.ssl.berkeley.edu
Address: 208.68.240.20

---

8/29/2011 6:21:37 AM | SETI@home | Project has no tasks available

8/29/2011 6:21:37 AM | SETI@home | Project has no tasks available

Don't think that's connection related though...
Even IF there would be tasks available I couldn't download them without using a HTTP-proxy.

---

I got a couple of work units a couple of days ago but nothing since. Will work the other project WU till Seti comes back.

Hi!

I have two ADSL sites, one works and one does not. They belong to the same operator, Telia Sonera.

The setiathome home page, however, works from both sites!

Site #1 can successfully ping all addresses.
Site #2 cannot.

Last successfull contact was 22 Aug 2011 | 20:56:11 UTC.

Site #1 location is Kungsbacka, Sweden.
Site #2 location is Island of Oeland, Sweden.

Both sites use identical routers and ADSL modems.

nslookup are ok on both sites.

Trace from site #1: (working)

C:\Users\SM6GXQ>pathping 208.68.240.13

Spårar väg till boinc2.ssl.berkeley.edu [208.68.240.13]
över högst 30 hopp:
0 PeterW7 [192.168.1.3]
1 gw-n1fls303o838.telia.com [81.227.132.1]
2 81.224.217.252
3 kbn-b4.telia.net [80.91.253.130]
4 kbn-bb2-link.telia.net [80.91.254.220]
5 nyk-bb2-link.telia.net [80.91.254.91]
6 sjo-bb1-link.telia.net [80.91.254.177]
7 hurricane-113209-sjo-bb1.c.telia.net [213.248.86.54]
8 64.71.140.42
9 208.68.243.254
10 boinc2.ssl.berkeley.edu [208.68.240.13]

Statistik för 250 sekunder beräknas...
^C
C:\Users\SM6GXQ>pathping 208.68.240.16

Spårar väg till setiboincdata.ssl.berkeley.edu [208.68.240.16]
över högst 30 hopp:
0 PeterW7 [192.168.1.3]
1 gw-n1fls303o838.telia.com [81.227.132.1]
2 81.224.217.252
3 kbn-b3-link.telia.net [80.91.247.38]
4 kbn-bb2-link.telia.net [80.91.254.26]
5 nyk-bb2-link.telia.net [80.91.247.121]
6 sjo-bb1-link.telia.net [213.155.130.131]
7 hurricane-113209-sjo-bb1.c.telia.net [213.248.86.54]
8 64.71.140.42
9 208.68.243.254
10 setiboincdata.ssl.berkeley.edu [208.68.240.16]

Statistik för 250 sekunder beräknas...
^C
C:\Users\SM6GXQ>pathping 208.68.240.18

Spårar väg till boinc2.ssl.berkeley.edu [208.68.240.18]
över högst 30 hopp:
0 PeterW7 [192.168.1.3]
1 gw-n1fls303o838.telia.com [81.227.132.1]
2 81.224.217.252
3 kbn-b3-link.telia.net [80.91.247.38]
4 kbn-bb1-link.telia.net [213.248.65.9]
5 nyk-bb1-link.telia.net [80.91.249.21]
6 sjo-bb1-link.telia.net [213.155.130.129]
7 hurricane-113209-sjo-bb1.c.telia.net [213.248.86.54]
8 64.71.140.42
9 208.68.243.254
10 boinc2.ssl.berkeley.edu [208.68.240.18]

Statistik för 250 sekunder beräknas...
^C
C:\Users\SM6GXQ>pathping 208.68.240.20

Spårar väg till setiboinc.ssl.berkeley.edu [208.68.240.20]
över högst 30 hopp:
0 PeterW7 [192.168.1.3]
1 gw-n1fls303o838.telia.com [81.227.132.1]
2 81.224.217.252
3 kbn-b4-link.telia.net [80.91.253.90]
4 kbn-bb2-link.telia.net [80.91.254.220]
5 nyk-bb2-link.telia.net [213.248.64.34]
6 sjo-bb1-link.telia.net [80.91.254.177]
7 hurricane-113209-sjo-bb1.c.telia.net [213.248.86.54]
8 64.71.140.42
9 208.68.243.254
10 setiboinc.ssl.berkeley.edu [208.68.240.20]

Statistik för 250 sekunder beräknas...


....................................................


Trace from site #2: (not working)


C:\Users\sm7gxq>pathping 208.68.240.13

Spårar väg till boinc2.ssl.berkeley.edu [208.68.240.13]
över högst 30 hopp:
0 CPGP [192.168.0.2]
1 217.208.47.1
2 213.66.4.236
3 kbn-b4-link.telia.net [80.91.247.46]
4 kbn-bb1-link.telia.net [80.91.245.2]
5 nyk-bb1-link.telia.net [213.248.64.22]
6 sjo-bb1-link.telia.net [213.155.130.129]
7 hurricane-113209-sjo-bb1.c.telia.net [213.248.86.54]
8 * * *
Statistik för 175 sekunder beräknas...
^C
C:\Users\sm7gxq>pathping 208.68.240.16

Spårar väg till setiboincdata.ssl.berkeley.edu [208.68.240.16]
över högst 30 hopp:
0 CPGP [192.168.0.2]
1 217.208.47.1
2 213.66.4.236
3 kbn-b3-link.telia.net [80.91.253.82]
4 kbn-bb1-link.telia.net [80.91.246.252]
5 nyk-bb1-link.telia.net [80.91.247.115]
6 sjo-bb1-link.telia.net [80.91.252.153]
7 hurricane-113209-sjo-bb1.c.telia.net [213.248.86.54]
8 * * *
Statistik för 175 sekunder beräknas...
^C
C:\Users\sm7gxq>pathping 208.68.240.18

Spårar väg till boinc2.ssl.berkeley.edu [208.68.240.18]
över högst 30 hopp:
0 CPGP [192.168.0.2]
1 217.208.47.1
2 213.66.4.236
3 kbn-b4-link.telia.net [80.91.253.86]
4 kbn-bb1-link.telia.net [213.155.130.96]
5 nyk-bb1-link.telia.net [80.91.247.115]
6 sjo-bb1-link.telia.net [213.155.130.129]
7 hurricane-113209-sjo-bb1.c.telia.net [213.248.86.54]
8 * * *
Statistik för 175 sekunder beräknas...
^C
C:\Users\sm7gxq>pathping 208.68.240.20

Spårar väg till setiboinc.ssl.berkeley.edu [208.68.240.20]
över högst 30 hopp:
0 CPGP [192.168.0.2]
1 217.208.47.1
2 213.66.4.236
3 kbn-b4.telia.net [80.91.253.130]
4 kbn-bb2-link.telia.net [80.91.254.220]
5 nyk-bb2-link.telia.net [213.248.64.34]
6 sjo-bb1-link.telia.net [80.91.254.177]
7 hurricane-113209-sjo-bb1.c.telia.net [213.248.86.54]
8 * * *
Statistik för 175 sekunder beräknas...

............................

It seems the traffic stops at the Telia/Hurricane gateway.

rgds
Peter