Message boards : BOINC Manager : File.SelectComputer - Connection Failure
Message board moderation
Previous · 1 · 2
Author | Message |
---|---|
Send message Joined: 24 Nov 05 Posts: 1 |
Here's my contribution for a first version of a HowTo for remote client access. If you find it adequate, then feel free to add it to the BOINC Wiki. How to control BOINC on remote computers Once you installed BOINC on a computer, it is possible to control and manage the [[BOINC Daemon]] from another computer connected via a network link. You can either use [[BOINC Manager]] or [http://boinc.berkeley.edu/boinc_cmd.php BOINC command tool] for this purpose. =Preparations= In the [[BOINC Directory]] of the remote computer, do the following: # Allow remote access by creating or editing the [[Remote Hosts File]] (remote_hosts.cfg). # Create or edit a [[BOINC Daemon Password]] in file gui_rpc_auth.cfg. # Restart the BOINC Daemon of the remote computer to make it aware of the changes. ==With BOINC Manager== * Open the ''File'' menu and select the menu entry ''Select computer...'' * Enter the hostname or [[IP address]] of the computer you want to access remotely. * Enter the password that is set in the [[BOINC Daemon Password]] file gui_rpc_auth.cfg on that remote computer. * Now you can use BOINC Manager as usual. The difference is that all commands are sent to the remote computer now. * To switch back to the local computer, repeat the steps listed in this section but enter hostname 'localhost' and the password set in the local [[BOINC Daemon Password]] file. ==With BOINC command tool== * For each command that you specify with the BOINC command tool, add the options ''--host hostname[:port]'' and ''--passwd password''. You can omit the password option; in this case, the password in the local gui_rpc_auth.cfg file will be used. By the way, menu entry ''Select computer...'' of menu ''File'' is not mentioned in the current Wiki page for BOINC Manager. I'd suggest to add in section 'BOINC Manager Menus' at least a line such as this: * Select computer: Connect to a [[BOINC Daemon]] which runs on a remote computer |
Send message Joined: 29 Aug 05 Posts: 225 |
Marck, Thanks I added your procedure. minor changes, but, a good start. The whole BOINC Application Owner's Manual is out of date, but I have not been able to do the work to update it. My current plan, when I can is to make the current manual current to 4.72 with a newer version for 5.x.y; send me some health .. :) |
Send message Joined: 10 Jan 06 Posts: 15 |
On the File - Select Computer, it might be worth pointing out a few things that novice computer users might not be aware of. Somewhere in the passwords section, that passwords are case sensitive. (My cat keeps stepping on the Caps Lock key.) That: With DHCP routers, the IP address of local computers may change after being powered off. (This may cause a lot of confusion after a power failure or the next day, when their list of IP to passwords no longer works, because a machines IP address has changed.) That: On Windows systems it is required that the default Networking settings for File Sharing and the Client for Microsoft Networks with its default TCP/IP Bindings be enabled if using the "Computer Name" instead of IP address. (Some security recommendations have you unbind the TCP/IP for your Internet connection from the Client for Microsoft Networks, and to disable File Sharing.) That: On Windows systems, to remove an entry in the drop down MRU list of computer names or IP addresses, it is necessary to edit the Registry for HKCR\\Software\\Spaces Sciences Laboratory, U.C. Berkeley\\BOINC Manager\\ComputerMRU and delete old or incorrect entries. |
Send message Joined: 30 Aug 05 Posts: 101 |
I have several machines spread out around my home all running boinc. I would like to configure them so I can check on their status from a single machine. Boincview is very good, I highly recommend it. JOIN Team ACC |
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.