3.08 cmdline client won't connect

on and off for the past 3 weeks or so, my client trys to send results
and fails, then then following message comes up

Sending result - connecting to server.
recv fd=64 n=-1, errno=2
Can't connect to server; will try again in an hour.

Seti@Home has been running on this box for about a year and a half.
1.6gb P4, Windows XP Pro, Norton Internet Security and Antivirus and
no problems on this end before now.

I downloaded and replaced the client. No change.

Anybody have any ideas?

Thanks!

Jim Wilson

fic wrote:
I'm having the same problem here... Also for the past 2,5 weeks.
I'm running the client on 6 pc's (different locations and different
providers) and they all have problems sending results.
All Windows-machines, some WinXP Pro, some Win2000 Pro.



"Jim Wilson" wrote in message
...
on and off for the past 3 weeks or so, my client trys to send
results and fails, then then following message comes up

Sending result - connecting to server.
recv fd=64 n=-1, errno=2
Can't connect to server; will try again in an hour.

Seti@Home has been running on this box for about a year and a half.
1.6gb P4, Windows XP Pro, Norton Internet Security and Antivirus and
no problems on this end before now.

I downloaded and replaced the client. No change.

Anybody have any ideas?

Thanks!

Jim Wilson

I similarly had this difficulty and found that disabling NIS solved the
problem.

Eddie in Colorado Springs

"When I read about the evils of drinking, I gave up reading." --Henny
Youngman

fic wrote:
I'm having the same problem here... Also for the past 2,5 weeks.
I'm running the client on 6 pc's (different locations and different
providers) and they all have problems sending results.
All Windows-machines, some WinXP Pro, some Win2000 Pro.



"Jim Wilson" wrote in message
...
on and off for the past 3 weeks or so, my client trys to send
results and fails, then then following message comes up

Sending result - connecting to server.
recv fd=64 n=-1, errno=2
Can't connect to server; will try again in an hour.

Seti@Home has been running on this box for about a year and a half.
1.6gb P4, Windows XP Pro, Norton Internet Security and Antivirus and
no problems on this end before now.

I downloaded and replaced the client. No change.

Anybody have any ideas?

Thanks!

Jim Wilson

I similarly had this difficulty and found that disabling NIS solved the
problem.

Eddie in Colorado Springs

"When I read about the evils of drinking, I gave up reading." --Henny
Youngman

On Mon, 1 Sep 2003 13:58:50 -0600, "Ed Felty"
wrote:

fic wrote:
I'm having the same problem here... Also for the past 2,5 weeks.
I'm running the client on 6 pc's (different locations and different
providers) and they all have problems sending results.
All Windows-machines, some WinXP Pro, some Win2000 Pro.



"Jim Wilson" wrote in message
...
on and off for the past 3 weeks or so, my client trys to send
results and fails, then then following message comes up

Sending result - connecting to server.
recv fd=64 n=-1, errno=2
Can't connect to server; will try again in an hour.

Seti@Home has been running on this box for about a year and a half.
1.6gb P4, Windows XP Pro, Norton Internet Security and Antivirus and
no problems on this end before now.

I downloaded and replaced the client. No change.

Anybody have any ideas?

Thanks!

Jim Wilson

I similarly had this difficulty and found that disabling NIS solved the
problem.

Eddie in Colorado Springs

"When I read about the evils of drinking, I gave up reading." --Henny
Youngman

Good suggestion. 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.

Jim

On Mon, 1 Sep 2003 13:58:50 -0600, "Ed Felty"
wrote:

fic wrote:
I'm having the same problem here... Also for the past 2,5 weeks.
I'm running the client on 6 pc's (different locations and different
providers) and they all have problems sending results.
All Windows-machines, some WinXP Pro, some Win2000 Pro.



"Jim Wilson" wrote in message
...
on and off for the past 3 weeks or so, my client trys to send
results and fails, then then following message comes up

Sending result - connecting to server.
recv fd=64 n=-1, errno=2
Can't connect to server; will try again in an hour.

Seti@Home has been running on this box for about a year and a half.
1.6gb P4, Windows XP Pro, Norton Internet Security and Antivirus and
no problems on this end before now.

I downloaded and replaced the client. No change.

Anybody have any ideas?

Thanks!

Jim Wilson

I similarly had this difficulty and found that disabling NIS solved the
problem.

Eddie in Colorado Springs

"When I read about the evils of drinking, I gave up reading." --Henny
Youngman

Good suggestion. 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.

Jim

"Jim Wilson" wrote in message
...
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 ...
Al


Jim

"Jim Wilson" wrote in message
...
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 ...
Al


Jim

"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...

"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...