I have been using BIONIC for several weeks on three computers. Now my primary computer is "BIONIC mamager is unable to connect to BIONIC client." My other two computers are working fine.

What am I doing wrong?

---

Have you tried entering "localhost" in "file -> choose computer"?

---

Have you tried entering "localhost" in "file -> choose computer"?

I do have the same problem.
Entering "localhost" doesn't solve it.

THere is no one answer to these problems, as you will find browsing this forum. For example, see this thread. Try the simple things first, though.

1. Close BOINC Manager with File/exit (don't just close the window). Then restart BOINC Manager manually. If that fixes it, remove BOINC from your startup folder and remember to start BOINC yourself after booting.

2. If that is no good, remove BOINC from startup and reboot, then start BOINC.

If those fail, you might like to read some old threads on this and try some of the things suggested. But by all means come back for further help.

---

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.
When all screens in Boinc Manager are blank, check that Boinc.exe is running. In Windows NT/2k/XP, rightclick on the Windows taskbar and choose Task Manager. Go to the processes tab and check if Boinc.exe is running. Check how many versions of Boincmgr.exe there are running.
If more than 2 of the latter, close them all down and restart one.
If Boinc.exe isn't running, please try a reboot of the computer first.
Close down BOINC.
Navigate to your Boinc directory.
Find the file called gui_rpc_auth.cfg, open it up with a word processor and delete password, then put a blank space followed by a carriage return, save file.
Then restart BOINC.
That will most probably fix it.

---

BOINC Wiki

I tried the suggested blank/carraige return modification to gui_rpc_auth.cfg and got an incorrect password error but it was on the right track. I then tried deleting the blank and carriage return leaving a completely null file. That worked. Thanks for the direction.

---

The other day, boinc was not connecting to localhost, I do not know why. I am also having an issue with streaming video with WMediaplayer, it would crash IE, or Firefox, or whatever. I talked to tech support at a site that I pay for media support, and they had me dl a codec pack for WMediaplayer 7+ and I ran that. Oddly, it did NOT fix the streaming problem, but suddenly, my boinc was connecting with no issue. So, I ignored it. Recently, however, I had to do a system restore for yet another WMP issue, and though I fixed that issue, now boinc won't connect again. I reinstalled the codec pack again, figuring "why not?" and it didn't do anything this time. I have tried all suggestions in this thread so far, and nothing does it. One time, oddly, it DID connect for like 5 seconds, I had all my projects listed and everything, but then it went away again. Seriously, this is getting annoying. If I don't get this fixed, I'm going to find out how to migrate my work files from this comp over to my other comp and just run everything from there, instead of both places. I get tired of aggravation without resolution.
So, is there ANYONE that can honestly fix this issue?

---

like to help, that's me!

Update.
More playing around made me find something. When I used a command window to run boinc.exe, I could connect. AS LONG AS I LEFT THE COMMAND WINDOW OPEN! As soon as I closed that window, boinc.exe stopped running. If I tried to run boinc.exe using the "run" command line, it openned a command window and left it open, and if I closed it, blammo! Boinc.exe stopped running. THIS is why I am not connecting! But why is boinc.exe not running in the background? What's the issue, that's the new question. I do have norton AV, but have boinc.exe in program exclusions, so it should be untouched. MS Antispyware also has always ignored it in the past. Any ideas??

Jindai

---

like to help, that's me!

But why is boinc.exe not running in the background? What's the issue, that's the new question.

Try running boinc.exe using the -redirectio flag. ;-)

For example:

"C:\\Program Files\\BOINC\\boinc.exe" -redirectio

The command window will be hidden. :-)

I have tried all of the suggestions and am at a loss. I will keep monitoring this Message board for other suggestions.

---

But why is boinc.exe not running in the background? What's the issue, that's the new question.

Try running boinc.exe using the -redirectio flag. ;-)

For example:

"C:\\Program Files\\BOINC\\boinc.exe" -redirectio

The command window will be hidden. :-)

Actually, the command window did come up, but remained blank. I closed it, checked my task manager and boinc.exe was still running. So it DID work, anyway. Thanks

---

like to help, that's me!

Your system has lost it's port connection and is no longer attached to "localhost". There are a few things you can try:

1) do a cold boot (not just restart)
2) click "file", "select computer", leave both boxes blank, click "ok"
3) click "file", "select computer", type in LOCALHOST, leave password blank, click "OK"
4) click "file", "select computer", type in 127.0.0.1, leave pasword blank, click "OK".
5) check software firewall to make sure both Boinc.exe and Boincmgr.exe have full access (also that Boinc.scr has outbound access if using the screensaver).

If this doesn't work there is more we can try.

Boinc 5.2.15 and earlier uses port 1043 as a loopback address so that the daemon can talk to the manager. This is what's NOT happening.

let me know

tony

I am having the same issue as well. I tried all the suggestions in the posts and I am still having the problem.

---

I am having the same issue as well. I tried all the suggestions in the posts and I am still having the problem.

Craig, what version of boinc are you using? Did you install as "single user", "Shared user", or "Service".

Open a command prompt window (start, all programs, accessories, then select "command prompt")

type in "netstat -a" (without quotation marks)

you should see 3 entries containing port 1043 or 31416. One should say "listening" the others should say "Established" and the port numbers should point to one another in a loopback fashion.

do you see this?

Are you a windows user?
Are you willing to try a developmental version?

Boinc had been assigned port 1043 from ICANN, Microsoft still used this port on some software and it's causing trouble. Rather than Fight MS Boinc has requested and is using port 31416 on new developemental versions of Boinc as a fix for the few affected users.

WARNING
Developemental version have bugs of one kind or another and are developemental for that reason. the Alpha testers are currently finding the flaws they can before these clients are released to the public a "recommended" clients.

I'm NOT an employee of Berkeley, do not hold them accountable for any bad things that may happen.

That being said I'm running the software without any large issues occuring.

---

Boinc Wiki

Sometimes I hate my Bob Newhart style of humor.

I don't see any of those ports open at all. Weird. This just started hapening yesterday. I am using 5.2.13 and I would be happy to try a developmental version.

---

I don't see any of those ports open at all. Weird. This just started hapening yesterday. I am using 5.2.13 and I would be happy to try a developmental version.

Which OS?

I don't see any of those ports open at all. Weird. This just started hapening yesterday. I am using 5.2.13 and I would be happy to try a developmental version.

Which OS?

Windows XP SP2.

---

Boinc V5.3.17 for WINDOWS.

This is a direct download and it should start immediately upon clicking it. It uses port 31416 and should fix your issue. NOTE: The display of project suspend does not work properly. The actual suspsend/unsuspend works it's just how it's displayed that is wrong. To fix it just exit boinc and restart when you suspend or unsuspend.

let me know

tony

[edit] see warning four posts up/down.

Side note:

If you go forwards in boinc numbers you do not need to use "add/remove programs" to uninstall boinc. If you go backwards in numbers you do need to uninstall.

I say this for all who are watching so no work is lost in the process.

tony