I have installed the program Boincview and it works with direct access. I then tried to change it for network access according to the installation procedure in Boinc Wiki. I have carefully changed everything according to the instruction, but how I try I don't get the message Remote Control Allowed after stop and start of Boinc. I'm running boinc as a daemon.

---

Based on the error you reported, you have not created the remote_hosts.cfg and the gui_rpc_auth.cfg files correctly.

1) They have to go in the DATA directory of the computer to be controlled, not the execuabeles directory. The data directory is listed at BOINC startup.

2) gui_rpc_auth.cfg contains a single line with the password. The password must match betweek this file and BV.

3) gui_rpc_auth.cfg contains a list of IP addresses or machine names one per line as follows:

10.192.168.4
foo
berntsbox

Would allow access to that BOINC installation from any machine that had the IP address 10.192.168.4 no matter what it was named, and the machines named foo and berntsbox no matter what IP they had.

The next step is to coerce your firewalls to let the traffic through.
1) BOINC.exe must be allowed to act as a server for port 31416. It must have outbound access to ports 443 and 80 (https and http).
2) BOINCView.exe, BOINCmgr.exe, BOINCCmd.exe and possibly BOINC.scr will have to have outbound access on port 31416 to get to the machine to be controlled.
NOTE: 31416 should only be allowed on the LAN, and not the general internet.

---

BOINC WIKI

I have checked what you said carefully and the info is in the right library.
You said that the gui_rpc_auth should carry the info about the IP. I suppose this a small typing error. The remote_hosts.cfg = IP and gui_rpc_auth.cfg = password and so it is. Could there be anything else that can make this go wrong? Service that should be started for instance? Grateful for any help?

---

Does the remote access via BOINC manager (Advanced menu/Select computer...) work?

The remote_hosts.cfg and the gui_rpc_auth.cfg files must be on every host.

For your convenience, the password on each host can be the same.

Gruß,
Gundolf

---

Computer sind nicht alles im Leben. (Kleiner Scherz)

SETI@home classic workunits 3,758
SETI@home classic CPU time 66,520 hours

Gundolf,

No it does not work to select an other pc in boincmanager. I have tried that as well, but in vain.

I can see all of them in the network and accessright is correct. Via the explorer everything is ok. I created the same user with the same rights on each PC to make it simple.

I found a very good instruction in Boinc Wiki how to do this. I followed it very carefully as I already said.

Bernt

---

Are there any error messages if you try to "Select computer..."?

See also in the file stdoutgui.txt

Gruß,
Gundolf

Voila,

18:45:21: Error: can't open file 'C:\Program Files\BOINC\\RebootPending.txt' (error 2: the system cannot find the file specified.)
[03/04/09 18:45:22] TRACE [1052]: RPC_CLIENT::init boinc_socket returned 352

[03/04/09 18:45:23] TRACE [1052]: RPC_CLIENT::init connect returned -1

[03/04/09 18:45:23] TRACE [1052]: RPC_CLIENT::init attempting connect

[03/04/09 18:45:23] TRACE [1052]: RPC_CLIENT::init_poll sock = 352

[03/04/09 18:45:23] TRACE [1052]: RPC_CLIENT::init_poll connected to port 31416

[03/04/09 18:45:23] TRACE [1052]: CAN'T FIND PROJECT http://setiathome.berkeley.edu/

[03/04/09 18:45:30] TRACE [1052]: RPC_CLIENT::init boinc_socket returned 352

[03/04/09 18:45:30] TRACE [1052]: RPC_CLIENT::init connect returned -1

[03/04/09 18:45:30] TRACE [1052]: RPC_CLIENT::init attempting connect

[03/04/09 18:45:30] TRACE [1052]: RPC_CLIENT::init_poll sock = 352

[03/04/09 18:45:30] TRACE [1052]: RPC_CLIENT::init_poll sock = 352

[03/04/09 18:45:31] TRACE [1052]: RPC_CLIENT::init_poll sock = 352

[03/04/09 18:45:31] TRACE [1052]: RPC_CLIENT::init_poll sock = 352

[03/04/09 18:45:31] TRACE [1052]: RPC_CLIENT::init_poll sock = 352

[03/04/09 18:45:31] TRACE [1052]: RPC_CLIENT::init_poll sock = 352

[03/04/09 18:45:32] TRACE [1052]: RPC_CLIENT::init_poll sock = 352

[03/04/09 18:45:32] TRACE [1052]: RPC_CLIENT::init_poll sock = 352

[03/04/09 18:45:32] TRACE [1052]: RPC_CLIENT::init_poll sock = 352

[03/04/09 18:45:32] TRACE [1052]: RPC_CLIENT::init_poll sock = 352

[03/04/09 18:45:33] TRACE [1052]: RPC_CLIENT::init_poll sock = 352

[03/04/09 18:45:33] TRACE [1052]: RPC_CLIENT::init_poll sock = 352

[03/04/09 18:45:33] TRACE [1052]: RPC_CLIENT::init_poll sock = 352

[03/04/09 18:45:33] TRACE [1052]: RPC_CLIENT::init_poll sock = 352

[03/04/09 18:45:34] TRACE [1052]: RPC_CLIENT::init_poll sock = 352

Some nice output after change to 192.168.0.3 via the menu in boincmanager.

Can you find anything in this Gundolf?

Bernt

---

[03/04/09 18:45:23] TRACE [1052]: RPC_CLIENT::init attempting connect

[03/04/09 18:45:23] TRACE [1052]: RPC_CLIENT::init_poll sock = 352

[03/04/09 18:45:23] TRACE [1052]: RPC_CLIENT::init_poll connected to port 31416

[03/04/09 18:45:23] TRACE [1052]: CAN'T FIND PROJECT http://setiathome.berkeley.edu/

[03/04/09 18:45:30] TRACE [1052]: RPC_CLIENT::init boinc_socket returned 352

[03/04/09 18:45:30] TRACE [1052]: RPC_CLIENT::init connect returned -1
...
Some nice output after change to 192.168.0.3 via the menu in boincmanager.

Can you find anything in this Gundolf?

Bernt

Me surely not! I have no knowledge about this, but perhaps others can help.

I suppose 352 is an error number, since I got 440 after giving a wrong password:

[03/01/09 20:08:16] TRACE [424]: RPC_CLIENT::init boinc_socket returned 440

but I don't know what it means.

Gruß,
Gundolf

---

Computer sind nicht alles im Leben. (Kleiner Scherz)

SETI@home classic workunits 3,758
SETI@home classic CPU time 66,520 hours

Gundolf,

You are surely right. I guess 352 means RPC not activated, it is just a wild guess.

Bernt

---

No, they're not error codes. They are socket ID numbers.

In bernt's example you can see what's happening:

[03/04/09 18:45:23] TRACE [1052]: RPC_CLIENT::init_poll sock = 352 --> tells which socket ID to use.

[03/04/09 18:45:23] TRACE [1052]: RPC_CLIENT::init_poll connected to port 31416 --> connection to BM made.

[03/04/09 18:45:30] TRACE [1052]: RPC_CLIENT::init boinc_socket returned 352 -> checking if we're still on socket 352.

[03/04/09 18:45:30] TRACE [1052]: RPC_CLIENT::init connect returned -1 --> yes we are.

---

Ageless,

Appreciate your explanation. I would be even more happy if you can explain why I can't connect via the boincmanager interface to a computer on my LAN. I have tried almost everything to make this correct so I am very happy to anyone who can give my some guidance.

Bernt

---

I explained the how to in this post for a Mac user. It is the same under Windows.

if that doesn't work, then make sure that your firewall allows for all parts of BOINc to communicate with each other.

---

Case closed

Thanks for the help

Bernt

---