Just me, or has SETI been dead for a few days?

[J3anyus]

I haven't been able to send in new WUs for a few days now, every time I try, SETI Driver tells me it can't connect to the server. Since I haven't been able to send in WUs for awhile, I've cleared through my cache, and am just wasting CPU cycles. Has the server been down, or is the problem on my end? It might be on my end, because I used to run Norton Personal Firewall, and recently uninstalled it, and that might be causing weird problems with the connection. Any help would be good. Thanks!

J3

Edit: Somehow, about 500 grammar errors snuck into that. It's better now.

 

[IsOs]

Send your workunits to orangekid.teamanandtech.com port 5001. SETI server have bandwidth problem.

 

[Jerboy]

They've been having problem with limited bandwidth on their network.


The best solution I've found so far is doing all the transmitting and receiving late at night when traffic is light. The server is in Berkely so 3AM PST (6AM EST) would be a good time.

 

[caddlad]

I've had good luck up until 9:00 AM EST then things bog down.

There's a note on the SETI homepage explaining thier bandwidth situation.

 

[Adul]

I had a couple of WU built up, thank god I got 10 qued.

 

[conjur]

I'm sending/receiving just fine right now 🙂 over dial-up (cable modem out until at least Thur.) :disgust:

 

[Jerboy]

<< I had a couple of WU built up, thank god I got 10 qued. >>




I got 100 queued 😀 😀 😀 😀 😀

 

[networkman]

You probably don't want to know how many I've got queue'd. :Q 😀

 

[Poof]

You probably don't want to know how many I've got queue'd. :Q 😀

Yeah... ditto.... 😛

 

[Confused]

I have 142 in my SetiQueue, but it seems to be sending the results OK at the moment!

ConfusedBW

 

[zodder]

I finally removed my head from my arse and installed seti driver (with the help and patience of JustStarting) on my main machine. I couldn't take watching The Federation close in on me and not be able to do anything about it. 🙂