i think it worked without a hitch last night b/c both the host computer and the remote computer from which i connected to the client are one the same local network (i have a single cable modem, who's signal is split to both computers in the condo via a router), and i was using the host's name to connect, not IP address. it turns out i cannot connect to my client at home from my computer at work today.so there's a good possibility that, after losing its connection and then reconnecting with the client so many times, my BOINC manager will finally fail to reconnect to the client after one of those lost connections, and i won't be able to reconnect the client until i get home from work b/c i cannot do so remotely.
Ok guys, it looks like i celebrated a bit prematurely. in the mean time i'm gonna try to gain control of this host's client from the computer in the other room and see if i can't confirm that its working myself. if anyone could confirm that this is the correct method i would appreciate it. where the "1" will allow a GUI RPC from any remote host. it appears i just have to add the following section to my cc_config.xml file: i found another page in the BOINC online documentation that contains all the logging flags and options that can be placed into a cc_config.xml file. *EDIT* - i just realized that i really don't need to do this via the command prompt.i think it was explained that way for linux/unix CLI users, hence my confusion.
#Boinc host location windows#
my problem is this: how exactly do i "run the client with the -allow_remote_gui_rpc command line option?" i understand that i must enter the command using the Windows command prompt, but what exactly to i type at the prompt? that is, what text/syntax precedes the actual command itself? also, what is the chronological order of things? do i do this before or after i have the BOINC manager up and running? any help would be appreciated.i would love to test it out tonight with a remote computer in the other bedroom so that its ready to go before i leave for work tomorrow.
#Boinc host location password#
so having the password memorized and being able to control the client from any remote computer is ideal for me. I'd prefer to use the 2nd method, as i never know when i might need access to this particular home client/host while i'm out and about. the 2nd method is to "run the client with the -allow_remote_gui_rpc command line option," which will allow it to accept connections from any host, subject to password authentication. one way is to place a remote_hosts.cfg file in your BOINC data directory containing a list of the DNS host names or IP addresses of the computers you'd like to have remote control over the client. as you can see, there are 2 ways to do it. but it doesn't quite spell it out for me,which is what i really need. i found a pretty good how-to guide in the BOINC online documentation, most of which i understand. As the title suggests, i'm interested in controlling the BOINC client of one of my hosts at home from my computer at work during the day.
0 kommentar(er)
