I've checked my firewall, even disabled it, but that doesn't change what happens:
- When trying to connect to localhost, I get a connection failure
- When connecting 'remotely' to 192.168.0.4 in this case (the computer's own IP), the manager, etc, can connect.

Are you sure, your password in gui_rpc_auth.cfg is not empty and BOINC Manager is started from the BOINC install folder?

If another program is using port 1043, shouldn't the latter fail as well?

I have not so much experience with this problem, but normally I would say yes.

This happened on two computers, both are running Windows XP SP2, and in both cases it happened after upgrading to boinc 5.2.x and then rebooting the computer

I am running the 5.2.7 in different configuration on XP SP2 hosts too. No problems so far. Are you using XP home? And have you tried to install BOINC as Service. That is for my feeling the best way to use it on XP.

You get a connection failure too if the BOINC Daemon can not start. That can happen when you have wrong access rights for example. Possible there are some error messages in the BOINC install folder in the logfiles:

stderr.txt, stdout.txt, stderrdae.txt, stdoutdae.txt

---

I occasionally get that problem on Linux.. stopping and restarting the network fixes it.. have you tried restarting the windows network service ?

---

Disabling and enabling my local network connection and release / renew via ipconfig has no effect.

---

On my WinXP box alg.exe, the Application Layer Gateway Service, had latched on to port 1043. Stoping that service allowed BOINC 5.0.2.7 to finally start.

---

On my WinXP box alg.exe, the Application Layer Gateway Service, had latched on to port 1043. Stoping that service allowed BOINC 5.0.2.7 to finally start.

Nice catch! Stopping and starting the Application Layer Gateway service worked for me too. I'm not sure why, but this is a fix that doesn't require me to reboot 1 to 20+ times to get boincmanager working properly.

---

Not very happy. Switched across today because I got the notification about Seti@Home moving totally across to BOINC. Installed on 2 machines:
- work laptop seems to work fine. Runs XP Pro.
- home PC (also running XP Pro): seems to be OK on first installation. Then screensaver locks PC up. Following reboot BOINC Manager fails to connect. Uninstalled.

This software does not seem ready for mass use. I'm sure it won't be able to cope with users switching across from SETI.

Any ideas what I can do about my 2 problems on the Home PC (screensaver failure and failure to connect)?

Martin

---

There are times when the BOINC Manager gets started before the BOINC daemons are running, and you see this message.

Yes, there are times....like, ALWAYS.

Can do nothing with the running BOINC Manager at that point. It will not do any work and no amount of "Retry communications" has any effect.

I tried BOINC a year ago. Finding that it was not ready for general release, I backed off to classic Setitathome. Now, I'm being dragged kicking and screaming into BOINC once more. And, its STILL not ready for general release.

I had to kill off the running BOINC Manager and restart it manually to get it to recognize the network connection.

---

It seems a lot of us are SETI@Home refugees here.
I was involved in Beta testing BOINC when it first went public,
but the servers were never up frequently enough to make it reliable.
I've been plugging away at SETI work units, now on 2,189.

Now I have to move - this should be easy.

I download the software OK.
The installation asks at one stage about running as a service.
I ticked YES
The install failed when one would have expected it to say
"You must restart your computer for these changes to take effect"
it actually said "Your service has failed to start"
I cannot find any sign of a new service.

So I went through the install process again, only this time
I choose the 'run when User Logged-In' installation.
This installation works.

Under BOINC Manager > Projects > Attach to Project > Project URL : http://setiathome.berkeley.edu
brings up a dialog wanting my email address and my Account Key
(Which SETI@Home has just sent me)
"Failed to Attach to Project"

I haven't been able to take it any further.
Meanwhile SETI is plugging away ...

---

I am also having the exact same problem. Even after uninstall and re-install. boinc.exe never loads, even when I click on it in Windows Explorer.
I tried starting it from the command line box in Win XP, and I get this error message:
________________________________
To pause/resume tasks hit CTRL-C, to exit hit CTRL-BREAK
2005-11-29 07:38:08 [---] Starting BOINC client version 5.2.12 for windows_intel
x86
2005-11-29 07:38:08 [---] libcurl/7.14.0 OpenSSL/0.9.8 zlib/1.2.3
2005-11-29 07:38:08 [---] Data directory: C:\\Program Files\\BOINC

***UNHANDLED EXCEPTION****
Reason: Access Violation (0xc0000005) at address 0x7C901010 read attempt to addr
ess 0x00000034

1: 11/29/05 07:38:08
_________________________________
This happens every single time. This is the same Windows box that I've had for years, everything else seems to be running fine. The old SETI runs. Folding At Home runs, etc.
I hope this helps someone come up with a solution.
-Chrys

---

Uninstalling and then re-installing into a different directory seems to have fixed it!

---

I am having the same problem as this. I Changed from classic SETI to BOINC a few days ago. Seti@home on BOINC worked fine until yesterday, when I started getting the 'not able to connect to a BOINC client message'

I have tried - uninstalling BOINC and then installing the newest version.
truning the computer off for a few minutes
disabling my firewall.

but nothing has helped. Has anyone any advice?

It seems a lot of us are SETI@Home refugees here.
I was involved in Beta testing BOINC when it first went public,
but the servers were never up frequently enough to make it reliable.
I've been plugging away at SETI work units, now on 2,189.

Now I have to move - this should be easy.

I download the software OK.
The installation asks at one stage about running as a service.
I ticked YES
The install failed when one would have expected it to say
"You must restart your computer for these changes to take effect"
it actually said "Your service has failed to start"
I cannot find any sign of a new service.

So I went through the install process again, only this time
I choose the 'run when User Logged-In' installation.
This installation works.

Under BOINC Manager > Projects > Attach to Project > Project URL : http://setiathome.berkeley.edu
brings up a dialog wanting my email address and my Account Key
(Which SETI@Home has just sent me)
"Failed to Attach to Project"

I haven't been able to take it any further.
Meanwhile SETI is plugging away ...

---

Craig Miller

This worked for me so I will pass it on. Going to projects, attach to projects:
After entering the SETI URL and the next dialog/question box comes, just press enter without entering any data. When I did this my system came up and connected to "local host"
Let me know if this works or not
Jim

---

There are three known issues for the "connection failure". And when I talk about "connection failure" this means the connection between BOINC Manager (boincmgr.exe) and BOINC client (boinc.exe) and is here related only to the Windows platform.

With the BOINC 5.2.13 client (must be the same with 5.2.12) you start BOINC Manager in single or share install mode and normaly BOINC Manager should start the BOINC Client, but this failed.

Issue 1:

Your firewall is blocking the program start or the ports BOINC manager needs to start the boinc.exe program. Test this by shutdown your firewall and then start BOINC Manager.

Issue 2:

Other programs, i.e. Windows alg.exe (Application layer gateway) use the port 1043, which is reserved for BOINC. Then BOINC Manager is not able to start the boinc.exe program too. Youi may test this by open a DOS window, change to the BOINC directory and start boinc.exe. This should be succesfully and possible BOINC report in a message line to use the alternate port. You can then start BOINC manager and it should connect to boinc.exe.

Issue 3:

Boinc Manager and BOINC client use a password to protect the communication between them. Both try to find the gui_rpc_auth.cfg file with the password in the work directory. If you move and start BOINC Manager from a other place in the filesystem they may find different passwords and get a connection failure with a wrong password message.

Solution:

For issue 1. try to configure your firewall in a way that boinc.exe and boincmgr.exe can start other programs and communicate on all tcp ports on localhost.

For issue 2. the only solution is to install and use BOINC in service mode or (if you have enough knowledge) stop the other program using the BOINC port. A new BOINC release may fix this issue, but I don't know when it will be published.

For issue 3. be sure to start BOINC Manager form the install folder or be sure to have the same password file in both working directory.

Greetings from Bremen/Germany
Jens Seidler
Webmaster http://www.boinc.de/

---