Message boards : BOINC Manager : Not connecting
Message board moderation
Author | Message |
---|---|
Send message Joined: 1 Sep 05 Posts: 3 |
Now when I start up boinc it says connection failed, anyone else having this prob with this thing that wont let me do anything. Wish we still had the old stand alone program. I have had nothing but trouble with this since I installed it. pigfairy |
Send message Joined: 30 Aug 05 Posts: 25 |
where are you getting this error message? What is the exact error message? What kind of install did you do? etc... |
Send message Joined: 1 Sep 05 Posts: 3 |
the message says "connection failed" worked kinda ok for a week, but seti doesnt upload. And yes its connected to the internet, or you wouldnt see this reply. pigfairy |
Send message Joined: 29 Aug 05 Posts: 15570 |
More information please. In the mean time do look if this is the error you see and if it is, then please tell us how you are connected, how you set Boinc up, if you are behind a firewall, if you have permission to go through said firewall. The more information you give us, the better we can help you. So, always give your Boinc version and OS to start with. Try answering all the questions that people ask you. If I give you 7 questions and you only answer 1 of them, how can I or anyone further help you? |
Send message Joined: 1 Sep 05 Posts: 3 |
OK, call me a fool, its the first thing I should have done......reboot. Everything is working fine now. Thanks for your time sorry I wasted it. Next time like a smart user I will reboot first then ask questions. again thanks pigfairy |
Send message Joined: 24 Sep 05 Posts: 7 |
Now when I start up boinc it says connection failed, anyone else having this prob with this thing that wont let me do anything. Wish we still had the old stand alone program. I have had nothing but trouble with this since I installed it. |
Send message Joined: 24 Sep 05 Posts: 7 |
I just re-installed (in fact I have removed and re-installed a couple of times) and everytime I try and start BOINC I get a pop-up window titled "BOINC Manager - Connection failed.". The text of the pop-up window says "Connection failed." I'm running with a cable modem connection. Are there ports that need to be opened up or something? |
Send message Joined: 7 Sep 05 Posts: 4 |
I had the same problem with Boinc. I solved it by creating the remote_hosts.cfg file and added a line that contains 127.0.0.1. Until now the problem never reappeared. |
Send message Joined: 29 Aug 05 Posts: 225 |
I just re-installed (in fact I have removed and re-installed a couple of times) and everytime I try and start BOINC I get a pop-up window titled "BOINC Manager - Connection failed.". The text of the pop-up window says "Connection failed." I'm running with a cable modem connection. Are there ports that need to be opened up or something? In SOME cases I have had the XP firewall interfering with this connection. So, I had to add the ports to the firewall as an exception. I found this surprising as most of the machines I run XP on were fine without this ... Also, on first start you may see this. Closing the manager and starting it again may clear that up. It seems to be a minor timing problem. |
Send message Joined: 24 Sep 05 Posts: 7 |
I had the same problem with Boinc. Hi. Thanks for the suggestion. Where do I put the remote_hosts.cfg file? I tried putting it in the BOINC directory but that didn't help any. |
Send message Joined: 24 Sep 05 Posts: 7 |
I just re-installed (in fact I have removed and re-installed a couple of times) and everytime I try and start BOINC I get a pop-up window titled "BOINC Manager - Connection failed.". The text of the pop-up window says "Connection failed." I'm running with a cable modem connection. Are there ports that need to be opened up or something? I have allowed the following exceptions in Windows Firewall: (program) C:\Program Files\BOINC\boincmgr.exe (program) C:\Program Files\BOINC\boinc-gui.exe (port) 1043 TCP (port) 1043 UDP I have closed and reopened the BOINC manager several times with no luck. |
Send message Joined: 24 Sep 05 Posts: 7 |
I have found out something. I went into the BOINC directory and double-clicked on boinc.exe. I got a command window and it looks like BOINC is doing work! I still can't get a connection with the BOINC manager window. |
Send message Joined: 7 Sep 05 Posts: 4 |
The remote_hosts.cfg must be put in the boinc directory, as you have done it. Please check if there is a line with "Remote control allowed" in the log when you start the boinc.exe. If not then boinc hasn't recognized the file. Be careful to put at least one empty line at the end of the file. You should add also the boinc.exe to the firewall exceptions. |
Send message Joined: 29 Aug 05 Posts: 225 |
You also have to stop and restart BOINC to have it see the remote hosts file. It is only read when the BOINC Daemon is started. If installed as a service you need to stop and restart the service. |
Send message Joined: 24 Sep 05 Posts: 7 |
I have removed BOINC, deleted the BOINC directory, re-installed BOINC, verified that remote_hosts.cfg is in the BOINC directory and that it has a blank line at the end, added boinc.exe to the firewall exceptions, and then rebooted. I still get "Connection failed". DarkGhost, are you referring to the log in BOINC Manager window? I'm not getting any log there. There are 2 files in the BOINC directoy titled stderrgui.txt and stdoutgui.txt in the BOINC directory. stderrgui.txt is empty and stdoutqui.txt has only " send: -1". |
Send message Joined: 7 Sep 05 Posts: 4 |
Hi, The logfiles for the Boinc deamon are named stderrdae.txt and stdoutdae.txt both located in the main directory. If you don't have them it is the same problem which is described in this Thread. The only good solution seams to be a downgrad to version 4.19 |
Send message Joined: 24 Sep 05 Posts: 7 |
Hi, I downloaded 4.19, removed 4.45, deleted the BOINC directory, rebooted, installed 4.19. Works great. Go figure. Hey, DarkGhost and Paul Buck, Thanks a bunch for your help!!! I am now crunching numbers. Wayne |
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.