I am having repeated problems with BOINC Manager not connecting to local host. I've tried uninstalling and installing it several times with no joy, including a change in diectory name to try to get round a possible Win XP registery problem.

It happened last week but then, after repeated attempts to resolve the problem, it just started working again.

I can get it to run as a CMD service but nothing on the GUI version.

I have asked questions elsewhere in the forum without any response from the project staff so, just before I dump it altogether and move on elsewhere I thought I would post the problem here.

---

Did you check the Boinc message boards? It seems to be a boinc client issue. You can also subscribe to the boinc email lists and post your question (possibly to the boinc_dev list). I don't know what could be causing this issue.

in versions up to 5.2.15 it's caused by some program stopping boinc from getting access to port 1043. Boinc uses port 1043 to do a "Loopback" between the daemon (boinc.exe) and the boinc manager (boincmgr.exe). This was done so the manager could be used to talk to/control any daemon on your network from one computer using the "select computer" option.

If you open a command prompt window (start, all programs, accessories, then select command prompt) and type in:

netstat -a

hit enter it will list your current TCP ports. You should see three references to 1043. Two would say established and one would say listening. You should see your puter listening on 1043, then 1043 talking to another port (say 1045) and then 1045 talking to 1043.

If you do not see this then something is stopping boinc from getting that port. Microsoft has see fit to use 1043 for some programs even though ICANN has assigned that port to boinc. In the newer developemental versions of boinc Dr Anderson and Co have secured and are using 31416 instead.

try clicking "File", "Select computer", leave both boxes blank and hit OK

OR

try clicking "file", "Select computer", type in localhost, leave password blank, hit OK

OR

try clicking "file", "Select computer", type in 127.0.0.1, leave password blank and hit OK

If this doesn't work I have another option.

tony

in versions up to 5.2.15 it's caused by some program stopping boinc from getting access to port 1043. Boinc uses port 1043 to do a "Loopback" between the daemon (boinc.exe) and the boinc manager (boincmgr.exe). This was done so the manager could be used to talk to/control any daemon on your network from one computer using the "select computer" option.

If you open a command prompt window (start, all programs, accessories, then select command prompt) and type in:

netstat -a

hit enter it will list your current TCP ports. You should see three references to 1043. Two would say established and one would say listening. You should see your puter listening on 1043, then 1043 talking to another port (say 1045) and then 1045 talking to 1043.

If you do not see this then something is stopping boinc from getting that port. Microsoft has see fit to use 1043 for some programs even though ICANN has assigned that port to boinc. In the newer developemental versions of boinc Dr Anderson and Co have secured and are using 31416 instead.

try clicking "File", "Select computer", leave both boxes blank and hit OK

OR

try clicking "file", "Select computer", type in localhost, leave password blank, hit OK

OR

try clicking "file", "Select computer", type in 127.0.0.1, leave password blank and hit OK

If this doesn't work I have another option.

tony

Can I get you to start submitting some of these as FAQs for the FAQ thread? I suppose I could just find them in the forums (I keep coming across your posts with good answers) but it would take me forever to find all of them. And when I do find them would you mind if I posted the info as a FAQ with credit to you and your team?

---

Moderator9
ROSETTA@home FAQ
Moderator Contact

Can I get you to start submitting some of these as FAQs for the FAQ thread? I suppose I could just find them in the forums (I keep coming across your posts with good answers) but it would take me forever to find all of them. And when I do find them would you mind if I posted the info as a FAQ with credit to you and your team?

I don't have any unique thoughts, everything I know came from others. Feel free to take what you like. Since they aren't mine, you don't need to credit either me or my team. Most of my knowledge comes from being here a long time and especially Paul Bucks' Wiki. The answers are there for any who care to search.

I just like to help people, I did it for a job until my cancer, and now I don't work (psuedo retired) and get enjoyment from helping others this way.

tony

Also note that my suggestion to do the "file" "select computer" bit worked more frequently with V4 clients than it does with V5. The solution to 98% of these are to be found in the newer developmental versions of Boinc. But you need to be careful recommending those to people, since they do infact have bugs. It's a matter of the lesser of two evils. I don't do it frequently and only as a last resort.

Tony.
I've tried all your suggestions with no change in the situation. I use BOINC Manager version 5.2.13 although I have also tried the earlier version to see if it worked. Result was just the same - no connection to localhost. I have also added 127.0.0.1 IP address as a trusted address to my ZoneAlarm Pro firewall.
As regards the CMD routine using netstat -a the first image below shows the result with BOINC Client failed and the second image is the result with no BOINC Client started.

I figured you'd be back. Are you willing to try a developmental version of Boinc?? It has a bug which causes the incorrect display of the suspend function, but the correct display can be seen by exiting boinc and restarting boinc. otherwise I've had no trouble with this version. There can be other bugs and I want to make sure you understand that neither Boinc nor I am responsible for problems you may incurr with the use of this version.

Wanna try it? It's worked for others, and this fix should be include in the next Officially Recommended version. Note: I am currently using it on 4 or my 5 hosts ranging from Celeron 500 to AMD64 3700.

tony

Tony,
Happy to try anything to get back crunching again. Been with this project for nearly 5 months and would prefer not to have to change.

I currently run an Athlon64 3500+ based system, which is very rarely suspended but left to run 24/7.

How do I get the new version?

Here is Boinc V5.3.17 for WINDOWS. This IS a developmental version (the latest one). It contains bugs, use at your own risk, etc, etc, etc. This is a direct download from Berkeley and should start immediately. There is no need to uninstall the old version. you will need to reboot.

NOTE: this link is provided for Evodude. Don't think this is a quick fix for everyones problems. It is not. It's merely the lessor of two evils. it will use port 31416 instead of 1043.

let me know if it works for you.

You'll notice many different nomenclatures for things, like "no new work" is now "no new tasks" and others.

tony
[edit] and Oh yeah, I was talking about Project suspend, not work suspend being a bug in this version.

Tony,
Yep, Connected straight away to localhost and is currently downloading work units. Thanks for your assistance in this problem and I have added a positive rating to your previous posts in appreciation of your help and time given.

If no further problems, I'll come back here in a couple of days to update you on progress. Is there a seperate thread for posting any bugs found in this experimental version?

Is it possible to connect to Ralph on this one too, as I would like to help where I can?

Tony,
Yep, Connected straight away to localhost and is currently downloading work units. Thanks for your assistance in this problem and I have added a positive rating to your previous posts in appreciation of your help and time given.

If no further problems, I'll come back here in a couple of days to update you on progress. Is there a seperate thread for posting any bugs found in this experimental version?

Is it possible to connect to Ralph on this one too, as I would like to help where I can?

That version will do what the other do. Boinc in continually under improvement and so the next official version should be like the one you have "minus" bugs +additional "features".

As for Reporting bugs, boinc uses a "mail list" to communicate between the developement and alpha testers. by subscribing to the mail lists you get to see everything that's going on "behind the scenes". It's usually about 8-10 emails a day or there abouts. You can find the "Alpha testters" mail list here and the Development branch mail list here. There is also an official "Bugbase" called Boinczilla for the reporting of bugs.

You should be fine

good luck

tony

That version will do what the other do. Boinc in continually under improvement and so the next official version should be like the one you have "minus" bugs +additional "features".

good luck

tony

Tony
Dues this mean that the BUGS will become "additional features"
Ray

---

Pizza@Home Rays Place Rays place Forums

That version will do what the other do. Boinc in continually under improvement and so the next official version should be like the one you have "minus" bugs +additional "features".

good luck

tony

Tony
Dues this mean that the BUGS will become "additional features"
Ray

Welllllllllll, it's a matter of perspective. LOL Some may consider crashing your system is a bug, but then some may like it. LOL

---

The experimental BOINC Client is still working faultlessly for me but I've got a couple of questions.

#1. It seems to take a very long time to run a work unit. Using previous client I would complete a WU in under an hour but WU's on new client are taking over 7 hours to complete. Are they different WU's or is this a problem with new client?

#2. I've added Ralph@home to my project list with a 50/50 split. It intitially switched but after the first hour it switched back to rosetta@home and has not switched again. That was a couple of days ago.

---

Default CPU time for WU is now 8 hours....go to your Rosetta prefs where there is now a facility to set your WU CPU run times....it's great!

---

Evodude, you upgraded to the new client at the same time they released the new app and changed the preferences. It's the new science app/prefs, not the new client. I run 15 projects and can say that I've not seen it take longer, remember the CC (boinc core client) doesn't do any science, and doesn't use hardly any processor time, so it shouldn't affect runtimes.

tony

Tony if you have not changed your Rosetta prefs and left as they were then they WILL default to the default setting of CPU time, which was 8 hours. This explains why Evo's WU started to run for over 7 hours.....

Tony if you have not changed your Rosetta prefs and left as they were then they WILL default to the default setting of CPU time, which was 8 hours. This explains why Evo's WU started to run for over 7 hours.....

yes, indeed it would.