I have several machines running boinc now, but one of them is reporting this pretty much consistently:

Fri 18 Nov 2005 12:47:29 GMT|SETI@home|Requesting 1728000 seconds of new work, and reporting 112 results
Fri 18 Nov 2005 12:48:14 GMT||Attempting to communicate with [setiboinc.ssl.berkeley.edu] timed out
Fri 18 Nov 2005 12:48:16 GMT|SETI@home|Scheduler request to http://setiboinc.ssl.berkeley.edu/sah_cgi/cgi failed with a return value of -182
Fri 18 Nov 2005 12:48:16 GMT|SETI@home|No schedulers responded
Fri 18 Nov 2005 12:48:21 GMT|SETI@home|Deferring communication with project for 1 hours, 51 minutes, and 9 seconds


The shell I'm running the manager in is reporting:

connect: Connection refused
connect: Operation now in progress
init_poll: get_socket_error(): 111

I've checked upstream connectivity with a web browser on the machine to the url it's complaining about and it's getting through. Any ideas what's going on here?

---

The connection is failing or being refused.

Is that machine firewalled out?
Bad routing?
Bad attempt to use proxies?
LAN/internet connection not enabled on that machine?
Has that user got internet access permissions?

Can you ping the Berkeley servers from that machine?

Might be worth trying as root a "service network restart"...

Good luck,
Martin

---

See new freedom: Mageia Linux
Take a look for yourself: Linux Format
The Future is what We all make IT (GPLv3)