Questions and Answers :
Web site :
Can not access remote BOINC client
Message board moderation
Author | Message |
---|---|
didi Send message Joined: 3 Jan 02 Posts: 2 Credit: 348,975 RAC: 0 |
After updating the boinc manager from 5.xy to 6.10.43 on my windows pc, I cannot access the client on the linux machine (boinc 5.2.7) gui_rpc_auth.cfg and remote_hosts.cfg exists. |
Jord Send message Joined: 9 Jun 99 Posts: 15184 Credit: 4,362,181 RAC: 3 |
Not sure, but didn't 5.2.7 use the old TCP port 1043 to communicate with the client and only switch to 31416 when the primary port was already taken? BOINC 6 uses only TCP port 31416. You can run the BOINC binary with the --gui_rpc_port <port> flag, where <port> is any value you want to give it. Default on BOINC 6 is 31416, default on 5.2.7 is 1043 with fall-back option of 31416. Is there any reason you can't update the Linux system to a later version of BOINC? The 5.10 range also uses only 31416. |
didi Send message Joined: 3 Jan 02 Posts: 2 Credit: 348,975 RAC: 0 |
OK, thats it. The "-gui_rpc_port <port>" flag is not a possible flag for boinc 5.2.7, but on my winsows machine with boinc 6.10.43 I have selected "MyLinuxBox:1043" as remote computer name and it works. thanks for this help. Didi |
John McLeod VII Send message Joined: 15 Jul 99 Posts: 24806 Credit: 790,712 RAC: 0 |
OK, thats it. The "-gui_rpc_port <port>" flag is not a possible flag for boinc 5.2.7, but on my winsows machine with boinc 6.10.43 I have selected "MyLinuxBox:1043" as remote computer name and it works. OK, didn't know that would work. BOINC WIKI |
©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.