I've been using BOINC since October with no problems. Now when I re-boot my computer I keep getting a connection failed message? BOINC was up running all night long but when I re-booted my computer this morning BOINC wouldn't reconnect? I bought a new Dell computer to run this project. Not sure why I am getting a connection failed message does anyone have any answers? I tried going into the control panel to repair BOINC but connection still is failing?

If you can please help & thanks!

---

Not sure which connection you are referring to so, if it is to the server, the server may be down or busy, plus check our firewall..


Do you have BOINC starting at boot? If so delete it from windows startup and reboot, that works for some people...

OK, the disconnected issue means that the BOINC manager is not able to talk to the BOINC daemon. Whether or not you are uploading/downloading/crunching at this point must be determined with the task list (I do not remember how to bring this up for 95/98/me).
The usual reason for this problem is that the BOINC manager is starting and trying to talk before the BOINC daemon is ready to listen. The usual fix is to wait a minute or two and see if connecting to "" or "localhost" or "127.0.0.1" works.
If the above fails, then there is a possibility that the BOINC daemon is not starting. If that is the case, then staring it manually may help. If it is installed as a service, run "net start BOINC" from a command line. If it is installed as single or multi user, cd to the install directory, and run BOINC.exe. If it is now running, you are the victim of a bug that has hopefully been fixed in 5.1.
If it is still not working, you have a problem with one of the XML files, and you will probably have to delete the directory and start over. (I have seen this problem much less with 5.1).
You might also go to the BOINC folder and look for this file "gui rpc auth.cfg" open with word pad and change the password to one you like make sure you enter a return at the end and then save and reboot computer then try the local host entry in select computer popup..... Check your firewall.

---

BOINC Wiki

Thanks Jim!

It started working again. I have it set up at boot & out of the blue here & there when I reboot I get this message saying failed to connect. The BOINC is totaly blank with no information on it also & I Couldn't figure out why it was happening at random like this?

If this happens again I will try what you suggested.

Love & Light

Mary

Not sure which connection you are referring to so, if it is to the server, the server may be down or busy, plus check our firewall..


Do you have BOINC starting at boot? If so delete it from windows startup and reboot, that works for some people...

OK, the disconnected issue means that the BOINC manager is not able to talk to the BOINC daemon. Whether or not you are uploading/downloading/crunching at this point must be determined with the task list (I do not remember how to bring this up for 95/98/me).
The usual reason for this problem is that the BOINC manager is starting and trying to talk before the BOINC daemon is ready to listen. The usual fix is to wait a minute or two and see if connecting to "" or "localhost" or "127.0.0.1" works.
If the above fails, then there is a possibility that the BOINC daemon is not starting. If that is the case, then staring it manually may help. If it is installed as a service, run "net start BOINC" from a command line. If it is installed as single or multi user, cd to the install directory, and run BOINC.exe. If it is now running, you are the victim of a bug that has hopefully been fixed in 5.1.
If it is still not working, you have a problem with one of the XML files, and you will probably have to delete the directory and start over. (I have seen this problem much less with 5.1).
You might also go to the BOINC folder and look for this file "gui rpc auth.cfg" open with word pad and change the password to one you like make sure you enter a return at the end and then save and reboot computer then try the local host entry in select computer popup..... Check your firewall.

---