@ 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.

WOW, my machine can reach again the S@h server without a proxy.
Also I can see again the test pages in my browser if I click to the upper mentioned server URLs.

I hope this isn't only a temporary event.. ;-)

It would be nice if the S@h router problem is solved for everyone..


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

---

Just wanted to add another vote of thanks from here in NZ for those who (I presume) fixed the router problem. (And let us hope it stays fixed this time).

After a week or so of only being able to connect via a proxy server, currently I can connect (fast) directly to upload my results.

Thanks again.

Martin.

---

Yeah! This morning my computer have started to upload and report my workunits. Someone has done a wery good job to fix the problem, thanks!
/Per

---

I can connect again and have uploaded my outstanding work units.

Many thanks

---

Uploads and scheduler started to work here again, too. Many thanks.

---

Just wanted to add that the connection problem is Ok for my system #2 that didn't work before.

C:\Users\sm7gxq>pathping setiboinc.ssl.berkeley.edu

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 64.71.140.42
9 208.68.243.254
10 setiboinc.ssl.berkeley.edu [208.68.240.20]

No packet loss at all!

Looking forward to be able to crunch more SETI work, since this was the main reason why I joined BOINC at the beginning.

I have set project priority to max for SETI, but still other projects like Primegrid get more work (at least more credits).

I have two other machines that only crunch SETI, and they are now set to buffer several days of work.

I really want to help you guys :-)

rgds
Peter

---

1.

H:\>ping anakin.ssl.berkeley.edu

Pinging anakin.ssl.berkeley.edu [128.32.18.168] with 32 bytes of data:

Request timed out.
Reply from 128.32.18.168: bytes=32 time=42ms TTL=52
Reply from 128.32.18.168: bytes=32 time=45ms TTL=52
Reply from 128.32.18.168: bytes=32 time=45ms TTL=52

Ping statistics for 128.32.18.168:
Packets: Sent = 4, Received = 3, Lost = 1 (25% loss),
Approximate round trip times in milli-seconds:
Minimum = 42ms, Maximum = 45ms, Average = 44ms

H:\>ping vader.ssl.berkeley.edu

Pinging vader.ssl.berkeley.edu [128.32.18.154] with 32 bytes of data:

Reply from 128.32.18.154: bytes=32 time=51ms TTL=52
Reply from 128.32.18.154: bytes=32 time=65ms TTL=52
Reply from 128.32.18.154: bytes=32 time=54ms TTL=52
Reply from 128.32.18.154: bytes=32 time=75ms TTL=52

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

H:\>ping bruno.ssl.berkeley.edu

Pinging bruno.ssl.berkeley.edu [128.32.18.138] with 32 bytes of data:

Request timed out.
Request timed out.
Request timed out.
Request timed out.

Ping statistics for 128.32.18.138:
Packets: Sent = 4, Received = 0, Lost = 4 (100% loss),

Bruno seems unreachable.

2. On or about 8-19-2011


3. UC Davis

4. Sacramento UCDHS campus

5.

H:\>ping 208.68.240.13

Pinging 208.68.240.13 with 32 bytes of data:

Reply from 208.68.240.13: bytes=32 time=58ms TTL=52
Request timed out.
Reply from 208.68.240.13: bytes=32 time=49ms TTL=52
Reply from 208.68.240.13: bytes=32 time=69ms TTL=52

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

H:\>ping 208.68.240.16

Pinging 208.68.240.16 with 32 bytes of data:

Reply from 208.68.240.16: bytes=32 time=47ms TTL=52
Reply from 208.68.240.16: bytes=32 time=44ms TTL=52
Reply from 208.68.240.16: bytes=32 time=46ms TTL=52
Reply from 208.68.240.16: bytes=32 time=48ms TTL=52

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

H:\>ping 208.68.240.18

Pinging 208.68.240.18 with 32 bytes of data:

Request timed out.
Reply from 208.68.240.18: bytes=32 time=47ms TTL=52
Reply from 208.68.240.18: bytes=32 time=47ms TTL=52
Reply from 208.68.240.18: bytes=32 time=47ms TTL=52

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

H:\>ping 208.68.240.20

Pinging 208.68.240.20 with 32 bytes of data:

Reply from 208.68.240.20: bytes=32 time=46ms TTL=52
Reply from 208.68.240.20: bytes=32 time=46ms TTL=52
Reply from 208.68.240.20: bytes=32 time=47ms TTL=52
Reply from 208.68.240.20: bytes=32 time=47ms TTL=52

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

6.
H:\>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 152.79.109.253
2 <1 ms <1 ms <1 ms sesp-0p715-cc-a-Te1-9.ucdmc.ucdavis.edu [10.252.1.101]
3 <1 ms <1 ms <1 ms primary-Gi9-11.ucdmc.ucdavis.edu [10.252.1.250]
4 <1 ms <1 ms <1 ms ucdmc-primary--border-ucdmc.ucdavis.edu [192.82.111.57]
5 1 ms 1 ms 1 ms sac-dc1--ucdmc-ge.cenic.net [137.164.23.73]
6 3 ms 3 ms 3 ms dc-oak-core1--sac-dc1-10g.cenic.net [137.164.47.22]
7 5 ms 4 ms 4 ms dc-svl-core1--oak-core1-10ge-2.cenic.net [137.164.46.28]
8 4 ms 4 ms 4 ms dc-svl-px1--svl-core1-10ge-3.cenic.net [137.164.46.15]
9 5 ms 5 ms 5 ms 137.164.131.61
10 5 ms 11 ms 5 ms 137.164.130.58
11 5 ms 5 ms 5 ms 64.71.140.42
12 47 ms 47 ms 46 ms 208.68.243.254
13 62 ms 53 ms * boinc2.ssl.berkeley.edu [208.68.240.13]
14 49 ms * 47 ms boinc2.ssl.berkeley.edu [208.68.240.13]

Trace complete.

H:\>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 152.79.109.253
2 <1 ms <1 ms <1 ms asb-1310-cc-a-Te1-9.ucdmc.ucdavis.edu [10.252.1.93]
3 <1 ms <1 ms <1 ms primary-Gi7-11.ucdmc.ucdavis.edu [10.252.1.242]
4 <1 ms <1 ms 9 ms ucdmc-primary--border-ucdmc.ucdavis.edu [192.82.111.57]
5 1 ms 1 ms 1 ms sac-dc1--ucdmc-ge.cenic.net [137.164.23.73]
6 3 ms 3 ms 3 ms dc-oak-core1--sac-dc1-10g.cenic.net [137.164.47.22]
7 5 ms 5 ms 4 ms dc-svl-core1--oak-core1-10ge-1.cenic.net [137.164.46.98]
8 4 ms 4 ms 4 ms dc-svl-px1--svl-core1-10ge-2.cenic.net [137.164.46.13]
9 5 ms 5 ms 5 ms 137.164.131.61
10 5 ms 5 ms 13 ms 137.164.130.58
11 5 ms 5 ms 5 ms 64.71.140.42
12 46 ms 47 ms 48 ms 208.68.243.254
13 47 ms 47 ms 47 ms setiboincdata.ssl.berkeley.edu [208.68.240.16]

Trace complete.

H:\>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 152.79.109.253
2 <1 ms <1 ms <1 ms asb-1310-cc-a-Te1-9.ucdmc.ucdavis.edu [10.252.1.93]
3 <1 ms <1 ms <1 ms primary-Gi7-11.ucdmc.ucdavis.edu [10.252.1.242]
4 <1 ms <1 ms <1 ms ucdmc-primary--border-ucdmc.ucdavis.edu [192.82.111.57]
5 1 ms 1 ms 1 ms sac-dc1--ucdmc-ge.cenic.net [137.164.23.73]
6 4 ms 3 ms 3 ms dc-oak-core1--sac-dc1-10g.cenic.net [137.164.47.22]
7 5 ms 4 ms 5 ms dc-svl-core1--oak-core1-10ge-1.cenic.net [137.164.46.100]
8 4 ms 4 ms 4 ms dc-svl-px1--svl-core1-10ge-2.cenic.net [137.164.46.13]
9 5 ms 5 ms 5 ms 137.164.131.61
10 5 ms 5 ms 11 ms 137.164.130.58
11 5 ms 5 ms 5 ms 64.71.140.42
12 48 ms 48 ms * 208.68.243.254
13 47 ms * 47 ms boinc2.ssl.berkeley.edu [208.68.240.18]

Trace complete.

H:\>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 152.79.109.253
2 <1 ms <1 ms <1 ms sesp-0p715-cc-a-Te1-9.ucdmc.ucdavis.edu [10.252.1.101]
3 <1 ms <1 ms <1 ms primary-Gi9-11.ucdmc.ucdavis.edu [10.252.1.250]
4 <1 ms <1 ms <1 ms ucdmc-primary--border-ucdmc.ucdavis.edu [192.82.111.57]
5 1 ms 1 ms 1 ms sac-dc1--ucdmc-ge.cenic.net [137.164.23.73]
6 3 ms 3 ms 3 ms dc-oak-core1--sac-dc1-10g.cenic.net [137.164.47.22]
7 8 ms 5 ms 4 ms dc-svl-core1--oak-core1-10ge-1.cenic.net [137.164.46.98]
8 4 ms 4 ms 4 ms dc-svl-px1--svl-core1-10ge-1.cenic.net [137.164.46.205]
9 5 ms 5 ms 5 ms 137.164.131.61
10 5 ms 14 ms 5 ms 137.164.130.58
11 5 ms 5 ms 5 ms 64.71.140.42
12 * * 48 ms 208.68.243.254
13 46 ms 46 ms 47 ms setiboinc.ssl.berkeley.edu [208.68.240.20]

Trace complete.

7.

H:\>nslookup 208.68.240.13
Server: aslan.ucdmc.ucdavis.edu
Address: 152.79.105.105

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


H:\>nslookup 208.68.240.16
Server: aslan.ucdmc.ucdavis.edu
Address: 152.79.105.105

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


H:\>nslookup 208.68.240.18
Server: aslan.ucdmc.ucdavis.edu
Address: 152.79.105.105

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


H:\>nslookup 208.68.240.20
Server: aslan.ucdmc.ucdavis.edu
Address: 152.79.105.105

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


--Jim

Just got back home and took my machines off the proxy.

All looks good here, uploads and downloads going through ok. I've gotten the best ping times through to the 4 SAH servers that I've had for sometime and download speeds have doubled despite the current log jam.

Thanks to all concerned for providing the Fix.

T.A.

The uploadserver seems to be down since yesterday.

---

ET? It's me!

Even though it says it is up!!!!!! :((

The current upload issues are a global problem, something within the server farm locked up during the night. See this thread: http://setiathome.berkeley.edu/forum_thread.php?id=65480&nowrap=true#1153740

---

Even though it says it is up!!!!!! :((

You have to remember to look at the time stamp on the server status page when viewing it.....
It's not been updated for about 13 hours now, so you can pretty much assume anything shown there is not valid information.

---

"Freedom is just Chaos, with better lighting." Alan Dean Foster

Yep, I am a newbe and I am not sure if this is the right place to post about the upload / download problems Seti@Home seems to always have. I would like to have my system but more then not there seems to be no way to get or send finished work. I guess that is why there is a Milkyway project. Any help to receive more work from Seti would be great of if I can be directed to the correct place to post would be great. Thanks, Scott

---

Well there ya have it...nothing happening atm....

9/20/2011 6:46:39 PM | SETI@home | Requesting new tasks for CPU and ATI GPU
9/20/2011 6:47:01 PM | SETI@home | Scheduler request failed: Couldn't connect to server
9/20/2011 6:47:04 PM | | Project communication failed: attempting access to reference site
9/20/2011 6:47:05 PM | | Internet access OK - project servers may be temporarily down.
9/20/2011 6:50:49 PM | SETI@home | Sending scheduler request: To fetch work.
9/20/2011 6:50:49 PM | SETI@home | Requesting new tasks for ATI GPU
9/20/2011 6:50:59 PM | SETI@home | Scheduler request completed: got 0 new tasks
9/20/2011 6:50:59 PM | SETI@home | Project has no tasks available
9/20/2011 6:52:12 PM | SETI@home | update requested by user
9/20/2011 6:52:15 PM | SETI@home | Sending scheduler request: Requested by user.
9/20/2011 6:52:15 PM | SETI@home | Requesting new tasks for CPU and ATI GPU
9/20/2011 6:52:17 PM | SETI@home | Scheduler request completed: got 0 new tasks
9/20/2011 6:52:17 PM | SETI@home | Project has no tasks available
9/20/2011 6:52:29 PM | SETI@home | update requested by user
9/20/2011 6:52:33 PM | SETI@home | Sending scheduler request: Requested by user.
9/20/2011 6:52:33 PM | SETI@home | Requesting new tasks for CPU and ATI GPU
9/20/2011 6:52:35 PM | SETI@home | Scheduler request completed: got 0 new tasks
9/20/2011 6:52:35 PM | SETI@home | Project has no tasks available

And what would that have to do with Hurricane Electric connection problems?

Obviously, your host can reach the servers very well!

Gruß,
Gundolf

Wonderful way to greet a new cruncher. If I had just started up I would have promptly removed Boinc from my computer after reading that curt reply.

@ David Gentry.............

Thanks for including the startup messages. Most new users don't know that. The messages indicate that you are contacting the servers properly but just as all of us are seeing, no work to send out from the servers. (The Hurricane connection problem is hopefully solved)

Keep on trying, someday perhaps they will get it going again. Welcome to Boinc/Seti.

---

Boinc....Boinc....Boinc....Boinc....

I don't know if May 2nd, 2000 qualifies as a "new user" even if it is his first post.

Barely more than 5k credits does!

---

Boinc....Boinc....Boinc....Boinc....

At a 398 RAC, not really.

Not really a "newbie". I had 48,812 hours on the Classic S@H, but I don't know how to get any credits back for that era. I just started back toying with the thing recently. I was happy to see the GPU options available now, but I've only had one or two of those files to show up.

I was an engineer with Alabama Power for 23 years. Moved to Boise Idaho in '97 and then worked with Idaho Power for a while. So my earlier "crunching" days were primarily during that period of time I was in Idaho. Back in Alabama now and just getting back into it again. Looks like it's a challenge to keep the work flow going from the server-side these days.

I hope all of this can move humanity towards a definitive answer to that timeless question.. "Are we alone?"

thanks for the comments people.