Let hope that the recent upload server problems go away soon.

---

There's a problem with the upload server?? :-)

---

PROUD MEMBER OF Team Starfire World BOINC

Only for those of us with Fermi cards!! :)

---

Only for those of us with Fermi cards!! :)

Good to go on my end for uploads. Not getting a single download though.

---

Executive Director GPU Users Group Inc. -
brad@gpuug.org

Only for those of us with Fermi cards!! :)

Good to go on my end for uploads. Not getting a single download though.

Shyly glances around and wonders where all these downloads are coming from. :-)

---

PROUD MEMBER OF Team Starfire World BOINC

Only for those of us with Fermi cards!! :)

I just uploaded.. :)

Seems to be a shortage of work at the moment. Splitters don't seem to be cranking up the pace at all to build up the Ready to Send buffer, they're barely keeping up with present demand.

---

Grant
Darwin NT

Hmm, the upload server and the Server Status Page, forgot to lock up at 07:00 UTC today.

Now that's strange, and highly disturbing :-)

Maybe it'll be another 23:50 UTC job this time. ;)

Cheers.

---

I guess switching off Jocelyn helped in some way.

---

With each crime and every kindness we birth our future.

I've still not been able to upload and some of my stuff starts timing out on the 25th. :((

---

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

I've still not been able to upload and some of my stuff starts timing out on the 25th. :((

May be a problem at your end. Try rebooting your computer & modem/router.
I've been able to upload OK since the last outage, the problem now is the lack of available work.

---

Grant
Darwin NT

I've still not been able to upload and some of my stuff starts timing out on the 25th. :((

Uploads are definitely working now. Must be some networking/firewall problem at your end. If everything else fails, try connecting through some http proxy (Advanced/Options... in BOINC Manager).

---

I've still not been able to upload and some of my stuff starts timing out on the 25th. :((

Uploads are definitely working now. Must be some networking/firewall problem at your end. If everything else fails, try connecting through some http proxy (Advanced/Options... in BOINC Manager).

This is from thread #48

Anyone have ideas on Jim S's question below? (1119185)

I found these lines interesting:

6/19/2011 12:55:47 PM SETI@home Fetching scheduler list
6/19/2011 12:55:48 PM SETI@home Master file download succeeded

He can't report or upload - but he did reach the server with that request, so that seems to rule out some possibilites.

I get a lot of "can't connect" due to congestion in the data straw, but get through eventually. Upload server's disabled again, but he's had problems for days. I don't have the knowledge to help on this but thought I'd point this out even though most of you probably already saw it.

And everything has been rebooted at least 3 times due to weather and all firewalls checked out.

---

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

Command prompt commands,
ipconfig/flushdns did nothing.
tracert to berkeley stopped about 3 hops short. (208.68.240.20)
Ping timed out 5 times in a row. (208.68.240.20)
I would hate to detach/Reattach and lose all of the work on my boxes.
I don't want to reset S@H.
All of my equiptment checked out.
My ISP and or firewalls aren't the problem.(Called my ISP)
And ALL of my other projects are having a Blast.
I don't know what to do...I'm Stumped. :((

---

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

Command prompt commands,
ipconfig/flushdns did nothing.
tracert to berkeley stopped about 3 hops short. (208.68.240.20)
Ping timed out 5 times in a row. (208.68.240.20)
I would hate to detach/Reattach and lose all of the work on my boxes.
I don't want to reset S@H.
All of my equiptment checked out.
My ISP and or firewalls aren't the problem.(Called my ISP)
And ALL of my other projects are having a Blast.
I don't know what to do...I'm Stumped. :((

Only a guess, but could it be the old problem with DNS not resolving properly?

Try entering these lines in the HOSTS file:

208.68.240.16 setiboincdata.ssl.berkeley.edu
208.68.240.20 setiboinc.ssl.berkeley.edu
208.68.240.13 boinc2.ssl.berkeley.edu

And restart Boinc.

Command prompt commands,
ipconfig/flushdns did nothing.
tracert to berkeley stopped about 3 hops short. (208.68.240.20)
Ping timed out 5 times in a row. (208.68.240.20)
I would hate to detach/Reattach and lose all of the work on my boxes.
I don't want to reset S@H.
All of my equiptment checked out.
My ISP and or firewalls aren't the problem.(Called my ISP)
And ALL of my other projects are having a Blast.
I don't know what to do...I'm Stumped. :((

Don't reset the project...it doesn't help
I'm having the same issue. Boxes at work running fine. Boxes at home not
doing JACK!

BUT, I'm getting :

C:\Windows\system32>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 DD-WRT [192.168.1.1]
2 7 ms 5 ms 5 ms 10.131.104.1
3 9 ms 16 ms 10 ms 24.248.104.102
4 10 ms 9 ms 9 ms btnrdsrj02-ae3.0.rd.br.cox.net [24.248.104.182]

5 73 ms 25 ms 18 ms 68.1.2.119
6 54 ms 69 ms 55 ms 10gigabitethernet1-2.core1.phx1.he.net [72.52.92
.253]
7 56 ms 53 ms 55 ms 10gigabitethernet2-2.core1.lax1.he.net [72.52.92
.249]
8 65 ms 63 ms 63 ms 10gigabitethernet1-3.core1.pao1.he.net [72.52.92
.21]
9 * * * Request timed out.
10 * * * Request timed out.
11 ^C
C:\Windows\system32>

A dead end at Hurricane...

---

"Two things are infinite: The universe and human stupidity; and I'm not sure about the universe." - Albert Einstein

A dead end at Hurricane...

Excellent sleuthing and brilliant conclusion! ;-) (No, that's not sarcasm)

Command prompt commands,
ipconfig/flushdns did nothing.
tracert to berkeley stopped about 3 hops short. (208.68.240.20)
Ping timed out 5 times in a row. (208.68.240.20)
I would hate to detach/Reattach and lose all of the work on my boxes.
I don't want to reset S@H.
All of my equiptment checked out.
My ISP and or firewalls aren't the problem.(Called my ISP)
And ALL of my other projects are having a Blast.
I don't know what to do...I'm Stumped. :((

Don't reset the project...it doesn't help
I'm having the same issue. Boxes at work running fine. Boxes at home not
doing JACK!

BUT, I'm getting :

C:\Windows\system32>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 DD-WRT [192.168.1.1]
2 7 ms 5 ms 5 ms 10.131.104.1
3 9 ms 16 ms 10 ms 24.248.104.102
4 10 ms 9 ms 9 ms btnrdsrj02-ae3.0.rd.br.cox.net [24.248.104.182]

5 73 ms 25 ms 18 ms 68.1.2.119
6 54 ms 69 ms 55 ms 10gigabitethernet1-2.core1.phx1.he.net [72.52.92
.253]
7 56 ms 53 ms 55 ms 10gigabitethernet2-2.core1.lax1.he.net [72.52.92
.249]
8 65 ms 63 ms 63 ms 10gigabitethernet1-3.core1.pao1.he.net [72.52.92
.21]
9 * * * Request timed out.
10 * * * Request timed out.
11 ^C
C:\Windows\system32>

A dead end at Hurricane...

THATS WHERE MINE STOPPED!
Will try the others after Supper.

---

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

It's working here on my 3G connection:

C:\Windows\System32>tracert 208.68.240.20

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

1 374 ms 389 ms 379 ms 172.30.132.113
2 * 366 ms 389 ms te-4-2.car1.Manchester1.Level3.net [195.50.119.9]
3 345 ms 391 ms 397 ms ae-4-4.ebr1.London1.Level3.net [4.69.133.102]
4 349 ms 379 ms 379 ms ae-1-51.edge3.London1.Level3.net [4.69.139.73]
5 365 ms 379 ms 379 ms Telia [4.68.111.182]
6 327 ms 399 ms 389 ms ldn-bb1-link.telia.net [80.91.246.144]
7 410 ms 479 ms 499 ms ash-bb1-link.telia.net [213.248.65.98]
8 501 ms 519 ms 519 ms sjo-bb1-link.telia.net [80.91.252.220]
9 499 ms 539 ms 539 ms hurricane-113209-sjo-bb1.c.telia.net [213.248.86.54]
10 483 ms 539 ms 559 ms 64.71.140.42
11 * 788 ms 559 ms 208.68.243.254
12 3913 ms 539 ms 559 ms setiboinc.ssl.berkeley.edu [208.68.240.20]

Trace complete.

C:\Windows\System32>

Claggy

The fact that some people are able to get all the way through to SSL from HE, but others stop at the same point indicate that the problem lies somewhere within the HE network/routing space.

This means it is not something SETI@Home can fix on their own, other than calling them up and alerting them of the problem.