Matt, be patient. The seti team should be in shortly and should have everything up and running again soon. This problem started during the long weekend for Thanksgiving holidays so they haven't had a chance to get in yet. It's happened before and usually is not a big problem to fix. It's only 7am there so they should be in in about an hour or so.

---

PROUD MEMBER OF Team Starfire World BOINC

my seti tasks never start. been saying downloading for 2 h rs now.
This is my message
11/30/2009 3:56:45 PM||Starting BOINC client version 6.10.18 for windows_x86_64
11/30/2009 3:56:45 PM||log flags: file_xfer, sched_ops, task
11/30/2009 3:56:45 PM||Libraries: libcurl/7.19.4 OpenSSL/0.9.8l zlib/1.2.3
11/30/2009 3:56:45 PM||Data directory: C:\ProgramData\BOINC
11/30/2009 3:56:45 PM||Running under account James Halen
11/30/2009 3:56:45 PM||Processor: 2 GenuineIntel Pentium(R) Dual-Core CPU T4200 @ 2.00GHz [Intel64 Family 6 Model 23 Stepping 10]
11/30/2009 3:56:45 PM||Processor: 1.00 MB cache
11/30/2009 3:56:45 PM||Processor features: fpu tsc pae nx sse sse2 pni
11/30/2009 3:56:45 PM||OS: Microsoft Windows Vista: Home Premium x64 Edition, Service Pack 1, (06.00.6001.00)
11/30/2009 3:56:45 PM||Memory: 3.96 GB physical, 8.10 GB virtual
11/30/2009 3:56:45 PM||Disk: 451.07 GB total, 337.44 GB free
11/30/2009 3:56:45 PM||Local time is UTC -5 hours
11/30/2009 3:56:45 PM||No usable GPUs found
11/30/2009 3:56:45 PM||Not using a proxy
11/30/2009 3:56:46 PM|SETI@home|URL http://setiathome.berkeley.edu/; Computer ID 5200761; resource share 100
11/30/2009 3:56:46 PM||No general preferences found - using BOINC defaults
11/30/2009 3:56:46 PM||Preferences limit memory usage when active to 2028.72MB
11/30/2009 3:56:46 PM||Preferences limit memory usage when idle to 3651.70MB
11/30/2009 3:56:46 PM||Preferences limit disk usage to 10.00GB
11/30/2009 3:56:46 PM|SETI@home|Started download of setiathome_6.03_windows_intelx86.exe
11/30/2009 3:56:46 PM|SETI@home|Started download of setigraphics_6.03_windows_intelx86.exe
11/30/2009 3:56:49 PM|SETI@home|Temporarily failed download of setiathome_6.03_windows_intelx86.exe: connect() failed
11/30/2009 3:56:49 PM|SETI@home|Backing off 1 min 0 sec on download of setiathome_6.03_windows_intelx86.exe
11/30/2009 3:56:49 PM|SETI@home|Temporarily failed download of setigraphics_6.03_windows_intelx86.exe: connect() failed
11/30/2009 3:56:49 PM|SETI@home|Backing off 1 min 0 sec on download of setigraphics_6.03_windows_intelx86.exe
11/30/2009 3:56:49 PM|SETI@home|Started download of libfftw3f-3-1-1a_upx.dll
11/30/2009 3:56:49 PM|SETI@home|Started download of setiathome-6.03_AUTHORS
11/30/2009 3:56:51 PM|SETI@home|Temporarily failed download of libfftw3f-3-1-1a_upx.dll: connect() failed
11/30/2009 3:56:51 PM|SETI@home|Backing off 1 min 0 sec on download of libfftw3f-3-1-1a_upx.dll
11/30/2009 3:56:51 PM|SETI@home|Temporarily failed download of setiathome-6.03_AUTHORS: connect() failed
11/30/2009 3:56:51 PM|SETI@home|Backing off 1 min 0 sec on download of setiathome-6.03_AUTHORS
11/30/2009 3:57:15 PM||Project communication failed: attempting access to reference site
11/30/2009 3:57:17 PM||Internet access OK - project servers may be temporarily down.
11/30/2009 3:57:51 PM|SETI@home|Started download of setiathome_6.03_windows_intelx86.exe
11/30/2009 3:57:51 PM|SETI@home|Started download of setigraphics_6.03_windows_intelx86.exe
11/30/2009 3:57:53 PM||Project communication failed: attempting access to reference site
11/30/2009 3:57:53 PM|SETI@home|Temporarily failed download of setiathome_6.03_windows_intelx86.exe: connect() failed
11/30/2009 3:57:53 PM|SETI@home|Backing off 1 min 0 sec on download of setiathome_6.03_windows_intelx86.exe
11/30/2009 3:57:53 PM|SETI@home|Temporarily failed download of setigraphics_6.03_windows_intelx86.exe: connect() failed
11/30/2009 3:57:53 PM|SETI@home|Backing off 1 min 0 sec on download of setigraphics_6.03_windows_intelx86.exe
11/30/2009 3:57:54 PM||Internet access OK - project servers may be temporarily down.
11/30/2009 3:59:57 PM|SETI@home|Started download of setiathome_6.03_windows_intelx86.exe
11/30/2009 3:59:57 PM|SETI@home|Started download of setigraphics_6.03_windows_intelx86.exe
11/30/2009 3:59:59 PM||Project communication failed: attempting access to reference site
11/30/2009 3:59:59 PM|SETI@home|Temporarily failed download of setiathome_6.03_windows_intelx86.exe: connect() failed
11/30/2009 3:59:59 PM|SETI@home|Backing off 1 min 0 sec on download of setiathome_6.03_windows_intelx86.exe
11/30/2009 3:59:59 PM|SETI@home|Temporarily failed download of setigraphics_6.03_windows_intelx86.exe: connect() failed
11/30/2009 3:59:59 PM|SETI@home|Backing off 1 min 0 sec on download of setigraphics_6.03_windows_intelx86.exe
11/30/2009 4:00:00 PM||Internet access OK - project servers may be temporarily down.

---

-Articulas

"Every Choice Makes a Sacrifice"

Try if a reboot helps. Until the server problems are solved, there might be several reboots necessary to clear the DNS cache.

Gruß,
Gundolf

---

Computer sind nicht alles im Leben. (Kleiner Scherz)

SETI@home classic workunits 3,758
SETI@home classic CPU time 66,520 hours

And for those of you out there who are uncomfortable about opening a command window and typing strange incantations into it, or about twiddling with netbios settings etc.

Start->Settings->Network Connections
right click on the connection corresponding to your internet connection and select "repair"

Does a few extra things besides a flush, but you don't have to worry about accidentally breaking anything.

---

Is it still down because I have a pending project that has been downloading for the past 2 plus days. Also it seems VERY difficult to find help, like connecting with a live body. I am all for helping out, would be nice to get some help back. Or at least some of response even if it is just F*** off!

Difficult to find help?

There's a lot of workarounds in this thread, as well as in this one, in this one and in this one you posted in.

After there was a problem with the router on Wednesday around Midnight, which was fixed during Thanksgiving (!!), there is since a problem with the download servers at Seti. It has to be fixed at Seti.

Posting profanities isn't going to help you any quicker.

---

I also got this problem, but only one ONE machine - a quad core XP machine. For several days I got the same message:

12/1/2009 11:25:34 AM	SETI@home	Temporarily failed download of setiathome_6.03_windows_intelx86.exe: connect() failed
12/1/2009 11:25:34 AM	SETI@home	Backing off 1 hr 18 min 11 sec on download of setiathome_6.03_windows_intelx86.exe
12/1/2009 11:25:34 AM	SETI@home	Temporarily failed download of setigraphics_6.03_windows_intelx86.exe: connect() failed
12/1/2009 11:25:34 AM	SETI@home	Backing off 2 hr 37 min 43 sec on download of setigraphics_6.03_windows_intelx86.exe
12/1/2009 11:25:34 AM	SETI@home	Started download of libfftw3f-3-1-1a_upx.dll
12/1/2009 11:25:34 AM	SETI@home	Started download of setiathome-6.03_AUTHORS
12/1/2009 11:25:35 AM		Internet access OK - project servers may be temporarily down.
12/1/2009 11:25:37 AM		Project communication failed: attempting access to reference site
12/1/2009 11:25:37 AM	SETI@home	Temporarily failed download of libfftw3f-3-1-1a_upx.dll: connect() failed
12/1/2009 11:25:37 AM	SETI@home	Backing off 1 hr 20 min 3 sec on download of libfftw3f-3-1-1a_upx.dll
12/1/2009 11:25:37 AM	SETI@home	Temporarily failed download of setiathome-6.03_AUTHORS: connect() failed
12/1/2009 11:25:37 AM	SETI@home	Backing off 54 min 10 sec on download of setiathome-6.03_AUTHORS
12/1/2009 11:25:38 AM		Internet access OK - project servers may be temporarily down.
12/1/2009 11:26:37 AM	SETI@home	Started download of setiathome-6.03_COPYING
12/1/2009 11:26:37 AM	SETI@home	Started download of setiathome-6.03_COPYRIGHT
12/1/2009 11:26:39 AM		Project communication failed: attempting access to reference site
12/1/2009 11:26:39 AM	SETI@home	Temporarily failed download of setiathome-6.03_COPYING: connect() failed
12/1/2009 11:26:39 AM	SETI@home	Backing off 1 hr 16 min 50 sec on download of setiathome-6.03_COPYING
12/1/2009 11:26:39 AM	SETI@home	Temporarily failed download of setiathome-6.03_COPYRIGHT: connect() failed
12/1/2009 11:26:39 AM	SETI@home	Backing off 3 hr 16 min 9 sec on download of setiathome-6.03_COPYRIGHT
12/1/2009 11:26:40 AM		Internet access OK - project servers may be temporarily down.
12/1/2009 11:28:52 AM	SETI@home	Started download of setiathome-6.03_README
12/1/2009 11:28:52 AM	SETI@home	Started download of seti_603.jpg
12/1/2009 11:28:54 AM		Project communication failed: attempting access to reference site

My linux and windows 2000 machines seem to be working fine. It's just one machine that fails.

Yesterday I took a RESET on the XP machine and a Windows 2000 machine at the same time. Within minutes the Windows 2000 machine was updated with new .exe files and project files, while the XP machine did not get a single bit from seti.

I have tried everyting - reboot, reset project, deinstall and install, detach and attach again. Nothing works.

All my machines access internet through a stand alone firewall. I can see in the logfile that all are connection go boing2.ssl.berkeley.edu with success. So there is nothing wrong with the connection.

I suspect that there must be somethign wrong in the database that cause this single machine to fail when trying to get new data.

---

I can see in the logfile that all are connection go boing2.ssl.berkeley.edu with success. So there is nothing wrong with the connection.

In fact boinc2.ssl.berkeley.edu is resolved into two IP addresses:
208.68.240.18 and 208.68.240.13
Since last Wednesday, the second one didn't work. So, you had only a 50% chance that after rebooting BOINC could download anything from SETI.

Meanwhile I guess the crew at Berkeley has fixed the server.

Gruß,
Gundolf

---

Computer sind nicht alles im Leben. (Kleiner Scherz)

SETI@home classic workunits 3,758
SETI@home classic CPU time 66,520 hours

Just checked the firewall and my "problem" XP machine do try to communicate with both IP-adresses.

---

Just checked the firewall and my "problem" XP machine do try to communicate with both IP-adresses.

If it still doesn't work, here a little "program" :-)

stop BOINC (make sure that boinc.exe isn't running)
ping boinc2.ssl.berkeley.edu
do while 208.68.240.13
  ipconfig /flushdns
  ping boinc2.ssl.berkeley,edu
end do
start BOINC

Gruß,
Gundolf

Thanks, it did not help but it gave me an idea:

I added an addresse translation rule in the firewall forcing all traffic to 208.68.240.18.

It worked!

---

If it still doesn't work, here a little "program" :-)

stop BOINC (make sure that boinc.exe isn't running)
ping boinc2.ssl.berkeley.edu
do while 208.68.240.13
  ipconfig /flushdns
  ping boinc2.ssl.berkeley,edu
end do
start BOINC

Gruß,
Gundolf

For those who aren't so Windows-savvy, what are the exact steps in order to execute the above??? I was able to ping SETI in Command Prompt, but the whole "do" stuff threw me off (I get an error).

(ask me to do anything on a Mac, and I can make you sliced bread :E ^_~ )!

Help appreciated ^^ !

---

That isn't a real program, just a recipe you have to follow step by step. That's why I put it in quotes ;-)

I hope it isn't necessary any longer, anyway, as the maintenance outage is over.

Gruß,
Gundolf

Eric, he was saying that if your ping went to 208.68.240.13 then you needed to do an ipconfig/flushdns from the command prompt window. Then ping boinc2.ssl.berkeley.edu again. If it still pinged to 13 then wash, rinse, repeat. If it went to 208.68.240.18 then exit command prompt and restart boinc.

Since the guys got the server fixed this is no longer needed but it has happened before and will probably happen again so it is a good trick to remember.

I forgot to add you may have to run the command window as administrator to do the ipconfig/flushdns.

---

PROUD MEMBER OF Team Starfire World BOINC

Thanks for the help everyone ^_^ ! Yeah, it's all working fine and dandy now, although I did do a change and repair of the program after it didn't connect the first time after the outage. I'm not sure if that's something else to try down the road, but glad to see it all crunching nicely once again after being dormant for a while.....

;D ,
Eric

---