Message boards : BOINC Manager : BOINC client does not bind to public interface in Windows
Message board moderation
Author | Message |
---|---|
Send message Joined: 13 Jun 06 Posts: 2 |
Hey. I am trying to get my Windows client to bind to 192.168.1.3:31416. I have specified '-allow_remote_gui_rpc' as the start paramaters from the Services panel. I started the service, but when I looked at netstat, it only showed that 127.0.0.1 was bound. Does anyone know what is wrong (I am using version 5.4.9)? I can connect to localhost successfully and have allowed the port in Windows firewall. |
Send message Joined: 13 Jun 06 Posts: 2 |
Hey. I am trying to get my Windows client to bind to 192.168.1.3:31416. I have specified '-allow_remote_gui_rpc' as the start paramaters from the Services panel. I started the service, but when I looked at netstat, it only showed that 127.0.0.1 was bound. Does anyone know what is wrong (I am using version 5.4.9)? I can connect to localhost successfully and have allowed the port in Windows firewall. Using a nasty registry hack, I fixed the problem. I edited HKEY_LOCAL_MACHINE\\Services\\CurrentControlSet\\BOINC\\ImagePath and just appended '-allow_remote_gui_rpc' to the end. |
Send message Joined: 29 Aug 05 Posts: 15561 |
I think you are trying to control a PC remotely? You followed all of these steps? By default, when you start Boinc Manager, the Boinc client you are using is running on the computer you run it from, and that one is localhost (127.0.0.1). If you want to reach any other PC in the remote_hosts.cfg list, you go Advanced, Select computer, fill in IP address and password of that computer and click OK. |
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.