Tracing route to setiathome.berkeley.edu [208.68.240.110]
Tracing route to setiathome.ssl.berkeley.edu [208.68.240.110]

Well, that looks like a DNS problem to me. Different servers, same IP address. You haven't been fiddling with a hosts file, have you?

Edit - or maybe not. I don't think "setiathome.ssl.berkeley.edu" (the second one) is a real server. Where did you get that name from?

I get the same IP address for both setiathome.berkeley.edu and setiathome.ssl.berkeley.edu. Both resolves to 208.68.240.110, and I haven't touched the hosts file on this computer.

Edit: http://setiathome.ssl.berkeley.edu/
http://setiathome.berkeley.edu/

OK, they must have registered the ...ssl... version as a spare, and parked it on the website server just in case. False alarm, forget I spoke.

But do remember that this website address - the one in your browser address bar, above this discussion - is not the one used by BOINC to upload, download, or report completed work. All three of those are different. So tracing the route to the message boards doesn't tell you anything more that what you can see on screen already - either you reach the website, or you don't.

closed boinc down and then restarted boinc straight after retried to send completed work units in and they went straight through and down loaded my cash to full again. the other pc wouldn't close down boinc so rebooted it and the same result all work sent in and cash filled up to max. les

same result here too, stop & restart Boinc and all tasks reported ok, though subsequent schedule requests failed with "can't connect to server"

Full reboot here on both machines yielded no help. Can still upload, but cannot report or get new work.
Tracert the same as before and as others.

---

I hate this silver badge. :((

---

With each crime and every kindness we birth our future.

I wonder if TCP Optimizer might help some of those who haven't been able to connect at all. As I recall, I set my machines up with that before the move to the co-lo and currently I'm at least getting intermittently successfully connections.

The thread Windows TCP Settings - Follow up - Help with server communication is where I originally got the info and settings for TCP Optimizer.

You mean the instructions for enabling TCP timestamps and window scaling, as provided for in RFC 1323?

No, they won't help. They smooth and accelerate the transfer of data - mainly for downloads - after you've connected. They don't help you connect in the first place.

Hey guys. I just wanted to report that something seems to be going wrong with the server because I cannot receive new tasks from seti@home nor can I send you the ones I finished. It's been like that for a while now.
I don't think the problem is from the boinc software because I have like a dozen other projects going on which work fine.
I restarted the program, restarted the pc but no luck.

http://i.imgur.com/FiEUBVV.png

But do remember that this website address - the one in your browser address bar, above this discussion - is not the one used by BOINC to upload, download, or report completed work. All three of those are different. So tracing the route to the message boards doesn't tell you anything more that what you can see on screen already - either you reach the website, or you don't.

Well, in that case:

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

1 <1 ms <1 ms <1 ms 192.168.1.1
2 6 ms 5 ms 5 ms 10.254.138.1
3 7 ms 6 ms 7 ms tb-rc0001-cr101-xe-0-3-4-0.core.as9143.net [213.51.186.180]
4 12 ms 9 ms 9 ms asd-tr0042-cr101-ae5-0.core.as9143.net [213.51.158.18]
5 11 ms 9 ms 11 ms lag-19.ear2.Amsterdam1.Level3.net [212.72.42.245]
6 155 ms 154 ms 155 ms ae-4-90.ear1.SanJose1.Level3.net [4.69.152.215]
7 155 ms 154 ms 155 ms ae-4-90.ear1.SanJose1.Level3.net [4.69.152.215]
8 192 ms 198 ms 198 ms CENIC.ear1.SanJose1.Level3.net [4.15.122.46]
9 198 ms 205 ms 204 ms dc-oak-agg4--svl-agg4-100ge.cenic.net [137.164.46.144]
10 202 ms 201 ms 202 ms ucb--oak-agg4-10g.cenic.net [137.164.50.31]
11 172 ms 173 ms 171 ms t2-3.inr-201-sut.Berkeley.EDU [128.32.0.37]
12 208 ms 206 ms 211 ms et3-48.inr-311-ewdc.Berkeley.EDU [128.32.0.101]
13 et3-48.inr-311-ewdc.Berkeley.EDU [128.32.0.101] reports: Destination host unreachable.

Trace complete.

---

Agreed, something not working right....

---

I wonder if TCP Optimizer might help some of those who haven't been able to connect at all. As I recall, I set my machines up with that before the move to the co-lo and currently I'm at least getting intermittently successfully connections.

The thread Windows TCP Settings - Follow up - Help with server communication is where I originally got the info and settings for TCP Optimizer.

You mean the instructions for enabling TCP timestamps and window scaling, as provided for in RFC 1323?

No, they won't help. They smooth and accelerate the transfer of data - mainly for downloads - after you've connected. They don't help you connect in the first place.

Well, as I recall, there was more to it that just the RFC 1323. If you let TCP Optimizer do its thing, it also may adjust the MTU size and a few other things. I'm just bringing it up because it seems strange that some users can't successfully connect at all, while others, like me, are having at least some success. So, I was wondering if optimized TCP settings might have some bearing on that success rate.

EDIT: Changed the link to force it, hopefully, to the beginning of that thread.

---

Tracing route to synergy.ssl.berkeley.edu [208.68.240.126]

Oh my, is it that easy? The servers can be traced based upon their name! Just stick .ssl.berkeley.edu to the end. That's easier than figuring out what their IP address is through a <sched_debug> flag.

---

I hate this silver badge. :((

Then get off your A**, and fix the new GPU, dear Mike :-)

Certainly not my friend.

---

With each crime and every kindness we birth our future.

But do remember that this website address - the one in your browser address bar, above this discussion - is not the one used by BOINC to upload, download, or report completed work. All three of those are different. So tracing the route to the message boards doesn't tell you anything more that what you can see on screen already - either you reach the website, or you don't.

Well, in that case:

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

1 <1 ms <1 ms <1 ms 192.168.1.1
2 6 ms 5 ms 5 ms 10.254.138.1
3 7 ms 6 ms 7 ms tb-rc0001-cr101-xe-0-3-4-0.core.as9143.net [213.51.186.180]
4 12 ms 9 ms 9 ms asd-tr0042-cr101-ae5-0.core.as9143.net [213.51.158.18]
5 11 ms 9 ms 11 ms lag-19.ear2.Amsterdam1.Level3.net [212.72.42.245]
6 155 ms 154 ms 155 ms ae-4-90.ear1.SanJose1.Level3.net [4.69.152.215]
7 155 ms 154 ms 155 ms ae-4-90.ear1.SanJose1.Level3.net [4.69.152.215]
8 192 ms 198 ms 198 ms CENIC.ear1.SanJose1.Level3.net [4.15.122.46]
9 198 ms 205 ms 204 ms dc-oak-agg4--svl-agg4-100ge.cenic.net [137.164.46.144]
10 202 ms 201 ms 202 ms ucb--oak-agg4-10g.cenic.net [137.164.50.31]
11 172 ms 173 ms 171 ms t2-3.inr-201-sut.Berkeley.EDU [128.32.0.37]
12 208 ms 206 ms 211 ms et3-48.inr-311-ewdc.Berkeley.EDU [128.32.0.101]
13 et3-48.inr-311-ewdc.Berkeley.EDU [128.32.0.101] reports: Destination host unreachable.

Trace complete.

Mine seems to be connecting;

traceroute to synergy.ssl.berkeley.edu (208.68.240.126), 64 hops max, 72 byte packets

 1  192.168.1.1 (192.168.1.1)  1.196 ms  0.646 ms  0.686 ms
 2  l100.tampfl-vfttp-76.verizon-gni.net (96.254.233.1)  7.711 ms  6.700 ms  7.977 ms
 3  g0-5-5-0.tampfl-lcr-22.verizon-gni.net (130.81.110.228)  12.235 ms  12.016 ms  12.889 ms
 4  * * *
 5  0.ae4.br1.mia19.alter.net (140.222.225.113)  17.624 ms  16.546 ms  17.973 ms
 6  lag-10.ear2.miami2.level3.net (4.68.71.169)  16.953 ms  17.545 ms  17.245 ms
 7  ae-31-51.ebr1.miami1.level3.net (4.69.138.91)  69.712 ms  69.655 ms  69.640 ms
 8  ae-2-2.ebr1.dallas1.level3.net (4.69.140.133)  70.492 ms  69.189 ms  70.187 ms
 9  ae-71-71.csw2.dallas1.level3.net (4.69.151.137)  67.432 ms  70.041 ms  69.654 ms
10  ae-73-73.ebr3.dallas1.level3.net (4.69.151.146)  70.198 ms  69.233 ms  70.177 ms
11  ae-3-3.ebr2.losangeles1.level3.net (4.69.132.77)  69.913 ms  69.731 ms  69.722 ms
12  ae-82-82.csw3.losangeles1.level3.net (4.69.137.26)  70.151 ms  69.363 ms  70.057 ms
13  * * *
14  cenic.ear1.losangeles1.level3.net (4.35.156.66)  70.261 ms  69.162 ms  70.457 ms
15  dc-svl-agg4--lax-agg6-100ge.cenic.net (137.164.11.1)  77.146 ms  76.815 ms  77.960 ms
16  dc-oak-agg4--svl-agg4-100ge.cenic.net (137.164.46.144)  79.872 ms  76.818 ms  79.945 ms
17  ucb--oak-agg4-10g.cenic.net (137.164.50.31)  79.880 ms  79.596 ms  79.809 ms
18  t2-3.inr-202-reccev.berkeley.edu (128.32.0.39)  80.130 ms  79.473 ms  79.883 ms
19  et3-47.inr-311-ewdc.berkeley.edu (128.32.0.103)  79.960 ms  78.861 ms  80.162 ms
20  et3-47.inr-311-ewdc.berkeley.edu (128.32.0.103)  552.653 ms !H *  1092.686 ms !H

Of course, anything trying to get through e3-47.inr-310-ewdc.berkeley.edu (128.32.0.99) gets stuck...

traceroute to georgem.ssl.berkeley.edu (208.68.240.119), 64 hops max, 72 byte packets
 1  192.168.1.1 (192.168.1.1)  0.951 ms  0.708 ms  0.628 ms
 2  l100.tampfl-vfttp-76.verizon-gni.net (96.254.233.1)  7.882 ms  7.109 ms  7.211 ms
 3  g0-5-5-0.tampfl-lcr-21.verizon-gni.net (130.81.109.254)  19.938 ms  9.178 ms  10.268 ms
 4  * * *
 5  0.ae3.br1.mia19.alter.net (140.222.225.111)  18.454 ms  16.160 ms  19.890 ms
 6  lag-10.ear2.miami2.level3.net (4.68.71.169)  20.245 ms  19.688 ms  19.960 ms
 7  ae-31-51.ebr1.miami1.level3.net (4.69.138.91)  69.785 ms  69.710 ms  69.686 ms
 8  ae-2-2.ebr1.dallas1.level3.net (4.69.140.133)  73.699 ms  68.940 ms  70.357 ms
 9  ae-91-91.csw4.dallas1.level3.net (4.69.151.161)  70.221 ms  70.758 ms  70.137 ms
10  ae-93-93.ebr3.dallas1.level3.net (4.69.151.170)  69.980 ms  69.542 ms  69.664 ms
11  ae-3-3.ebr2.losangeles1.level3.net (4.69.132.77)  70.199 ms  72.246 ms  70.183 ms
12  ae-72-72.csw2.losangeles1.level3.net (4.69.137.22)  71.892 ms  73.291 ms  69.115 ms
13  * ae-2-70.ear1.losangeles1.level3.net (4.69.144.82)  68.848 ms  70.403 ms
14  cenic.ear1.losangeles1.level3.net (4.35.156.66)  69.179 ms  72.375 ms  72.429 ms
15  dc-svl-agg4--lax-agg6-100ge.cenic.net (137.164.11.1)  80.211 ms  79.463 ms  79.177 ms
16  dc-oak-agg4--svl-agg4-100ge.cenic.net (137.164.46.144)  79.884 ms  79.767 ms  79.962 ms
17  ucb--oak-agg4-10g.cenic.net (137.164.50.31)  82.661 ms  79.562 ms  79.979 ms
18  t2-3.inr-202-reccev.berkeley.edu (128.32.0.39)  79.628 ms  79.443 ms  79.875 ms
19  e3-47.inr-310-ewdc.berkeley.edu (128.32.0.99)  80.160 ms  79.544 ms  79.931 ms
20  * * *
21  * * *
22  *

*shrugs*

But do remember that this website address - the one in your browser address bar, above this discussion - is not the one used by BOINC to upload, download, or report completed work. All three of those are different. So tracing the route to the message boards doesn't tell you anything more that what you can see on screen already - either you reach the website, or you don't.

Well, in that case:

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

1 <1 ms <1 ms <1 ms 192.168.1.1
2 6 ms 5 ms 5 ms 10.254.138.1
3 7 ms 6 ms 7 ms tb-rc0001-cr101-xe-0-3-4-0.core.as9143.net [213.51.186.180]
4 12 ms 9 ms 9 ms asd-tr0042-cr101-ae5-0.core.as9143.net [213.51.158.18]
5 11 ms 9 ms 11 ms lag-19.ear2.Amsterdam1.Level3.net [212.72.42.245]
6 155 ms 154 ms 155 ms ae-4-90.ear1.SanJose1.Level3.net [4.69.152.215]
7 155 ms 154 ms 155 ms ae-4-90.ear1.SanJose1.Level3.net [4.69.152.215]
8 192 ms 198 ms 198 ms CENIC.ear1.SanJose1.Level3.net [4.15.122.46]
9 198 ms 205 ms 204 ms dc-oak-agg4--svl-agg4-100ge.cenic.net [137.164.46.144]
10 202 ms 201 ms 202 ms ucb--oak-agg4-10g.cenic.net [137.164.50.31]
11 172 ms 173 ms 171 ms t2-3.inr-201-sut.Berkeley.EDU [128.32.0.37]
12 208 ms 206 ms 211 ms et3-48.inr-311-ewdc.Berkeley.EDU [128.32.0.101]
13 et3-48.inr-311-ewdc.Berkeley.EDU [128.32.0.101] reports: Destination host unreachable.

Trace complete.

Likewise. I've now got a laptop in front of me with four separate tracert consoles open, each chugging away towards one of the four servers.

Upload, download, and website all route through inr-310 and reach their (mostly stealthed) destination - only the website server is friendly enough to introduce itself (hello, muarae1).

The scheduler is still trying to route through inr-311, and is unreachable via tracert - though in practical use, about half my scheduler requests seem to actually make it.

12 208 ms 206 ms 211 ms et3-48.inr-311-ewdc.Berkeley.EDU [128.32.0.101]
13 et3-48.inr-311-ewdc.Berkeley.EDU [128.32.0.101] reports: Destination host unreachable.

Mine seems to be connecting;

19 et3-47.inr-311-ewdc.berkeley.edu (128.32.0.103) 79.960 ms 78.861 ms 80.162 ms
20 et3-47.inr-311-ewdc.berkeley.edu (128.32.0.103) 552.653 ms !H * 1092.686 ms !H

To/through different servers.

t2-3.inr-202-reccev.berkeley.edu (128.32.0.39) for you, which seems to work.
t2-3.inr-201-sut.Berkeley.EDU [128.32.0.37] for me, which seems to point to a dead end.

et3-47 (128.32.0.103) for you,
et3-48 (128.32.0.101) for me.

---

I hate this silver badge. :((

Then get off your A**, and fix the new GPU, dear Mike :-)

Certainly not my friend.

Fine, have it your way.

I guess i missunderstood.
I´m trying but with my new 380.

---

With each crime and every kindness we birth our future.

et3-47 (128.32.0.103) for you,
et3-48 (128.32.0.101) for me.

I *think* those are simply two separate incoming interfaces into the same (inr-311) router.

I think it matters where we come from before that time. t2-3.inr-201 or t2-3.inr-202 seems to decide if we're going to e(t)3-47 or e(t)3-48

And I see everyone with 202 and 47 getting through and everyone with 201 and 48 getting stuck. Same route to the BOINC forums, for me also through t2-3.inr-201-sut.Berkeley.EDU and getting stuck in et3-48.inr-311-ewdc.Berkeley.EDU

Isn't there a way to re-route through another node into Berkeley?

Edit:
Yes... Campus Topology PDF shows the two servers I pointed out to be core routers.

---

What is the DNS address used for reporting wus?

If you put 208.68.240.110 into the web address bar you get the seti home page and 208.68.240.126 goes to apache test page. Tracert pings are not accepted by these addresses maybe to stop dos attacks?

---

Everything worked fine up to 7:00AM PDT, then at 7:15AM PDT I started to get the Couldn't connect to server message, and it's been that way since.

Richard, you are probably right about the trace of setiathome.berkeley.edu. I can reach all of the web pages.

I don't know the IP address of the Scheduler, so I tried the trace that Ageless did of synergy.ssl.berkeley.edu and received this:

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

11 76 ms 75 ms 75 ms calren-cenic.paix.net [198.32.176.33]
12 77 ms 77 ms 77 ms dc-oak-agg4--paix-px1-ge.cenic.net [137.164.47.1
9]
13 78 ms 77 ms 78 ms ucb--oak-agg4-10g.cenic.net [137.164.50.31]
14 79 ms 78 ms 78 ms t2-3.inr-201-sut.Berkeley.EDU [128.32.0.37]
15 78 ms 78 ms 78 ms et3-48.inr-311-ewdc.Berkeley.EDU [128.32.0.101]

16 * et3-48.inr-311-ewdc.Berkeley.EDU [128.32.0.101] reports: Destinat
ion host unreachable.

I don't know why I can't connect to the Scheduler, but it's not because of anything that I did.

Bruce

---

Bruce

What is the DNS address used for reporting wus?

setiboinc.ssl.berkeley.edu

The full scheduler url is

http://setiboinc.ssl.berkeley.edu/sah_cgi/cgi

If you put that into a browser address bar, you get (as would be expected)

<scheduler_reply>
<scheduler_version>707</scheduler_version>
<master_url>http://setiathome.berkeley.edu/</master_url>
<request_delay>303.000000</request_delay>
<message priority="low">Error in request message: xp.get_tag() failed</message>
<project_name>SETI@home</project_name>
</scheduler_reply>

Strange you can get to muarae1 through e3-47.inr-310-ewdc.berkeley.edu (128.32.0.99) but not the others;

traceroute to muarae1.ssl.berkeley.edu (208.68.240.110), 64 hops max, 72 byte packets
 1  192.168.1.1 (192.168.1.1)  1.196 ms  1.055 ms  0.499 ms
 2  l100.tampfl-vfttp-76.verizon-gni.net (96.254.233.1)  8.062 ms  7.292 ms  7.233 ms
 3  g0-5-5-0.tampfl-lcr-22.verizon-gni.net (130.81.110.228)  22.944 ms  22.955 ms  17.657 ms
 4  * * *
 5  0.ae4.br1.mia19.alter.net (140.222.225.113)  18.191 ms  17.348 ms  17.465 ms
 6  lag-10.ear2.miami2.level3.net (4.68.71.169)  1487.560 ms  2797.003 ms *
 7  ae-31-51.ebr1.miami1.level3.net (4.69.138.91)  68.938 ms  69.456 ms  70.443 ms
 8  ae-2-2.ebr1.dallas1.level3.net (4.69.140.133)  69.647 ms  69.677 ms  69.685 ms
 9  ae-61-61.csw1.dallas1.level3.net (4.69.151.125)  70.185 ms  69.340 ms  70.421 ms
10  ae-63-63.ebr3.dallas1.level3.net (4.69.151.134)  69.674 ms  69.765 ms  69.666 ms
11  ae-3-3.ebr2.losangeles1.level3.net (4.69.132.77)  70.202 ms  68.913 ms  70.406 ms
12  ae-62-62.csw1.losangeles1.level3.net (4.69.137.18)  71.915 ms  71.892 ms  70.659 ms
13  ae-1-60.ear1.losangeles1.level3.net (4.69.144.18)  69.400 ms  70.311 ms  69.195 ms
14  cenic.ear1.losangeles1.level3.net (4.35.156.66)  70.654 ms  68.771 ms  70.712 ms
15  dc-svl-agg4--lax-agg6-100ge.cenic.net (137.164.11.1)  76.889 ms  77.594 ms  79.917 ms
16  dc-oak-agg4--svl-agg4-100ge.cenic.net (137.164.46.144)  79.918 ms  79.437 ms  80.211 ms
17  ucb--oak-agg4-10g.cenic.net (137.164.50.31)  79.904 ms  79.574 ms  79.950 ms
18  t2-3.inr-202-reccev.berkeley.edu (128.32.0.39)  79.855 ms  79.725 ms  87.204 ms
19  e3-47.inr-310-ewdc.berkeley.edu (128.32.0.99)  80.117 ms  79.545 ms  79.908 ms
20  muarae1.ssl.berkeley.edu (208.68.240.110)  79.885 ms  79.599 ms  79.880 ms

traceroute to bruno.ssl.berkeley.edu (208.68.240.118), 64 hops max, 72 byte packets
 1  192.168.1.1 (192.168.1.1)  1.581 ms  0.440 ms  0.463 ms
 2  l100.tampfl-vfttp-76.verizon-gni.net (96.254.233.1)  5.764 ms  7.884 ms  6.716 ms
 3  g0-5-5-0.tampfl-lcr-22.verizon-gni.net (130.81.110.228)  10.415 ms  11.542 ms  10.439 ms
 4  * * *
 5  0.ae4.br1.mia19.alter.net (140.222.225.113)  17.617 ms  17.352 ms  17.786 ms
 6  lag-10.ear2.miami2.level3.net (4.68.71.169)  17.948 ms  16.416 ms  17.557 ms
 7  ae-31-51.ebr1.miami1.level3.net (4.69.138.91)  69.583 ms  69.713 ms  69.670 ms
 8  ae-2-2.ebr1.dallas1.level3.net (4.69.140.133)  70.426 ms  69.328 ms  70.147 ms
 9  ae-71-71.csw2.dallas1.level3.net (4.69.151.137)  69.671 ms  69.537 ms  69.941 ms
10  ae-73-73.ebr3.dallas1.level3.net (4.69.151.146)  70.182 ms  69.148 ms  70.214 ms
11  ae-3-3.ebr2.losangeles1.level3.net (4.69.132.77)  69.647 ms  70.095 ms  69.669 ms
12  ae-72-72.csw2.losangeles1.level3.net (4.69.137.22)  70.214 ms  71.792 ms  70.417 ms
13  * * *
14  cenic.ear1.losangeles1.level3.net (4.35.156.66)  72.035 ms  69.384 ms  70.304 ms
15  dc-svl-agg4--lax-agg6-100ge.cenic.net (137.164.11.1)  77.151 ms  76.800 ms  77.902 ms
16  dc-oak-agg4--svl-agg4-100ge.cenic.net (137.164.46.144)  79.932 ms  79.483 ms  79.883 ms
17  ucb--oak-agg4-10g.cenic.net (137.164.50.31)  80.165 ms  79.490 ms  79.888 ms
18  t2-3.inr-202-reccev.berkeley.edu (128.32.0.39)  79.869 ms  79.519 ms  80.138 ms
19  e3-47.inr-310-ewdc.berkeley.edu (128.32.0.99)  80.030 ms  79.199 ms  79.898 ms
20  * * *
21  * * *
22  * * *