How do I get this to work? I keep getting "GUI RPC request from non-allowed address" from my Boinc clients.

---

On each of your systems you need to create the file <b>remote_hosts.cfg</b> in the BOINC installation directory. All it needs to contain is the name (or IP address) of the system you're running BoincView on. You need to restart BOINC on the remote systems to make if read the new file.

You could run BOINC with the command line option <b>-allow_remote_gui_rpc</b> instead, but that'll allow connections from any system with access to the port used for GUI RPC. I opened up port 31416 on one of my systems just to see what happened, and it wasn't long before it rejected an attempted connection from an external system. So I'd advise going for the file option ;)

---

"The ultimate test of a moral society is the kind of world that it leaves to its children." - Dietrich Bonhoeffer

Thank you very much...and, do you guys ever sleep? I'm not used to getting responses for anything in 32 minutes. Wow!

---

Please double check this but,
I found a virus in one of the add-on folders; don't use any anymore.
:(

---

-----------------------
Click to see my tag
<a href="http://boinc.mundayweb.com/one/stats.php?userID=1049">My tag</a>
SNAFU'ed? Turn the Page! :D

&gt; Please double check this but,
&gt; I found a virus in one of the add-on folders; don't use any anymore.
&gt; :(
&gt;
What add-on folder? For BOINCView?

&gt; On each of your systems you need to create the file <b>remote_hosts.cfg</b> in
&gt; the BOINC installation directory. All it needs to contain is the name (or IP
&gt; address) of the system you're running BoincView on. You need to restart BOINC
&gt; on the remote systems to make if read the new file.
&gt;
&gt; You could run BOINC with the command line option <b>-allow_remote_gui_rpc</b>
&gt; instead, but that'll allow connections from any system with access to the port
&gt; used for GUI RPC. I opened up port 31416 on one of my systems just to see
&gt; what happened, and it wasn't long before it rejected an attempted connection
&gt; from an external system. So I'd advise going for the file option ;)
&gt;

I created the .cfg file as instructed with the IP of the monitoring station but no werkie. I still get the same non-allowed IP error. The file contains 192.168.1.53 only. I am connecting Ok using port 31416 so what am I missing here?

I am running this on 96 processors and desperately need a way to monitor them.

Thanks
Joe

---

Probably not the problem but - BoincView 0.9.2d works with BOINC 4.19 and lower, BoincView 1.0.x works with Boinc 4.25+
Putting an IP of BoincView machine in remote_hosts.cfg and running boinc_gui.exe worked fine for me...

---

<i>phpBB forum for CPDN, all are </i><a href="http://www.climateprediction.net/board">invited</a>

&gt; I created the .cfg file as instructed with the IP of the monitoring station
&gt; but no werkie. I still get the same non-allowed IP error. The file contains
&gt; 192.168.1.53 only. I am connecting Ok using port 31416 so what am I missing
&gt; here?

You probably aren't missing anything Joe. I'm running 11 systems, all set up identically. BoincView works fine with 10 of them but the other one refuses to play ball. I suspect something else might be using port 31416 on that system, but I haven't bothered to investigate any further as only one system is affected.

---

"The ultimate test of a moral society is the kind of world that it leaves to its children." - Dietrich Bonhoeffer

The port number changed with the 4.2x clients it is now 1043. Unfortunately there is another app that uses this port so the 4.28 client should allow both ports when it comes out.

---

BOINC WIKI

BOINCing since 2002/12/8

I downloaded the 1.02.9D Beta version and all is working now. Thanks all for the tips.

---