remote connection failed unless I started using REMOTE_HOSTS.CFG

Message boards : Questions and problems : remote connection failed unless I started using REMOTE_HOSTS.CFG
Message board moderation

To post messages, you must log in.

AuthorMessage
Profile Joseph Stateson
Volunteer tester
Avatar

Send message
Joined: 27 Jun 08
Posts: 641
United States
Message 74633 - Posted: 6 Dec 2016, 21:38:34 UTC
Last modified: 6 Dec 2016, 21:40:50 UTC

Been running a SETI farm since about 2009 and never had this problem before. My second windows 10 system, also running 7.6.22, would not allow a remote connection unless I created REMOTE_HOSTS.CFG and put in the ip address of the remote. i spent two days looking at this trying re-installs, removing / adding firewall, testing with telnet to port 31416, etc. Tried both boinctasks and the "select computer" option in boincmgr. I did notice that boinctasks tried connection to both boinc and the associated tthrottle and that tthrottle did make a connection (port 31417) but the connection timed out for boinc (31416). I then tried creating that remote host config file and sure enough was able to make a connection. Was wondering if anyone has seen this problem before. I have created at least 100+ SETI and later BOINC systems and this is the first time I had to use that cfg file. My normal setup is an empty (0 size) gui_rpc_auth.cfg file and a non-existent hosts cfg file so I can check my systems from any computer running boinctasks.
ID: 74633 · Report as offensive
Juha
Volunteer developer
Volunteer tester
Help desk expert

Send message
Joined: 20 Nov 12
Posts: 801
Finland
Message 74644 - Posted: 7 Dec 2016, 14:55:25 UTC - in response to Message 74633.  

Have you set <allow_remote_gui_rpc> in cc_config.xml on other systems but not this one?
ID: 74644 · Report as offensive
Profile Joseph Stateson
Volunteer tester
Avatar

Send message
Joined: 27 Jun 08
Posts: 641
United States
Message 74668 - Posted: 7 Dec 2016, 20:10:09 UTC - in response to Message 74644.  

I use "\boinc.exe" --detach --allow_remote_gui_rpc in the windows registry to start boinc and do not use that cc file unless boinc ignores one or more of my GPUs. The boincmgr and boinctray keys are deleted as these systems are part of a farm and only need boinc.exe.

I cannot account for why this system requires that hosts file. I had something strange happen while testing the first install. I got an error -155 when attempting to execute bonccmd.exe "Authorization Denied" or something like that. That was in the program file\boinc directory so it should have worked. However, after reinstalling boinc a second time, that error went away. I originally executed the boinc install program using "run as administrator" but since I am the administrator that should have made no difference whether I selected it or not (one would think).
ID: 74668 · Report as offensive
Profile Jord
Volunteer tester
Help desk expert
Avatar

Send message
Joined: 29 Aug 05
Posts: 15477
Netherlands
Message 74670 - Posted: 7 Dec 2016, 22:03:16 UTC - in response to Message 74668.  

The built-in Windows administrator account is different from your administrator account. The 'run as administrator' option uses the built-in administrator account, not yours. The built-in administrator account and a user administrator account have the same level of privileges, but if you install BOINC with the built-in account it puts permission for just that account on the program- and data directory. When you then try to run BOINC with the other account, you don't have permission.
ID: 74670 · Report as offensive
Richard Haselgrove
Volunteer tester
Help desk expert

Send message
Joined: 5 Oct 06
Posts: 5077
United Kingdom
Message 74671 - Posted: 7 Dec 2016, 22:03:44 UTC - in response to Message 74668.  

I cannot account for why this system requires that hosts file. I had something strange happen while testing the first install. I got an error -155 when attempting to execute bonccmd.exe "Authorization Denied" or something like that. That was in the program file\boinc directory so it should have worked. However, after reinstalling boinc a second time, that error went away. I originally executed the boinc install program using "run as administrator" but since I am the administrator that should have made no difference whether I selected it or not (one would think).
It sounds as if you executed the boinccmd program from the BOINC program directory - as you should. But the authorisation key (password) is stored in the gui_rpc_auth.cfg file, which lives in the BOINC data directory.

Since the two directories are different, there needs to be a way of finding one from the other: that's the DATADIR key in the Windows registry. It sounds as if your first installation failed to set that key properly, but the second did its job.
ID: 74671 · Report as offensive
Profile Joseph Stateson
Volunteer tester
Avatar

Send message
Joined: 27 Jun 08
Posts: 641
United States
Message 74689 - Posted: 8 Dec 2016, 14:23:32 UTC - in response to Message 74644.  

[SOLVED] Juha's thought about the cc_config.xml had me look at that file and I discovered that when I used the boincmgr dialog box option to exclude a program that cc_config file got created, with all defaults, and sure enough the remote gui option was set to "0". This negated my launch command --detach --allow_remote_gui_rpc. Also want to point out I was a member of seti since 1999, not 2009.
ID: 74689 · Report as offensive

Message boards : Questions and problems : remote connection failed unless I started using REMOTE_HOSTS.CFG

Copyright © 2024 University of California.
Permission is granted to copy, distribute and/or modify this document under the terms of the GNU Free Documentation License, Version 1.2 or any later version published by the Free Software Foundation.