At the risk of annoying everyone, I redid with names.
comcast is my isp. transitrail.net is a peering program
(has nice web page) and is part of cenic.net.
Which gets us to Berkeley.edu.

1 192.168.1.1 (192.168.1.1) 0.599 ms 1.452 ms 1.714 ms
2 24.23.156.1 (24.23.156.1) 51.168 ms 56.180 ms 73.184 ms
3 te-5-1-ur01.sanmateo.ca.sfba.comcast.net (68.86.248.209) 56.502 ms 56.705 ms 56.916 ms
4 te-1-3-0-1-ar01.sfsutro.ca.sfba.comcast.net (68.87.226.246) 57.699 ms 57.945 ms 58.062 ms
5 pos-1-9-0-0-cr01.sanjose.ca.ibone.comcast.net (68.86.90.225) 59.289 ms 59.532 ms 59.654 ms
6 pos-0-1-0-0-pe01.529bryant.ca.ibone.comcast.net (68.86.87.2) 60.200 ms 15.612 ms 37.409 ms
7 te2-3--406.tr01-plalca01.transitrail.net (137.164.130.233) 82.546 ms 82.658 ms 82.762 ms
8 137.164.131.62 (137.164.131.62) 44.195 ms 44.471 ms 44.632 ms
9 dc-svl-core1--svl-px1-10ge-1.cenic.net (137.164.46.204) 44.819 ms 47.177 ms 47.437 ms
10 dc-oak-agg1--svl-core1-10ge.cenic.net (137.164.47.114) 47.635 ms 47.757 ms 48.192 ms
11 dc-ucb-gw-1--oak-agg1.cenic.net (137.164.50.85) 48.378 ms 48.504 ms 48.858 ms
12 t2-3.inr-202-reccev.Berkeley.EDU (128.32.0.39) 14.862 ms 37.860 ms 46.259 ms
13 g5-2.inr-204-sut.Berkeley.EDU (128.32.255.107) 46.383 ms 46.310 ms 44.014 ms
14 * * *
All the rest of the 30 are * * *.

---

At the risk of annoying everyone, I redid with names.
comcast is my isp. transitrail.net is a peering program
(has nice web page) and is part of cenic.net.
Which gets us to Berkeley.edu.

*edited out tracert*

You are missing, which I believe the *** is a timeout, webfarm.Berkeley.EDU [169.229.131.91]

Mine comes back fine with it being the last hop for me. Actually it appears your routing inside Berkley is different from mine.

Mine goes from transitrail to cenic then berkeley. Inside there it travels from reccev [128.32.0.39] to srb [128.32.255.43](note not sut) then to the webfarm.

Here is mine minus the Charter specific ISP hops from me to the backbone:

te4-1.tr01-chcgil01.transitrail.net [137.164.129.11]
te4-1.tr01-sttlwa01.transitrail.net [137.164.129.2]
64.57.20.222
137.164.131.62
dc-svl-core1--svl-px1-10ge-2.cenic.net [137.164.46.12]
dc-oak-agg1--svl-core1-10ge.cenic.net [137.164.47.114]
dc-ucb-gw-1--oak-agg1.cenic.net [137.164.50.85]
t2-3.inr-202-reccev.Berkeley.EDU [128.32.0.39]
t1-1.inr-211-srb.Berkeley.EDU [128.32.255.43]
webfarm.Berkeley.EDU [169.229.131.81]

EDIT: The address "setiathome.ssl.berkeley.edu" is resolving for me now. I guess I was mistaken, as it is not an alias for "setiathome.berkeley.edu". Both addresses resolve to the same IP address, though.

If that's the case for you, then you have some DNS issues. Here is how they ping out for me.

setiathome.ssl.berkeley.edu [128.32.18.150] (as well as seti.ssl.berkeley.edu)
berkeley.edu [169.229.131.81]

---

Traveling through space at ~67,000mph!

Lost uploads, downloads and scheduler contact again on my Main ISP, switched to 3G connection, all is O.K there,

Claggy

Lost uploads, downloads and scheduler contact again on my Main ISP, switched to 3G connection, all is O.K there,

Claggy

Yeah, you can literally see it in the cricket logs when it goes down and up.

---

Lost uploads, downloads and scheduler contact again on my Main ISP, switched to 3G connection, all is O.K there,

Claggy

It's the same with my ISP, sometimes it works, sometimes not. Without having a clue, I think it must be some problem with the berkeley servers.

Either use another DNS or enter 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

---

My routers gets the DNS servers from my ISP, but I also have the addresses of my my previous ISPs & the ones we use at work listed. Here is a list of public DNS servers that you could use for alternates if you thing your ISP has wonky DNS issues.

---

SETI@home classic workunits: 93,865 CPU time: 863,447 hours
Join the [url=http://tinyurl.com/8y46zvu]BP6/VP6 User Group[

It seems when I try to browse too:

setiathome.ssl.berkeley.edu

it switches too:

setiathome.ssl.berkeley.edu.org

and comes up with some website parking crap. If I change it to:

setiathome.berkeley.edu

it then works fine.

---

Both of those load the SETI site for me, I don't use my ISP DNS servers though.

---

Almost never, can't even remember, had ISP troubles, last lines from my LapTop,
using WLAN:
24-4-2011 12:16:51 SETI@home Sending scheduler request: To fetch work.
24-4-2011 12:16:51 SETI@home Reporting 1 completed tasks, requesting new tasks
24-4-2011 12:16:53 SETI@home Started upload of 30dc10ab.13161.5384.5.10.125_1_0
24-4-2011 12:16:54 SETI@home Scheduler request completed: got 1 new tasks
24-4-2011 12:16:56 SETI@home Started download of 30dc10ab.31059.15609.7.10.218
24-4-2011 12:16:57 SETI@home Finished upload of 30dc10ab.13161.5384.5.10.125_1_0
24-4-2011 12:17:01 SETI@home Finished download of 30dc10ab.31059.15609.7.10.218
24-4-2011 13:57:59 SETI@home Starting 30dc10ab.31059.15609.7.10.218_1
24-4-2011 13:57:59 SETI@home Starting task 30dc10ab.31059.15609.7.10.218_1 using setiathome_enhanced version 603 .

---

Both of those load the SETI site for me, I don't use my ISP DNS servers though.

Yeah, that was part of my problem. If I tried to use the one to load the Seti web page it would just time out but I could get to the other stuff fine. If I took out the SSL part I could get there instantly. I wonder what is going on with that.

---

Both of those load the SETI site for me, I don't use my ISP DNS servers though.

Yeah, that was part of my problem. If I tried to use the one to load the Seti web page it would just time out but I could get to the other stuff fine. If I took out the SSL part I could get there instantly. I wonder what is going on with that.

Both of them load fine for me, the front page, look above for the bolded. The people having issues are because they are using DNS servers that probably have out dated records. Judging by most of you guys reporting problems, you aren't pulling the correct IP address when you do a ping or tracert I would imagine the DNS you are using caches too long and has out dated information. They may have changed things campus side and your ISP simply hasn't polled the new information yet. Best way to find out is use a different DNS and see if the problems go away. That's why I started using more reliable DNSs a long long time ago. It will more than likely work itself out in 36-72 hours or less. Sometimes it takes awhile for these things to propagate.

---

Traveling through space at ~67,000mph!

Strange, since last 2-3 days very often get the message :Couldn´t resolve hostname.

Uploads fail and no more work to get. Server Status on Seti side seems to be working, but...

OK This message seems to fix the issue :Message 1099950

Regards
Some1new

---

All that we see or seem is but a dream within a dream.

Both of those load the SETI site for me, I don't use my ISP DNS servers though.

Yeah, that was part of my problem. If I tried to use the one to load the Seti web page it would just time out but I could get to the other stuff fine. If I took out the SSL part I could get there instantly. I wonder what is going on with that.

Both of them load fine for me, the front page, look above for the bolded. The people having issues are because they are using DNS servers that probably have out dated records. Judging by most of you guys reporting problems, you aren't pulling the correct IP address when you do a ping or tracert I would imagine the DNS you are using caches too long and has out dated information. They may have changed things campus side and your ISP simply hasn't polled the new information yet. Best way to find out is use a different DNS and see if the problems go away. That's why I started using more reliable DNSs a long long time ago. It will more than likely work itself out in 36-72 hours or less. Sometimes it takes awhile for these things to propagate.

You don't seem to understand. This has been going on for weeks. A server ip or name change would have propagated out long ago.

---

You don't seem to understand. This has been going on for weeks. A server ip or name change would have propagated out long ago.

You don't seem to understand how DNS works and how they are run by different people. My ISP has been known not to update records for a month.....So it propagating isn't necessarily automatic on every DNS or done often.

Also one other thing I would note if I was in your situation and some of us are trying to push across to you lot, is not everyone has this issue....so it's probably not on the Berkeley side of things.

---

Traveling through space at ~67,000mph!

Both of those load the SETI site for me, I don't use my ISP DNS servers though.

Yeah, that was part of my problem. If I tried to use the one to load the Seti web page it would just time out but I could get to the other stuff fine. If I took out the SSL part I could get there instantly. I wonder what is going on with that.

Both of them load fine for me, the front page, look above for the bolded. The people having issues are because they are using DNS servers that probably have out dated records. Judging by most of you guys reporting problems, you aren't pulling the correct IP address when you do a ping or tracert I would imagine the DNS you are using caches too long and has out dated information. They may have changed things campus side and your ISP simply hasn't polled the new information yet. Best way to find out is use a different DNS and see if the problems go away. That's why I started using more reliable DNSs a long long time ago. It will more than likely work itself out in 36-72 hours or less. Sometimes it takes awhile for these things to propagate.

You don't seem to understand. This has been going on for weeks. A server ip or name change would have propagated out long ago.

The use of the nslookup tool will quickly point out DNS issues for you.

c:\>nslookup
Default Server:  Knob01
Address:  192.168.1.20

> bruno.ssl.berkley.edu
Server:  Knob01
Address:  192.168.1.20

Non-authoritative answer:
Name:    bruno.ssl.berkeley.edu
Address:  128.32.18.138

> server 8.8.8.8
Default Server:  google-public-dns-a.google.com
Address:  8.8.8.8

> bruno.ssl.berkley.edu
Server:  google-public-dns-a.google.com
Address:  8.8.8.8

Non-authoritative answer:
Name:    bruno.ssl.berkeley.edu
Address:  128.32.18.138
> exit

In this example you can see that my internal lab DNS server and one of the public DNS servers that Google has are both giving the correct address response. If you enter the IP that comes up then you will resolve the host name assigned to that address.

> 128.32.18.138
Server:  google-public-dns-a.google.com
Address:  8.8.8.8

Name:    bruno.ssl.berkeley.edu
Address:  128.32.18.138

---

SETI@home classic workunits: 93,865 CPU time: 863,447 hours
Join the [url=http://tinyurl.com/8y46zvu]BP6/VP6 User Group[

I'm been seeing temporary upload issues periodically, too. They happen a few days apart (often around this time of day), last for a couple of hours, and seem to cure themselves automatically.

One has just started, and the first evidence is

25/04/2011 14:50:26 | SETI@home | Started upload of 29no10ab.16457.215446.14.10.230_1_0
25/04/2011 14:50:27 |  | [http] [ID#806] Info:  timeout on name lookup is not supported
25/04/2011 14:50:27 |  | [http] [ID#806] Info:  About to connect() to setiboincdata.ssl.berkeley.edu port 80 (#0)
25/04/2011 14:50:27 |  | [http] [ID#806] Info:    Trying 16.240.68.208... 
25/04/2011 14:50:48 |  | [http] [ID#806] Info:  Timed out
25/04/2011 14:50:48 |  | [http] [ID#806] Info:  Failed connect to setiboincdata.ssl.berkeley.edu:80; No error
25/04/2011 14:50:48 |  | [http] [ID#806] Info:  Expire cleared
25/04/2011 14:50:48 |  | [http] [ID#806] Info:  Closing connection #0
25/04/2011 14:50:48 |  | [http] HTTP error: Couldn't connect to server
25/04/2011 14:50:49 | SETI@home | Temporarily failed upload of 29no10ab.16457.215446.14.10.230_1_0: connect() failed

That IP address is the wrong way round....

I'll do some more digging.

In my case, it looks like a router problem:

C:\Users\Richard Haselgrove>nslookup
Default Server:  my.router
Address:  192.168.173.1

> setiboincdata.ssl.berkeley.edu
Server:  my.router
Address:  192.168.173.1

Non-authoritative answer:
Name:    setiboincdata.ssl.berkeley.edu

> server 8.8.8.8
Default Server:  google-public-dns-a.google.com
Address:  8.8.8.8

> setiboincdata.ssl.berkeley.edu
Server:  google-public-dns-a.google.com
Address:  8.8.8.8

Non-authoritative answer:
Name:    setiboincdata.ssl.berkeley.edu
Address:  208.68.240.16

These are the two DNS servers that my ISP (BT Internet) has automatically assigned for my router to use (I have dynamic IP):

C:\Users\Richard Haselgrove>nslookup
Default Server:  my.router
Address:  192.168.173.1

> setiboincdata.ssl.berkeley.edu
Server:  my.router
Address:  192.168.173.1

Non-authoritative answer:
Name:    setiboincdata.ssl.berkeley.edu

> 194.72.9.34
Server:  my.router
Address:  192.168.173.1

Name:    indnsc72.ukcore.bt.net
Address:  194.72.9.34

> setiboincdata.ssl.berkeley.edu
Server:  my.router
Address:  192.168.173.1

Non-authoritative answer:
Name:    setiboincdata.ssl.berkeley.edu

> 62.6.40.166
Server:  my.router
Address:  192.168.173.1

Name:    indnsc72.ukcore.bt.net
Address:  62.6.40.166

> setiboincdata.ssl.berkeley.edu
Server:  my.router
Address:  192.168.173.1

Non-authoritative answer:
Name:    setiboincdata.ssl.berkeley.edu

>

And then, just as I'm looking into it, the problem clears itself:

C:\Users\Richard Haselgrove>ipconfig /displaydns

Windows IP Configuration

    setiboincdata.ssl.berkeley.edu
    ----------------------------------------
    Record Name . . . . . : setiboincdata.ssl.berkeley.edu
    Record Type . . . . . : 1
    Time To Live  . . . . : 45
    Data Length . . . . . : 4
    Section . . . . . . . : Answer
    A (Host) Record . . . : 208.68.240.16

- yet nslookup still can't see it?

You don't seem to understand. This has been going on for weeks. A server ip or name change would have propagated out long ago.

You don't seem to understand how DNS works and how they are run by different people. My ISP has been known not to update records for a month.....So it propagating isn't necessarily automatic on every DNS or done often.

Also one other thing I would note if I was in your situation and some of us are trying to push across to you lot, is not everyone has this issue....so it's probably not on the Berkeley side of things.

So your theory is that all the people having this issue are having the same inept ISP people that aren't updating their DNS records? I am not saying it is Seti's issue but there is something else going on other then slow DNS updates. Also, not everyone may be going to the setiathome.ssl.berkeley.edu address so they may not get the problem at all. We also all know there are many different paths to get to that address depending on your route and connection method.

---

So your theory is that all the people having this issue are having the same inept ISP people that aren't updating their DNS records? I am not saying it is Seti's issue but there is something else going on other then slow DNS updates. Also, not everyone may be going to the setiathome.ssl.berkeley.edu address so they may not get the problem at all. We also all know there are many different paths to get to that address depending on your route and connection method.

Exactly my point. So why make it personal and say I don't know what's going on when you say it's the same reason I do. Sheesh.....

---

Traveling through space at ~67,000mph!

So your theory is that all the people having this issue are having the same inept ISP people that aren't updating their DNS records? I am not saying it is Seti's issue but there is something else going on other then slow DNS updates. Also, not everyone may be going to the setiathome.ssl.berkeley.edu address so they may not get the problem at all. We also all know there are many different paths to get to that address depending on your route and connection method.

Exactly my point. So why make it personal and say I don't know what's going on when you say it's the same reason I do. Sheesh.....

I give up, you clearly don't understand what I am saying or getting too.

---

Haven't really notice Up or Download throuble, last messages of my LT, but Firefox 4 gives a warning, your leaving a secured site(SSL) at SETI Bêta.

26-4-2011 23:59:22 SETI@home Scheduler request completed: got 2 new tasks
26-4-2011 23:59:24 SETI@home Started download of 16se10ae.11711.10292.13.10.249
26-4-2011 23:59:24 SETI@home Started download of 23fe11aj.1295.11271.11.10.1
26-4-2011 23:59:44 SETI@home Finished download of 16se10ae.11711.10292.13.10.249
26-4-2011 23:59:47 SETI@home Finished download of 23fe11aj.1295.11271.11.10.1
27-4-2011 0:23:41 SETI@home Started upload of 20oc10aa.2716.214464.11.10.111_1_0
27-4-2011 0:24:28 SETI@home Finished upload of 20oc10aa.2716.214464.11.10.111_1_0
27-4-2011 0:32:00 SETI@home Starting 23fe11aj.1295.11271.11.10.1_1
27-4-2011 0:32:53 SETI@home Sending scheduler request: To fetch work.
27-4-2011 0:32:53 SETI@home Reporting 1 completed tasks, requesting new tasks
27-4-2011 0:32:56 SETI@home Scheduler request completed: got 0 new tasks
27-4-2011 0:32:56 SETI@home Message from server: Project has no tasks available
27-4-2011 0:33:07 SETI@home Finished upload of 23fe11aj.1295.11271.11.10.1_1_0
27-4-2011 0:39:15 SETI@home Sending scheduler request: To fetch work.
27-4-2011 0:39:15 SETI@home Reporting 1 completed tasks, requesting new tasks
27-4-2011 0:39:20 SETI@home Scheduler request completed: got 0 new tasks
27-4-2011 0:39:20 SETI@home Message from server: Project has no tasks available
27-4-2011 0:44:23 SETI@home Sending scheduler request: To fetch work.
27-4-2011 0:44:23 SETI@home Requesting new tasks
27-4-2011 0:44:35 SETI@home Scheduler request completed: got 1 new tasks
27-4-2011 0:44:37 SETI@home Started download of 10dc10ad.11000.25016.15.10.173
27-4-2011 0:44:40 SETI@home Temporarily failed download of 10dc10ad.11000.25016.15.10.173: HTTP error
27-4-2011 0:44:40 SETI@home Backing off 1 min 0 sec on download of 10dc10ad.11000.25016.15.10.173
27-4-2011 0:45:41 SETI@home Started download of 10dc10ad.11000.25016.15.10.173
27-4-2011 0:45:43 SETI@home Temporarily failed download of 10dc10ad.11000.25016.15.10.173: HTTP error
27-4-2011 0:45:43 SETI@home Backing off 1 min 0 sec on download of 10dc10ad.11000.25016.15.10.173
27-4-2011 0:46:43 SETI@home Started download of 10dc10ad.11000.25016.15.10.173
27-4-2011 0:47:04 SETI@home Finished download of 10dc10ad.11000.25016.15.10.173

Last lines from BOINC. Appears to OK.
Also got plenty of work, some with 4 or 5 weeks deadline. In most cases it's more
1 to 3 days. Sometimes the rig with 2 HD5870's and an i7-2600, can get very noisy
a lot off heat from the GPU's, 80% out the rear, but 3 case fans have to run 1200rpm and one on 1600, but the fans from those cards are doing 3600rpm, a MW
WU drives those cards to their edge, with 99% GPU load.
The rev516 AP app.'s works OK, but takes some time finding the most effective setting with ccmd line, they validate and are much faster, 4 to 20 times the CPU times. AP optimized and stock AP V5.05

---