I have three Windows XP machines running BOINC with climate prediction. For the last couple of weeks, two of these machines keep reporting that \"the BOINC Manager is unable to connect to client.\" message. The two machines that are not running the client have BOINC version 5.2.13 loaded. The machine that is properly running the client is operating on version 4.25. Any help that might be out there would be appreciated. Thanks, Trevor

---

Go to File in the menu and click \'Select computer...\'
When you get a popup window, click OK, leaving both fields blank.

If you are trying to use one computer to control the other two, it\'s a differnet matter, and I\'ll have to find the info on how to do it.

Go to File in the menu and click \'Select computer...\'
When you get a popup window, click OK, leaving both fields blank.

If you are trying to use one computer to control the other two, it\'s a differnet matter, and I\'ll have to find the info on how to do it.

Thank you for the suggestion. I tried your solution and still got the same response. I am not trying to use one computer to control the others, so I am not quite sure what I am doing wrong.

---

Hi, Trevor,

I\'m out of my element here because I don\'t use Proxies or software Firewalls.

However, many participants experienced connection problems when Proxy or, more likely, Firewall settings kept the Boinc Manager from getting a request out of the machine. Boinc.exe requires free access to port 80.

If that isn\'t your problem, would you please copy/paste the appropriate error lines from the Messages Tab?

Edit: Can\'t argue with success but 4.25 is \"historical\". At risk of an absurd suggestion, have you tried 4.25 on one of the failing machines? I doubt it will work but one never knows... If, on the off chance that it did work, it might give a clue for one of the Board\'s experts to diagnose when they return from Christmas holiday.

---

"We have met the enemy and he is us." -- Pogo
Greetings from coastal Washington state, the scenic US Pacific Northwest.

boinc.exe needs access to the web on ports 80 and 443, local access on ports 1043 and 31416.
boincmgr.exe needs local access on ports 1043 and 31416.
boinccmd.exe (if used) needs local access on ports 1043 and 31416.
boinc.scr may need local access on ports 1043 and 31416.

Sometimes the order of startup can cause these ports to be blocked. In that case exiting and restarting the client can help.

A real fix is in progress, a new set of ports has been requested from ICANN, as well as more robust handling of blocked ports.

---

BOINC WIKI

BOINCing since 2002/12/8

Hi, Trevor,

I\'m out of my element here because I don\'t use Proxies or software Firewalls.

However, many participants experienced connection problems when Proxy or, more likely, Firewall settings kept the Boinc Manager from getting a request out of the machine. Boinc.exe requires free access to port 80.

If that isn\'t your problem, would you please copy/paste the appropriate error lines from the Messages Tab?

Edit: Can\'t argue with success but 4.25 is \"historical\". At risk of an absurd suggestion, have you tried 4.25 on one of the failing machines? I doubt it will work but one never knows... If, on the off chance that it did work, it might give a clue for one of the Board\'s experts to diagnose when they return from Christmas holiday.

There is nothing on the messages tab--I presume this is due to the connection failure which states \"BOINC Manager is not able to connect to a BOINC client. Would you like to try to connect again?\"

---

If my suggestion worked, you will have:
BOINC Manager - (localhost)
on the left side of the top blue bar of the BOINC window, and:
Connected to localhost
on the bottom bar at the right. (There is a small round icon in front of each.)

At this point, you should be able to go to Projects in the menu, and click on Attach to project, which brings up a connection wizard.

Can you get this far?

If my suggestion worked, you will have:
BOINC Manager - (localhost)
on the left side of the top blue bar of the BOINC window, and:
Connected to localhost
on the bottom bar at the right. (There is a small round icon in front of each.)

At this point, you should be able to go to Projects in the menu, and click on Attach to project, which brings up a connection wizard.

Can you get this far?

I tried to connect to the local host by leaving both fields blank under \"Select Computer\". When I do this the lower right hand corner of the window says \"connecting to localhost\". This message is quickly replaced by \"Disconnected,\" and a new BOINC Manager window opens with the message \"connection failed\".

---

In that case, the two parts of BOINC can\'t talk to each other.
As John Keck said, they communicate via ports, which is a new idea in the 5.* versions.
It seems that good old Microsoft is grabbing one or more of the ports allocated to BOINC, and not letting it use it / them. (Apparently, MS progrms don\'t bother to check if a port belongs to other non-MS programs.)

I\'m not sure where you go from this point, as I haven\'t had any problems in the month since I upgraded, even after several reboots.
Perhaps it is necessary to rearrange the order in which software is started, so that BOINC starts before whatever MS program is being difficult. But I don\'t know how to do this. John or some other person may know.

In that case, the two parts of BOINC can\'t talk to each other.
As John Keck said, they communicate via ports, which is a new idea in the 5.* versions.
It seems that good old Microsoft is grabbing one or more of the ports allocated to BOINC, and not letting it use it / them. (Apparently, MS progrms don\'t bother to check if a port belongs to other non-MS programs.)

I\'m not sure where you go from this point, as I haven\'t had any problems in the month since I upgraded, even after several reboots.
Perhaps it is necessary to rearrange the order in which software is started, so that BOINC starts before whatever MS program is being difficult. But I don\'t know how to do this. John or some other person may know.

Actually it is normally better for BOINC to start after the other program, assuming both ports are not blocked. Exit BOINC completely and restart if you are having problems.

---

BOINC WIKI

BOINCing since 2002/12/8