I've been seeing this on all of my clients, 3.03 and 3.08 under 
Windows, OS2 and Linux.  So, I think the problem is on the other end. 
I got so frustrated, I finally installed SetiQueue as a proxy server, 
and have all the workstatons getting their work units from there.

There is still the access problem to the seti server, but since I have
about 1 1/2 days of work units queued, the workstations never run out 
of work.  SeitQUEUE still says it only gets to the seti server about 
60% of the time, but when it does, it gets all the workunits I need 
(about 100 per day).

Wished I'd done this sooner.

Alex

On Mon, 1 Sep 2003 18:47:48 UTC, Jim Wilson 
<jgwilson@REMOVETHISadelphia.net> wrote:

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 

--