3.08 cmdline client won't connect
"Alfred A. Aburto Jr." wrote
"Jim Wilson" wrote
On Mon, 1 Sep 2003 13:58:50 -0600, "Ed Felty"
[snip]
................ Upload/download works for mee with and without NIS.
I did get a private e-mail saying that "Connections (with seti@home)
have been strained for several weeks." Perhaps that's the simple
answer. I hadn't seen any posting on Berkeley's website so I posted
the question here.
I have the problem too. I have found that on the third try things go
through
ok (for some unexplained reason), but this can be a hassle if you have
more
than one machine to deal with ...
I think the problem my be due to the fact that they still haven't got that
new CPU installed on the main server ...
My SetiQueue has been having some difficulty connecting for the last few
days too - normally a whole bunch of results (50+) takes no more than a
couple minutes but it's a lot longer than that at the moment. I'm also
getting a lot of 'duplicate result' returns from Berkeley & that's usually a
symptom of network congestion - maybe all these recent worms Et Al aren't
helping..?
If you're having difficulty connecting direct then I'd suggest using a
queueing add-on like SetiQueue (SQ) - SQ will keep trying until it
eventually gets through whilst the machines accessing SQ keep on crunching
straight through any network difficulties ...
Ciao...
[UK]_Nick...
|