It's been a few years since I used that program but from what I remember...

You must have a guirpc.cfg file (with the IP address or HOST NAME of the Remote Monitor PC's -- each on a separate line) on each PC you have BOINC running on... It goes in the BOINC DATA FOLDER.

You also might have to allow the program access through your firewall on the PC it's installed on and possibly on each "remote" PC BOINC runs on.

Why not consider using eFMer's BOINCTasks? It is far better and more up to date and can access just about all the "tools"/menu's in the current BOINC version.

---

I have a couple of Parallella's (they run Ubuntu) and a few Raspberry Pi's (they run Debian). I use BOINCtasks with them. While BOINCview will work it can't do half of what BT can do.

From what I gather the author of BV passed away so it hasn't been updated and the source code was not made available.

To manage machines via either one you'll need to setup a gui_rpc_auth.cfg and remote_hosts.cfg. They go in the BOINC data folder. The remote_hosts tells it which computers (or IP addesses) are allowed and the gui_rpc_auth has a password, although it can be blank. You need to set the same password in BV or BT when you configure the computers that its going to control.

If you have a firewall configured on your number crunchers you'll need to allow the BT machine through.

---

BOINC blog

Do you know if ... allow permissions to access the the File for the Project to be monitored by another PC ...

All three of the main visualisation tools for BOINC - BOINCTasks, BoincView, and BOINC Manager itself - use the same protocols as described in Controlling BOINC remotely: none of them require any direct access to the file system on the remote computer (although that can be handy for other purposes).

No special changes need to be made on the central computer running BOINC Tasks/View: all permissions need to be set on the remote computers you wish to monitor.

These are:

Set (or record) a memorable password in gui_rpc_auth.cfg
Put details of the monitoring computer in remote_hosts.cfg (new file)
Allow boinc.exe to communicate through any firewall software (Windows firewall or possibly a component of your anti-virus software)

I prefer it over BOINCTasks as does continuously switch to the task view when I am looking at the hosts info & it is much more responsive in getting the number of tasks on each host.

I just use <allow_remote_gui_rpc>1</allow_remote_gui_rpc> in my cc_config.xml. Rather than enter every IP address on my network as remote hosts. Once a gui_rpc_auth.cfg, cc_config.xml settings & firewall settings are configured BOINCView is ready to go. Personally I don't bother with a highly secure password in my gui_rpc_auth.cfg. As I don't have the ports for BOINC open in my routers.

If you do that then you can select the 2nd radial button that says "Get data via network access" instead of "Get data via direct file access".

---

SETI@home classic workunits: 93,865 CPU time: 863,447 hours
Join the [url=http://tinyurl.com/8y46zvu]BP6/VP6 User Group[