Curious.
Is everyone with "Connection Failed" on every boot running behind a Software Firewall or Virus protection?
Also, do links to projects through GUI cause problems?
I have intermittant problems with ZoneAlarm.
Seen other reports of AntiVirus software not working nice with BOINC.

NO, I do NOT run a firewall on my machines, excpet my main one, the rest are either easily fixable, thru reloading, they are mostly Seti machines, or my sons and I don't care if I have to rebuild it. My machine works fine, I use ZoneAlarm, BUT 2 other machines, they DO NOT connect thru mine to get to the net, are having this problem. One runs version 4.43, the other 4.27.
Adding on....I JUST tried upgrading from 4.43 to 4.45 and that did NOT help! But DOWNGRADING to version 4.19 DID work! I am now back crunching!
Don't ask me, but I HAVE upgraded with the MS automatic upgrades EVERYTIME they come out. Maybe the newer versions of Boinc are sensitive to something MS did.
I just clciked on the 4.19 file I had downloaded a while back and installed it, right over the top of the 4.45 I had JUST installed that did not work. 4.19 is now running fine AND all my old units are still there and crunching fine.

---

This problem has disappered for me ever since I installed BOINC 4.45. I was able to avoid it under 4.35 by going to ZONE-ALARM (do you have this or a similar firewall running?), and setting "PASS LOCK" for each of the three BOINC programs. This advise was thanks to another thread on this topic.
I therefore suggest that you download and install the latest recommended BOINC (4.45) and this should solve your problem.

---

BESTEST!

I'm using 4.45 and getting "connection failed" on one of my W2K machines. Another W2K machine with similar setup runs just fine with no problems at all. I've tried every tip and trick I've found to no avail. I just keep getting that error.

So one of my machines is back to seti classic. :-(

I'm using 4.45 and getting "connection failed" on one of my W2K machines. Another W2K machine with similar setup runs just fine with no problems at all. I've tried every tip and trick I've found to no avail. I just keep getting that error.

How did you install it? As service? Is the service in your Services list? Is it running (can you see boinc.exe in process list)? Check the files stdoutdae.txt,stderrdae.txt, stdoutgui.txt, stderrgui.txt in your BOINC directory; what's dumped there (at end of files)?

So one of my machines is back to seti classic. :-(

Wouldn't really help since Seti Classic will be surely shut down within 1-3 months.

The connection failure is usually caused by the manager trying to talk before the daemon is ready to listen. The usual fixes for this are:
File - Select Computer - leave everything blank
File - Select Computer - localhost
File - Select Computer - 127.0.0.1
restart BOINC
Reboot.

There is the possibility that some other program is using ports 1043 and 31416. In that case, you need to figure out what the offending programs are, and either do without them, or make certain that they get loaded AFTER BOINC gets loaded (or in some cases a long time before BOINC is loaded so that they stop using the ports before BOINC is loaded)

Try using the most recent development version (appears to be somewhat better about this), but this carries a higher risk of bugs.

---

BOINC WIKI