Message boards : BOINC Manager : Cannot attach to Project etc.
Message board moderation
Author | Message |
---|---|
Send message Joined: 14 Mar 06 Posts: 1 |
I am trying to join a Project and have spent all night attempting to get started but with no luck. I d/load everything but keep getting the following... Failed to attach to Project and BOINC cannot connect to a BOINC Manager and BOINC is not currently connected to a BOINC client!! It is hopeless and very frustrating as I want to contribute. Please advise. Thankyou Elisabeth |
Send message Joined: 29 Aug 05 Posts: 15563 |
Which project are you trying to attach to? |
Send message Joined: 8 Jan 06 Posts: 448 |
Please post the log in the message tab so we can see exactly what error message Boinc is giving. Boinc V 7.4.36 Win7 i5 3.33G 4GB NVidia 470 |
Send message Joined: 25 Nov 05 Posts: 1654 |
[quote]BOINC cannot connect to a BOINC Manager and BOINC is not currently connected to a BOINC client.[/qoute] This sounds likt the 2 parts of BOINC aren't talking. Perhaps your firewall is blocking the connection. What is written on the bottom right hand end of the gui? |
Send message Joined: 27 Mar 06 Posts: 7 |
I am trying to join a Project and have spent all night attempting to get started but with no luck. I d/load everything but keep getting the following... You are not alone, even though that is of no help. |
Send message Joined: 29 Mar 06 Posts: 1 |
I just dowloaded the manager and when I start it, I get a message that the manager cannot connect to the client computer. Can someone tell me how I can get this to work? I have registered with SETI@HOME but do not seem to get any troubleshooting from their site. Cheers. |
Send message Joined: 25 Nov 05 Posts: 1654 |
In File in the menu, click on: Select computer, then click OK, leaving the 2 fields blank. They are only for people with more than one computer, in a network. The gui will now connect to the 'worker', and you will get: Connected to localhost in the bottom right of the gui. Now you can go to the menu, and click Attach to a project. Or several. |
Send message Joined: 30 Aug 05 Posts: 98 |
I believe the problem you are experiencing is that your port 1043 is in use by another program. ICANN has registered that port to Boinc, but MS has used it in a program they made. Boinc used 1043 as a "loopback" address so that the manager could communicate with the daemon across networks. Boinc has switched to port 31416 in the newer developmental clients. computers this apply to will say "disconnected" on the very bottom bar (right hand side) of the Boinc manager. it should read (in most instances) "connected to localhost". are you experiencing this issue? tony |
Send message Joined: 13 May 06 Posts: 1 |
I had the same problem, but i solved it by going to the Boinc folder and running the boinc.exe file (the one that looks like an MS-DOS application).. After that, the manager could connect to my computer gain. I have yet to figureout how to hide that window that popsup. Hope this helps. Edit : Found this thread by a google search, and did not see all other thread's that solved this problem, sorry for bumping. |
Send message Joined: 13 May 06 Posts: 1 |
I find the same problem as Stuart. My message says "The project is temporarily unavailable. Please try again later." I tried the Les solution - not successful for me. I do not get a "disconnected" message or find a port conflict. Does the Project occationally shut down for modification or house cleaning? Allan I had the same problem, but i solved it by going to the Boinc folder and running the boinc.exe file (the one that looks like an MS-DOS application).. |
Send message Joined: 30 Aug 05 Posts: 98 |
I find the same problem as Stuart. My message says "The project is temporarily unavailable. Well, all projects shut down from time to time. This is the Boinc message board and it applies to the "manager" of all projects. What is your particular issue and which project is temporarily unavailable? Basically, I need you to describe your issue in more depth. tony |
Send message Joined: 13 May 06 Posts: 2 |
I believe the problem you are experiencing is that your port 1043 is in use by another program. ICANN has registered that port to Boinc, but MS has used it in a program they made. Boinc used 1043 as a "loopback" address so that the manager could communicate with the daemon across networks. Boinc has switched to port 31416 in the newer developmental clients. Thanks Tony. Boinc Manager also stopped working for me a few days ago. I guess around the time of one of my M$ hotfix updates. I too found that it would work by starting Boinc.exe but didn't want that as a permanent solution. All that's really needed is to install the BOINC 5.4.9 version. Port 31416 is used instead and everything works just fine. Thanks again. Doug Hornick |
Send message Joined: 16 Apr 06 Posts: 18 |
mmciastro wrote: ICANN has registered that port to Boinc, but MS has used it in a program they made. Boinc used 1043 as a "loopback" address so that the manager could communicate with the daemon across networks. Boinc has switched to port 31416 in the newer developmental clients. Unfortunately port 31416 is already in use as well: Port numbers |
Send message Joined: 30 Aug 05 Posts: 98 |
mmciastro wrote: Yes, I saw that myself. The whole point is that MS is taking a port and to fix the problem a different port is being used. It's worked for everyone so far (that was affected by the disconnected issue). As a matter of fact I found out on April 21st as can be see in this thread. In another post in that thread I asked about it. |
Copyright © 2024 University of California.
Permission is granted to copy, distribute and/or modify this document
under the terms of the GNU Free Documentation License,
Version 1.2 or any later version published by the Free Software Foundation.