3.08 cmdline client won't connect
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
|