| Index | Recent Threads | Unanswered Threads | Who's Active | Guidelines | Search |
 |
World Community Grid Forums
Category: Support
Forum: BOINC Agent Support
Thread: Cant connect to localhost |
| No member browsing this thread |
|
Thread Status: Active Total posts in this thread: 6
|
|
| Author |
|
|
Former Member
Cruncher Joined: May 22, 2018 Post Count: 0 Status: Offline |
I recently made some changes in services.msc.
I stopped UPnP Device Host and SSDP Discovery manually to overcome issues with another program. In the same action, it seemed that my BOINC Manager disconnected and wont connect again. I have tried undoing the changes, manually start BOINC in services.msc, repairing the software, uninstalling and reinstalling the software, restarting computer, nothing seems to get things rolling again! Any ideas on how to fix this? |
||
|
|
sk..
Master Cruncher http://s17.rimg.info/ccb5d62bd3e856cc0d1df9b0ee2f7f6a.gif Joined: Mar 22, 2007 Post Count: 2324 Status: Offline Project Badges: 
|
Sounds like one of the services you stopped has dependencies including Boinc. Stopping Universal Plug and Play most likely (and hardly recommended). Trawl down the list and manually start UPnP and SSDP, and double check you didn't turn anything else off. System restart may be required to force changes.
Did you try going back to a system restore point/Last known good configuration? |
||
|
|
desmond-clarkson
Cruncher Joined: Dec 17, 2005 Post Count: 1 Status: Offline |
I'm having similar problem. I don't know if BOINC is IPv6-aware. If not, it may be seeing ipv6 connection first and failing to connect to thru it.
|
||
|
|
Former Member
Cruncher Joined: May 22, 2018 Post Count: 0 Status: Offline |
The sparseness of information in your message makes it quite unclear why you think the BOINC manager cannot connect to the core client over localhost IP 127.0.0.1 port 31416. Very frequent it's just missing permissions or a Firewall that blocks the connection.
As for IPv6, that has been supported for longer by BOINC, since 2008 is my reading. --//-- |
||
|
|
Former Member
Cruncher Joined: May 22, 2018 Post Count: 0 Status: Offline |
Cant connect to localhost
------------------------------------------------------------------------------------------------------------------------ I recently made some changes in services.msc. I stopped UPnP Device Host and SSDP Discovery manually to overcome issues with another program. In the same action, it seemed that my BOINC Manager disconnected and wont connect again. I have tried undoing the changes, manually start BOINC in services.msc, repairing the software, uninstalling and reinstalling the software, restarting computer, nothing seems to get things rolling again! Any ideas on how to fix this? Other than using restore point...I don`t want to have to install tons of software again. It`s not lacking permissions in routers and not being blocked by firewalls either. If anyone ever had this problem, and got it solved, feedback would be highly appreciated. Or if anyone with some technical insight might have some suggestions, I`d be happy to try! [Edit 1 times, last edit by Former Member at Dec 29, 2011 6:14:28 PM] |
||
|
|
Former Member
Cruncher Joined: May 22, 2018 Post Count: 0 Status: Offline |
I know of two things that can cause this, I don't know if your problem is the same.
* When editing remote_hosts.cfg and/or gui_rpc_auth.cfg (to allow another computer to connect), it blocks the localhost manager. I fixed it by adding '127.0.0.1' to remote_hosts.cfg. (On Linux I also need to select "advanced > connect to computer" from the Boinc Manager menu and type 127.0.0.1 instead of localhost, on Win 7 I apparently don't need to do that.) * When the boinc-client service isn't running. Boinc is two parts, boinc-client ("boinc.exe *32" in the Task Manager process list) and boinc-manager (the GUI, "boincmgr.exe" in Task Manager). Check that the boinc client is running, see if you can start it manually if it isn't. As for how UPnP and SSDP relates to this, I have no idea. |
||
|
|
|