| Index | Recent Threads | Unanswered Threads | Who's Active | Guidelines | Search |
| World Community Grid Forums
|
| No member browsing this thread |
|
Thread Status: Active Total posts in this thread: 2
|
|
| Author |
|
|
Former Member
Cruncher Joined: May 22, 2018 Post Count: 0 Status: Offline |
I'll try and use the correct terminology so here goes.
I've only just set up the WCG Windows client on my desktop PC (XP) and noticed it has an option under the advanced menu to 'select computer' at which point you can put in a hostname and some kind of password. Sounds very useful I figure, controlling or checking multiple clients, even over a network. I also have a 'headless' linux pc (no mouse/kb/video card) as a fileserver, so I installed the WCG client on this (debian/sid/32bit). I stumbled my way through setting the client up over a shell (SSH). Both PC's are now configured and happily working away on projects. What I cant figure out currently is why I cant use the Windows client manager to connect to the linux client over the local network (no firewalls, no rules, nothing). It attempts a connection but then says:- World Community Grid - BOINC Client - Connection failed and asks if i want to try again. There's a password that the manager has put in, which is long (about 30 characters) which is the same length as the one for localhost (on the XP machine) which does work. I'm assuming its one of those long key's in my profile. Is there something I have to enable on the linux client to allow remote connections, or am I overlooking something else entirely. Oh and both PC's are running version 5.10.45 As I mentioned before, its all a bit new and confusing and I hope I've explained myself and what I'm trying to do adequately. James |
||
|
|
Sekerob
Ace Cruncher Joined: Jul 24, 2005 Post Count: 20043 Status: Offline |
Two tips:
----------------------------------------- set up the gui_rpc_auth.cfg file on all clients with a same simplified password, replacing the random 32 hex that is entered during install. - set up / create the remote_hosts.cfg file to contain a list of device IP's and network device names that are allowed to connect. Keep that file on all clients identical, so include the local host ip too (as last entry). sample: 192.168.1.101 clienta 192.168.1.102 clientb 192.168.1.103 clientc 127.0.0.1 localhost If you set up these files and restart BOINC you should be able to connect, of course making sure to also allow the passage through any firewalls and to include port 31416 used by BOINC for RPC comms. Placement of these files is in the socalled BOINC data directory, usually the location where the installer puts the gui_rpc_auth.cfg.
WCG
----------------------------------------Please help to make the Forums an enjoyable experience for All! [Edit 2 times, last edit by Sekerob at Aug 4, 2008 12:36:52 PM] |
||
|
|
|