BoincView

Author	Message
Ron Volunteer tester Send message Joined: 16 Sep 99 Posts: 47 Credit: 3,900,704 RAC: 0	Message 95693 - Posted: 6 Apr 2005, 19:30:17 UTC Last modified: 6 Apr 2005, 19:31:44 UTC I'm trying to use BoincView on a LAN. I don't want to share folders, so was hoping to use the update mode within BoincView of "via network access (using GUI RPC)". When I try to connect to client (which definily has BOINC running), I get an error "There seems to be no BOINC client behind port 1043. Use port anyway?". Even if I say yes to the error, it does not work and does not connect. Any thoughts? P.S. I've tried connecting to a few different clients, and get the same error. <br><br><img src='http://www.boincsynergy.com/images/stats/1185sah.png'> <br> Thanks to Tim (Captain Avatar) for my groovy Red Foxx avatar! ID: 95693 ·

Cerberus Send message Joined: 3 Apr 99 Posts: 12 Credit: 3,064,488 RAC: 0	Message 95700 - Posted: 6 Apr 2005, 20:21:08 UTC - in response to Message 95693. Last modified: 6 Apr 2005, 20:30:18 UTC > I'm trying to use BoincView on a LAN. I don't want to share folders, so was > hoping to use the update mode within BoincView of "via network access (using > GUI RPC)". When I try to connect to client (which definily has BOINC > running), I get an error "There seems to be no BOINC client behind port 1043. > Use port anyway?". Even if I say yes to the error, it does not work and does > not connect. Any thoughts? > > P.S. I've tried connecting to a few different clients, and get the same error. > You will have to enable the gui_rpc access for each client and this feature only works for Linux and Windows clients (no mac functionality/access (yet)). Create a file in each BOINC install folder called remote_hosts.cfg. Inside, listed one ip (or host name) per line is the hosts that this client will allow to conenct to it. Restart that client (each client) and you will be able to use boincview via port 1043. ID: 95700 ·

Paul D. Buck Volunteer tester Send message Joined: 19 Jul 00 Posts: 3898 Credit: 1,158,042 RAC: 0	Message 95717 - Posted: 6 Apr 2005, 21:20:04 UTC - in response to Message 95700. > You will have to enable the gui_rpc access for each client and this feature > only works for Linux and Windows clients (no mac functionality/access (yet)). > > Create a file in each BOINC install folder called remote_hosts.cfg. Inside, > listed one ip (or host name) per line is the hosts that this client will allow > to conenct to it. Restart that client (each client) and you will be able to > use boincview via port 1043. Well, um, no ... I use BOINC View to see my Mac all the time ... just add the same hosts file and away you go ... You may have to add the port to the firewall's exception lists also ... ID: 95717 ·

Ron Volunteer tester Send message Joined: 16 Sep 99 Posts: 47 Credit: 3,900,704 RAC: 0	Message 95720 - Posted: 6 Apr 2005, 21:28:51 UTC - in response to Message 95700. Cool, thanks! <br><br><img src='http://www.boincsynergy.com/images/stats/1185sah.png'> <br> Thanks to Tim (Captain Avatar) for my groovy Red Foxx avatar! ID: 95720 ·

Dusty33 Volunteer tester Send message Joined: 16 Jul 01 Posts: 24 Credit: 3,368,100 RAC: 0	Message 95743 - Posted: 6 Apr 2005, 22:48:16 UTC Fred, You may be using the wrong version of boincview with your boinc applications. If you have boinc mgr 4.19 need to run boincview 0.9.2.d If you have boinc mgr 4.25 or newer need to run boincview 1.0.0 or newer. The difference is they use different ports to communicate with, BV 0.9.2.d uses port 31416 for boinc mgr 4.19. BV 1.0.0 and higher uses port 1043 for boinc mgr 4.25 and up. Dusty ID: 95743 ·

©2024 University of California

SETI@home and Astropulse are funded by grants from the National Science Foundation, NASA, and donations from SETI@home volunteers. AstroPulse is funded in part by the NSF through grant AST-0307956.