eFMer - BoincTasks and TThrottle forum

BoincTasks For Window, Mac & Linux => Questions => Topic started by: RaulB on August 26, 2010, 07:09:22 AM

Title: Remote computers found, but unable to select them (SOLVED)
Post by: RaulB on August 26, 2010, 07:09:22 AM
I have installed BoincTasks on several remote windows 7 systems. When I do a 'Find computers' from the localhost, all are found with IP addresses, but no "Yes" in the Boinc field. When I tick the check box to select any of them, it clears itself immediately.
I thought at first to move my .cgf files (gui_rpc_auth and remote_hosts) from the ProgramData/Boinc directory to the ProgramFiles/Boinc directory, but this did not work (in fact, BoincTasks created it's own gui_rpc_auth.cfg in the ProgramData/Boinc directory with its own password).
So I reverted to the ProgramData/Boinc directories and have the .cgf files in all the remote systems.
The localhost works fine on all the systems, but I cannot get the remote systems connected.
Title: Re: Remote computers found, but unable to select them
Post by: fred on August 26, 2010, 07:51:01 AM
Quote from: RaulB on August 26, 2010, 07:09:22 AM
1) I have installed BoincTasks on several remote windows 7 systems. When I do a 'Find computers' from the localhost, all are found with IP addresses, but no "Yes" in the Boinc field. When I tick the check box to select any of them, it clears itself immediately.
2) I thought at first to move my .cgf files (gui_rpc_auth and remote_hosts) from the ProgramData/Boinc directory to the ProgramFiles/Boinc directory, but this did not work (in fact, BoincTasks created it's own gui_rpc_auth.cfg in the ProgramData/Boinc directory with its own password).
So I reverted to the ProgramData/Boinc directories and have the .cgf files in all the remote systems.
The localhost works fine on all the systems, but I cannot get the remote systems connected.
1) You can't check computers that are not found with BOINC running.
If you make any changes to gui_rpc_auth and remote_hosts, you have to close down the BOINC client and restart it, or reboot the system.  Otherwise the new files aren't used.
2) The files NEED to be here C:\ProgramData\BOINC.
If there isn't any gui_rpc_auth.cfg, or it isn't in the right place the BOINC client makes a new one.

You better install http://www.efmer.eu/boinc/boinc_tasks/download_beta.html (http://www.efmer.eu/boinc/boinc_tasks/download_beta.html) 0.72.
It needs to be running on the computer, you want to see all the other computer on. There is no need to run BT on all machines, but you may.
It is even easier if you are running TThrottle on one of the remote machines. But that's no must to get it working.

In 0.72 use "Scan address range" and see if you can find your computers.
If you don't see a yes in the BOINC column check the log of that computer. Most of the time you see an entry, like refused.
Title: Re: Remote computers found, but unable to select them
Post by: RaulB on August 26, 2010, 08:31:41 AM
Thanks for the prompt reply. I have removed the .cfg files from the ProgramFiles/Boinc directory and left them in the ProgramData/Boinc directory. When I do a scan for other computers, a remote XP system is identified correctly and I can access the tasks - no Windows 7 systems identifed. When I do a find, the XP system is not identified, but all Windows 7 systems are with IP addresses - but without a BOINC "Yes".
I will download what you recommend at try again.
Title: Re: Remote computers found, but unable to select them
Post by: fred on August 26, 2010, 09:27:17 AM
Quote from: RaulB on August 26, 2010, 08:31:41 AM
Thanks for the prompt reply. I have removed the .cfg files from the ProgramFiles/Boinc directory and left them in the ProgramData/Boinc directory. When I do a scan for other computers, a remote XP system is identified correctly and I can access the tasks - no Windows 7 systems identifed. When I do a find, the XP system is not identified, but all Windows 7 systems are with IP addresses - but without a BOINC "Yes".
I will download what you recommend at try again.
When you have a name instead of an ip address in the "IP address" column it may not work. Best use an IP address, because names are not always resolved. And Win 7 allows even less.
Title: Re: Remote computers found, but unable to select them
Post by: jjwhalen on August 26, 2010, 10:46:01 AM
Fred,

I'm following this thread with interest, since I raised this issue some days ago in the BT 0.71 (http://www.efmer.eu/forum_tt/index.php?topic=510.0) testing thread:

Quote from: jjwhalen on August 20, 2010, 04:47:34 PM
Quote from: fred on August 20, 2010, 02:26:49 PM
1) ...
You can only set a check, when the BOINC or TThrottle column show a Yes.

I reviewed the Manual and found
QuoteFinding TThrottle and not BOINC (missing yes), indicates a missing remote_hosts.cfg or a missing entry in the file.
but I definitely have remote_hosts.cfg on all my boxes & as far as I know it's complete.  Certainly I can use BM to log onto any machine from any other machine using either IP or machine_name.  So what exactly does
Quotea missing entry in the file
refer to? I'll be glad to tweak my remote_hosts.cfg(s) any way I need to :)

Beginning with v0.72 I can now set a checkmark in Find computers as long as Tthrottle is running on the host, because of
QuoteChanged: Dialog find computers: Scan address range will now use the host name found by TThrottle.
and that's very helpful.  But I still don't get a Yes under BOINC and I'd still like to know: what does the BT Manual mean by a missing entry in the remote_hosts.cfg ???  My remote_host.cfg's are built per the BOINC Manual (http://boinc.berkeley.edu/wiki/Controlling_BOINC_remotely) as far as I know.  As I said before, it's good enough for each computer to log onto each of the others using BOINCManager (reverified), so what is BT looking for that BM isn't?

I followed the advice you gave RaulB above
QuoteIn 0.72 use "Scan address range" and see if you can find your computers.
If you don't see a yes in the BOINC column check the log of that computer. Most of the time you see an entry, like refused,
but I didn't see any such entry.  (BTW from past debugging experience, I believe the exact form you're looking for is "unable to resolve hostname..." ;) )
Title: Re: Remote computers found, but unable to select them
Post by: RaulB on August 26, 2010, 11:30:49 AM
I have exactly the same gui_rpc-auth.cfg and remote_hosts.cfg in all my systems (win 7 and XP) - The XP system is found on a Scan (but not on a Find) and I connect correctly. The Win 7 systems are not found at all on a Scan, but are identified on a Find, but with no Boinc "Yes" and hence no connection. Most puzzling!!!!
Title: Re: Remote computers found, but unable to select them
Post by: fred on August 26, 2010, 11:58:07 AM
Quote from: jjwhalen on August 26, 2010, 10:46:01 AM
But I still don't get a Yes under BOINC.
As you don't get a yes and you can connect with the machine without any problems with the same IP address something seems to be wrong with the detection.
I will try to add some extra diagnostics in the next version.
Title: Re: Remote computers found, but unable to select them
Post by: fred on August 26, 2010, 12:02:37 PM
Quote from: RaulB on August 26, 2010, 11:30:49 AM
I have exactly the same gui_rpc-auth.cfg and remote_hosts.cfg in all my systems (win 7 and XP) - The XP system is found on a Scan (but not on a Find) and I connect correctly. The Win 7 systems are not found at all on a Scan, but are identified on a Find, but with no Boinc "Yes" and hence no connection. Most puzzling!!!!
Try adding the missing computers manually in the computer tab and see if there is any response.
Title: Re: Remote computers found, but unable to select them
Post by: Pepo on August 26, 2010, 12:03:48 PM
Quote from: RaulB on August 26, 2010, 11:30:49 AM
I have exactly the same gui_rpc-auth.cfg and remote_hosts.cfg in all my systems (win 7 and XP) - The XP system is found on a Scan (but not on a Find) and I connect correctly. The Win 7 systems are not found at all on a Scan, but are identified on a Find, but with no Boinc "Yes" and hence no connection. Most puzzling!!!!
After entering the Win 7 systems manually in the Computers tab, does BT have no problem connecting to them?
(OK I'm the second to recommend this.)
Title: Re: Remote computers found, but unable to select them
Post by: fred on August 26, 2010, 12:14:04 PM
But if you can both do the following:

Menu: Extra BoincTasks setting -> General, remove the check before "Connect to TThrottle".
Menu: Show -> show log , check "Enable debug mode" select  the "Clear" button.

Computers tab, menu: Computer -> Find computer and select "Scan address range".
When the scan is completed remove the "Enable debug mode" from the logging.

As the log will exceed the maximum shown, find the complete log:

C:\Users\user_name\AppData\Roaming\eFMer\BoincTasks\log *.log from today.

Look for the lines SendRecieve ---- Recieved from Server: <boinc_gui_rpc_reply>
This is what the BOINC client responds.

And give me all these lines, if there are 3 computes there should be 3 lines.
Title: Re: Remote computers found, but unable to select them
Post by: Pepo on August 26, 2010, 12:35:01 PM
Sorry for my possible ignorance, but even after looking around, I somehow can not realize the implementation difference behind Scan and Find. How do they actually differ? Just in the number of simultaneously launched threads?

Additionally, after scanning the range 192.168.7.1-255 twice (always correctly found my localhost with BOINC and one remote machine without BOINC), I've inadvertently pressed something (was it the Find?) and now BT is progressing... without any additional threads or any open connection (except to the localhost) already nearly for 30 minutes long... No way to cancel it :-\
Title: Re: Remote computers found, but unable to select them
Post by: RaulB on August 26, 2010, 12:37:02 PM
OK - No Throttle, debug mode on, added all computers manually with correct names and IP addresses.
Here's the log
26 August 2010 - 14:16:55 Logging ---- Start debug mode
26 August 2010 - 14:16:55
26 August 2010 - 14:16:56 GetUserDirectory3 ---- C:\Users\RaulB\AppData\Roaming\eFMer\BoincTasks
26 August 2010 - 14:16:56 GetUserDirectory3 ---- C:\Users\RaulB\AppData\Roaming\eFMer\BoincTasks
26 August 2010 - 14:17:26 GetUserDirectory3 ---- C:\Users\RaulB\AppData\Roaming\eFMer\BoincTasks
26 August 2010 - 14:17:26 GetUserDirectory3 ---- C:\Users\RaulB\AppData\Roaming\eFMer\BoincTasks
26 August 2010 - 14:17:56 GetUserDirectory3 ---- C:\Users\RaulB\AppData\Roaming\eFMer\BoincTasks
26 August 2010 - 14:17:56 GetUserDirectory3 ---- C:\Users\RaulB\AppData\Roaming\eFMer\BoincTasks
26 August 2010 - 14:18:26 GetUserDirectory3 ---- C:\Users\RaulB\AppData\Roaming\eFMer\BoincTasks
26 August 2010 - 14:18:26 GetUserDirectory3 ---- C:\Users\RaulB\AppData\Roaming\eFMer\BoincTasks
26 August 2010 - 14:18:53 GetUserDirectory3 ---- C:\Users\RaulB\AppData\Roaming\eFMer\BoincTasks
26 August 2010 - 14:18:53 GetUserDirectory3 ---- C:\Users\RaulB\AppData\Roaming\eFMer\BoincTasks
26 August 2010 - 14:19:10 GetUserDirectory3 ---- C:\Users\RaulB\AppData\Roaming\eFMer\BoincTasks
26 August 2010 - 14:19:10 GetUserDirectory3 ---- C:\Users\RaulB\AppData\Roaming\eFMer\BoincTasks
26 August 2010 - 14:19:20 GetUserDirectory3 ---- C:\Users\RaulB\AppData\Roaming\eFMer\BoincTasks
26 August 2010 - 14:19:20 GetUserDirectory3 ---- C:\Users\RaulB\AppData\Roaming\eFMer\BoincTasks
26 August 2010 - 14:19:25 GetUserDirectory3 ---- C:\Users\RaulB\AppData\Roaming\eFMer\BoincTasks
26 August 2010 - 14:19:25 GetUserDirectory3 ---- C:\Users\RaulB\AppData\Roaming\eFMer\BoincTasks
26 August 2010 - 14:19:29 GetUserDirectory3 ---- C:\Users\RaulB\AppData\Roaming\eFMer\BoincTasks
26 August 2010 - 14:19:29 GetUserDirectory3 ---- C:\Users\RaulB\AppData\Roaming\eFMer\BoincTasks
26 August 2010 - 14:19:31 GetUserDirectory3 ---- C:\Users\RaulB\AppData\Roaming\eFMer\BoincTasks
26 August 2010 - 14:19:31 GetUserDirectory3 ---- C:\Users\RaulB\AppData\Roaming\eFMer\BoincTasks
26 August 2010 - 14:19:32 GetUserDirectory3 ---- C:\Users\RaulB\AppData\Roaming\eFMer\BoincTasks
26 August 2010 - 14:19:32 GetUserDirectory3 ---- C:\Users\RaulB\AppData\Roaming\eFMer\BoincTasks
26 August 2010 - 14:19:33 GetUserDirectory3 ---- C:\Users\RaulB\AppData\Roaming\eFMer\BoincTasks
26 August 2010 - 14:19:33 GetUserDirectory3 ---- C:\Users\RaulB\AppData\Roaming\eFMer\BoincTasks
26 August 2010 - 14:19:34 GetUserDirectory3 ---- C:\Users\RaulB\AppData\Roaming\eFMer\BoincTasks
26 August 2010 - 14:19:34 GetUserDirectory3 ---- C:\Users\RaulB\AppData\Roaming\eFMer\BoincTasks
26 August 2010 - 14:19:35 GetUserDirectory3 ---- C:\Users\RaulB\AppData\Roaming\eFMer\BoincTasks
26 August 2010 - 14:19:35 GetUserDirectory3 ---- C:\Users\RaulB\AppData\Roaming\eFMer\BoincTasks
26 August 2010 - 14:19:36 GetUserDirectory3 ---- C:\Users\RaulB\AppData\Roaming\eFMer\BoincTasks
26 August 2010 - 14:19:36 GetUserDirectory3 ---- C:\Users\RaulB\AppData\Roaming\eFMer\BoincTasks
26 August 2010 - 14:19:37 GetUserDirectory3 ---- C:\Users\RaulB\AppData\Roaming\eFMer\BoincTasks
26 August 2010 - 14:19:37 GetUserDirectory3 ---- C:\Users\RaulB\AppData\Roaming\eFMer\BoincTasks
26 August 2010 - 14:19:38 GetUserDirectory3 ---- C:\Users\RaulB\AppData\Roaming\eFMer\BoincTasks
26 August 2010 - 14:19:38 GetUserDirectory3 ---- C:\Users\RaulB\AppData\Roaming\eFMer\BoincTasks
26 August 2010 - 14:19:39 GetUserDirectory3 ---- C:\Users\RaulB\AppData\Roaming\eFMer\BoincTasks
26 August 2010 - 14:19:39 GetUserDirectory3 ---- C:\Users\RaulB\AppData\Roaming\eFMer\BoincTasks
26 August 2010 - 14:19:40 GetUserDirectory3 ---- C:\Users\RaulB\AppData\Roaming\eFMer\BoincTasks
26 August 2010 - 14:19:40 GetUserDirectory3 ---- C:\Users\RaulB\AppData\Roaming\eFMer\BoincTasks
26 August 2010 - 14:20:10 GetUserDirectory3 ---- C:\Users\RaulB\AppData\Roaming\eFMer\BoincTasks
26 August 2010 - 14:20:11 GetUserDirectory3 ---- C:\Users\RaulB\AppData\Roaming\eFMer\BoincTasks
26 August 2010 - 14:20:40 GetUserDirectory3 ---- C:\Users\RaulB\AppData\Roaming\eFMer\BoincTasks
26 August 2010 - 14:20:40 GetUserDirectory3 ---- C:\Users\RaulB\AppData\Roaming\eFMer\BoincTasks
26 August 2010 - 14:21:03 , SendRecieve ---- Recieved from Server: <boinc_gui_rpc_reply>
<unauthorized/>
</boinc_gui_rpc_reply>

26 August 2010 - 14:21:04 , Connect ---- Invalid Socket
26 August 2010 - 14:21:10 GetUserDirectory3 ---- C:\Users\RaulB\AppData\Roaming\eFMer\BoincTasks
26 August 2010 - 14:21:10 GetUserDirectory3 ---- C:\Users\RaulB\AppData\Roaming\eFMer\BoincTasks
26 August 2010 - 14:21:25 , Connect ---- Invalid Socket
26 August 2010 - 14:21:40 GetUserDirectory3 ---- C:\Users\RaulB\AppData\Roaming\eFMer\BoincTasks
26 August 2010 - 14:21:40 GetUserDirectory3 ---- C:\Users\RaulB\AppData\Roaming\eFMer\BoincTasks
26 August 2010 - 14:21:47 , Connect ---- Invalid Socket
26 August 2010 - 14:22:10 GetUserDirectory3 ---- C:\Users\RaulB\AppData\Roaming\eFMer\BoincTasks
26 August 2010 - 14:22:10 GetUserDirectory3 ---- C:\Users\RaulB\AppData\Roaming\eFMer\BoincTasks
26 August 2010 - 14:22:40 GetUserDirectory3 ---- C:\Users\RaulB\AppData\Roaming\eFMer\BoincTasks
26 August 2010 - 14:22:40 GetUserDirectory3 ---- C:\Users\RaulB\AppData\Roaming\eFMer\BoincTasks
26 August 2010 - 14:22:47 , SendRecieve ---- Recieved from Server: <boinc_gui_rpc_reply>
<unauthorized/>
</boinc_gui_rpc_reply>

26 August 2010 - 14:22:48 , Connect ---- Invalid Socket
26 August 2010 - 14:23:09 , Connect ---- Invalid Socket
26 August 2010 - 14:23:10 GetUserDirectory3 ---- C:\Users\RaulB\AppData\Roaming\eFMer\BoincTasks
26 August 2010 - 14:23:10 GetUserDirectory3 ---- C:\Users\RaulB\AppData\Roaming\eFMer\BoincTasks
26 August 2010 - 14:23:30 , Connect ---- Invalid Socket
26 August 2010 - 14:23:40 GetUserDirectory3 ---- C:\Users\RaulB\AppData\Roaming\eFMer\BoincTasks
26 August 2010 - 14:23:40 GetUserDirectory3 ---- C:\Users\RaulB\AppData\Roaming\eFMer\BoincTasks
26 August 2010 - 14:23:51 , Connect ---- Invalid Socket
26 August 2010 - 14:24:10 GetUserDirectory3 ---- C:\Users\RaulB\AppData\Roaming\eFMer\BoincTasks
26 August 2010 - 14:24:10 GetUserDirectory3 ---- C:\Users\RaulB\AppData\Roaming\eFMer\BoincTasks
26 August 2010 - 14:24:12 , Connect ---- Invalid Socket
26 August 2010 - 14:24:33 , Connect ---- Invalid Socket
26 August 2010 - 14:24:40 GetUserDirectory3 ---- C:\Users\RaulB\AppData\Roaming\eFMer\BoincTasks
26 August 2010 - 14:24:40 GetUserDirectory3 ---- C:\Users\RaulB\AppData\Roaming\eFMer\BoincTasks
26 August 2010 - 14:24:54 , Connect ---- Invalid Socket
26 August 2010 - 14:25:10 GetUserDirectory3 ---- C:\Users\RaulB\AppData\Roaming\eFMer\BoincTasks
26 August 2010 - 14:25:10 GetUserDirectory3 ---- C:\Users\RaulB\AppData\Roaming\eFMer\BoincTasks
26 August 2010 - 14:25:40 GetUserDirectory3 ---- C:\Users\RaulB\AppData\Roaming\eFMer\BoincTasks
26 August 2010 - 14:25:40 GetUserDirectory3 ---- C:\Users\RaulB\AppData\Roaming\eFMer\BoincTasks
26 August 2010 - 14:26:10 GetUserDirectory3 ---- C:\Users\RaulB\AppData\Roaming\eFMer\BoincTasks
26 August 2010 - 14:26:10 GetUserDirectory3 ---- C:\Users\RaulB\AppData\Roaming\eFMer\BoincTasks
26 August 2010 - 14:26:40 GetUserDirectory3 ---- C:\Users\RaulB\AppData\Roaming\eFMer\BoincTasks
26 August 2010 - 14:26:40 GetUserDirectory3 ---- C:\Users\RaulB\AppData\Roaming\eFMer\BoincTasks
26 August 2010 - 14:27:10 GetUserDirectory3 ---- C:\Users\RaulB\AppData\Roaming\eFMer\BoincTasks
26 August 2010 - 14:27:10 GetUserDirectory3 ---- C:\Users\RaulB\AppData\Roaming\eFMer\BoincTasks
26 August 2010 - 14:27:40 GetUserDirectory3 ---- C:\Users\RaulB\AppData\Roaming\eFMer\BoincTasks
26 August 2010 - 14:27:40 GetUserDirectory3 ---- C:\Users\RaulB\AppData\Roaming\eFMer\BoincTasks
26 August 2010 - 14:27:54 GetUserDirectory3 ---- C:\Users\RaulB\AppData\Roaming\eFMer\BoincTasks
26 August 2010 - 14:27:54 BoincTasks version: 0.71
26 August 2010 - 14:27:54 Maximum number of computers: 60
26 August 2010 - 14:27:54 Computers ---- localhost get local password: (D:\ProgramData\BOINC\\gui_rpc_auth.cfg) raulb
26 August 2010 - 14:27:54 Computers ---- RaulB-Desktop , localhost
26 August 2010 - 14:27:54 Computers ---- RaulB , 192.168.0.6
26 August 2010 - 14:27:54 Computers ---- RaulB-Tablet , 192.168.0.5
26 August 2010 - 14:27:54 Computers ---- raulb-lenovotab , 192.168.0.4
26 August 2010 - 14:27:54 Computers ---- raquelnatalia , 192.168.0.3
26 August 2010 - 14:27:54 GetLocalDirectory ---- D:\Program Files\eFMer\BoincTasks
26 August 2010 - 14:27:54 GetUserDirectory3 ---- C:\Users\RaulB\AppData\Roaming\eFMer\BoincTasks
26 August 2010 - 14:27:55 GetUserDirectory3 ---- C:\Users\RaulB\AppData\Roaming\eFMer\BoincTasks
26 August 2010 - 14:27:55 GetUserDirectory3 ---- C:\Users\RaulB\AppData\Roaming\eFMer\BoincTasks
26 August 2010 - 14:27:55 GetUserDirectory3 ---- C:\Users\RaulB\AppData\Roaming\eFMer\BoincTasks
26 August 2010 - 14:27:55 GetUserDirectory3 ---- C:\Users\RaulB\AppData\Roaming\eFMer\BoincTasks
26 August 2010 - 14:27:55 Connected ---- Host: localhost,RaulB-Desktop,Port: 31416, BOINC Version: 6.10.56
26 August 2010 - 14:27:55 Connected ---- Host: 192.168.0.6,RaulB,Port: 31416, BOINC Version: 6.10.56
26 August 2010 - 14:28:15 XU§ ---- Host: 192.168.0.4,raulb-lenovotab,Port: 31416, connection error
26 August 2010 - 14:28:15 pء ---- Host: 192.168.0.5,RaulB-Tablet,Port: 31416, connection error
26 August 2010 - 14:28:15 ÈÉ+ ---- Host: 192.168.0.3,raquelnatalia,Port: 31416, connection error
26 August 2010 - 14:28:16 GetUserDirectory3 ---- C:\Users\RaulB\AppData\Roaming\eFMer\BoincTasks
26 August 2010 - 14:28:16 GetUserDirectory3 ---- C:\Users\RaulB\AppData\Roaming\eFMer\BoincTasks
26 August 2010 - 14:28:17 GetUserDirectory3 ---- C:\Users\RaulB\AppData\Roaming\eFMer\BoincTasks
26 August 2010 - 14:28:17 GetUserDirectory3 ---- C:\Users\RaulB\AppData\Roaming\eFMer\BoincTasks
26 August 2010 - 14:28:47 GetUserDirectory3 ---- C:\Users\RaulB\AppData\Roaming\eFMer\BoincTasks
26 August 2010 - 14:28:47 GetUserDirectory3 ---- C:\Users\RaulB\AppData\Roaming\eFMer\BoincTasks
26 August 2010 - 14:29:17 GetUserDirectory3 ---- C:\Users\RaulB\AppData\Roaming\eFMer\BoincTasks
26 August 2010 - 14:29:17 GetUserDirectory3 ---- C:\Users\RaulB\AppData\Roaming\eFMer\BoincTasks
26 August 2010 - 14:30:08 pØ¡ø‰-  ---- Host: 192.168.0.5,RaulB-Tablet,Port: 31416, connection error
26 August 2010 - 14:30:08 ÈÉ+¨Ë¡  ---- Host: 192.168.0.3,raquelnatalia,Port: 31416, connection error
26 August 2010 - 14:30:08 XU§øv-  ---- Host: 192.168.0.4,raulb-lenovotab,Port: 31416, connection error
26 August 2010 - 14:30:08 GetUserDirectory3 ---- C:\Users\RaulB\AppData\Roaming\eFMer\BoincTasks
26 August 2010 - 14:30:08 GetUserDirectory3 ---- C:\Users\RaulB\AppData\Roaming\eFMer\BoincTasks
26 August 2010 - 14:30:38 GetUserDirectory3 ---- C:\Users\RaulB\AppData\Roaming\eFMer\BoincTasks
26 August 2010 - 14:30:38 GetUserDirectory3 ---- C:\Users\RaulB\AppData\Roaming\eFMer\BoincTasks
26 August 2010 - 14:31:08 GetUserDirectory3 ---- C:\Users\RaulB\AppData\Roaming\eFMer\BoincTasks
26 August 2010 - 14:31:08 GetUserDirectory3 ---- C:\Users\RaulB\AppData\Roaming\eFMer\BoincTasks
26 August 2010 - 14:31:39 GetUserDirectory3 ---- C:\Users\RaulB\AppData\Roaming\eFMer\BoincTasks
26 August 2010 - 14:31:39 GetUserDirectory3 ---- C:\Users\RaulB\AppData\Roaming\eFMer\BoincTasks
26 August 2010 - 14:32:09 GetUserDirectory3 ---- C:\Users\RaulB\AppData\Roaming\eFMer\BoincTasks
26 August 2010 - 14:32:09 GetUserDirectory3 ---- C:\Users\RaulB\AppData\Roaming\eFMer\BoincTasks
26 August 2010 - 14:33:00 ;1¨Ë¡  ---- Host: 192.168.0.3,raquelnatalia,Port: 31416, connection error
26 August 2010 - 14:33:00 XU§øv-  ---- Host: 192.168.0.4,raulb-lenovotab,Port: 31416, connection error
26 August 2010 - 14:33:00 pØ¡ø‰-  ---- Host: 192.168.0.5,RaulB-Tablet,Port: 31416, connection error
26 August 2010 - 14:33:00 GetUserDirectory3 ---- C:\Users\RaulB\AppData\Roaming\eFMer\BoincTasks
26 August 2010 - 14:33:01 GetUserDirectory3 ---- C:\Users\RaulB\AppData\Roaming\eFMer\BoincTasks
26 August 2010 - 14:33:30 GetUserDirectory3 ---- C:\Users\RaulB\AppData\Roaming\eFMer\BoincTasks
26 August 2010 - 14:33:30 GetUserDirectory3 ---- C:\Users\RaulB\AppData\Roaming\eFMer\BoincTasks
26 August 2010 - 14:34:00 GetUserDirectory3 ---- C:\Users\RaulB\AppData\Roaming\eFMer\BoincTasks
26 August 2010 - 14:34:01 GetUserDirectory3 ---- C:\Users\RaulB\AppData\Roaming\eFMer\BoincTasks
26 August 2010 - 14:34:05 Logging ---- Stop debug mode

What's the invalid socket???
Title: Re: Remote computers found, but unable to select them
Post by: fred on August 26, 2010, 12:45:31 PM
Quote from: RaulB on August 26, 2010, 12:37:02 PM
OK - No Throttle, debug mode on, added all computers manually with correct names and IP addresses.

What's the invalid socket???
The invalided socket is a IP address it can't connect to.
In the log I see 2 computers responding.
Title: Re: Remote computers found, but unable to select them
Post by: fred on August 26, 2010, 12:51:52 PM
Quote from: Pepo on August 26, 2010, 12:35:01 PM
Sorry for my possible ignorance, but even after looking around, I somehow can not realize the implementation difference behind Scan and Find. How do they actually differ? Just in the number of simultaneously launched threads?

Additionally, after scanning the range 192.168.7.1-255 twice (always correctly found my localhost with BOINC and one remote machine without BOINC), I've inadvertently pressed something (was it the Find?) and now BT is progressing... without any additional threads or any open connection (except to the localhost) already nearly for 30 minutes long... No way to cancel it :-\
The two are fundamentally different.
Find uses a build in Windows function to detect computers on the net. It uses all sorts of protocols to find it.

Scan, scans all addresses in the range using the tcp ip protocol only.
It sends a dummy string to each computer and waits for a response.
The BOINC response should be  <boinc_gui_rpc_reply> <unauthorized/> </boinc_gui_rpc_reply>
A request without a supplied password.
Title: Re: Remote computers found, but unable to select them
Post by: Pepo on August 26, 2010, 02:16:05 PM
Quote from: fred on August 26, 2010, 12:51:52 PM
Quote from: Pepo on August 26, 2010, 12:35:01 PM
Sorry for my possible ignorance, but even after looking around, I somehow can not realize the implementation difference behind Scan and Find. How do they actually differ?
Find uses a build in Windows function to detect computers on the net. It uses all sorts of protocols to find it.

Scan, scans all addresses in the range using the tcp ip protocol only.
It sends a dummy string to each computer and waits for a response.
The BOINC response should be  <boinc_gui_rpc_reply> <unauthorized/> </boinc_gui_rpc_reply>
Thanks, Fred, that's an excellent explanation!
Title: Re: Remote computers found, but unable to select them
Post by: jjwhalen on August 26, 2010, 02:28:31 PM
Quote from: fred on August 26, 2010, 12:14:04 PM
But if you can both do the following:

--SNIP--


I got curious, so I set up 3 test cases (all hosts are WinVista SP2, all BOINC clients v6.11.6):

QuoteCase 1 - Per Fred's instructions

Preconditions:
BOINC clients all running
All computers correctly listed by IP (except 'localhost') in Computers, showing status Connected
Tthrottle connect disabled on BT but Tthrottle still running on all computers
Temp display disappeared from Tasks
Tthrottle version disappeared from Computers

Action:
Scan address range

Result:
All 3 computers found
Tthrottle still Yes on Find computers
BOINC Yes absent on Find computers

Log entries:
26 August 2010 - 05:50:10 , SendRecieve ---- Recieved from Server: <TThrottle><HN:VGN-FW170J><PV 2.10><AC 0><TC 56><TG 0><NV 0><NA 0><DC 100><DG -1><CT0 55.8><CT1 56.0><GT4 0.0><GT5 0.0>
26 August 2010 - 05:50:10 , SendRecieve ---- Recieved from Server: <TThrottle><HN:Velocity_MX228><PV 2.10><AC 1><TC 62><TG 80><NV 1><NA 0><DC 100><DG 100><CT0 61.2><CT1 54.0><CT2 61.1><CT3 60.0><GT0 80.0><GT4 0.0><GT5 0.0>
26 August 2010 - 05:50:10 , SendRecieve ---- Recieved from Server: <TThrottle><HN:VGN-FZ320EB><PV 2.10><AC 1><TC 67><TG 15664056><NV 0><NA 0><DC 100><DG -1><CT0 64.7><CT1 67.2><GT4 0.0><GT5 0.0>



QuoteCase 2 - Shut down Tthrottle also

Preconditions:
Tthrottle connect disabled
Tthrottle shut down on all computers
Other preconditions as Case 1 above

Action:
Scan address range

Result:
No computers found
Tthrottle & BOINC Yes absent on Find computers


Log entries:
26 August 2010 - 06:06:38 , SendRecieve ---- Recieved from Server:
26 August 2010 - 06:06:38 , SendRecieve ---- Recieved from Server:
26 August 2010 - 06:06:39 , SendRecieve ---- Recieved from Server:


QuoteCase 3 - Bright idea :) eliminate the firewall/application control suite as a cause

Preconditions:
Disabled all Kaspersky Internet Security v11.0.1 protections on all computers
Other preconditions as Case 2 above

Action:
Scan address range

Result:
No computers found
Tthrottle & BOINC Yes absent on Find computers
All "Invalid Socket" (Possibly because the Windows Firewall took over from Kaspersky and slammed the door(s)?)

Log entries:
26 August 2010 - 06:51:45 4+1, Connect ---- Invalid Socket
26 August 2010 - 06:51:45 console, Connect ---- Invalid Socket
26 August 2010 - 06:51:45 dual 32, Connect ---- Invalid Socket
26 August 2010 - 06:51:46 GetUserDirectory3 ---- C:\Users\jjwhalen\AppData\Roaming\eFMer\BoincTasks
26 August 2010 - 06:51:46 GetUserDirectory3 ---- C:\Users\jjwhalen\AppData\Roaming\eFMer\BoincTasks
26 August 2010 - 06:51:46 GetUserDirectory3 ---- C:\Users\jjwhalen\AppData\Roaming\eFMer\BoincTasks
26 August 2010 - 06:51:47 console, Connect ---- Invalid Socket
26 August 2010 - 06:51:47 4+1, Connect ---- Invalid Socket
26 August 2010 - 06:51:47 dual 32, Connect ---- Invalid Socket
26 August 2010 - 06:51:51 console, Connect ---- Invalid Socket
26 August 2010 - 06:51:51 dual 32, Connect ---- Invalid Socket
26 August 2010 - 06:51:51 4+1, Connect ---- Invalid Socket
26 August 2010 - 06:51:57 4+1, Connect ---- Invalid Socket
26 August 2010 - 06:51:57 dual 32, Connect ---- Invalid Socket
26 August 2010 - 06:51:57 console, Connect ---- Invalid Socket
26 August 2010 - 06:51:58 , SendRecieve ---- Recieved from Server:
26 August 2010 - 06:51:58 , SendRecieve ---- Recieved from Server:
26 August 2010 - 06:51:58 , SendRecieve ---- Recieved from Server:
26 August 2010 - 06:51:59 , Connect ---- Invalid Socket
26 August 2010 - 06:51:59 , Connect ---- Invalid Socket
26 August 2010 - 06:51:59 , Connect ---- Invalid Socket
26 August 2010 - 06:52:03 console, Connect ---- Invalid Socket
26 August 2010 - 06:52:03 4+1, Connect ---- Invalid Socket
26 August 2010 - 06:52:03 dual 32, Connect ---- Invalid Socket
26 August 2010 - 06:52:09 dual 32, Connect ---- Invalid Socket
26 August 2010 - 06:52:09 4+1, Connect ---- Invalid Socket
26 August 2010 - 06:52:09 console, Connect ---- Invalid Socket
26 August 2010 - 06:52:15 dual 32, Connect ---- Invalid Socket
26 August 2010 - 06:52:15 4+1, Connect ---- Invalid Socket
26 August 2010 - 06:52:15 console, Connect ---- Invalid Socket
26 August 2010 - 06:52:17 GetUserDirectory3 ---- C:\Users\jjwhalen\AppData\Roaming\eFMer\BoincTasks
26 August 2010 - 06:52:17 GetUserDirectory3 ---- C:\Users\jjwhalen\AppData\Roaming\eFMer\BoincTasks
26 August 2010 - 06:52:17 GetUserDirectory3 ---- C:\Users\jjwhalen\AppData\Roaming\eFMer\BoincTasks
26 August 2010 - 06:52:17 4+1, Connect ---- Invalid Socket
26 August 2010 - 06:52:17 dual 32, Connect ---- Invalid Socket
26 August 2010 - 06:52:17 console, Connect ---- Invalid Socket

I didn't see any <boinc_gui_rpc_reply> anywhere - neither did a string search of the entire log :'(
Title: Re: Remote computers found, but unable to select them
Post by: fred on August 26, 2010, 03:57:41 PM
Quote from: jjwhalen on August 26, 2010, 02:28:31 PM
I didn't see any <boinc_gui_rpc_reply> anywhere - neither did a string search of the entire log :'(
That's not good. Do you use names or numbers for the IP. As far as I can see the first.
Title: Re: Remote computers found, but unable to select them
Post by: jjwhalen on August 26, 2010, 08:30:22 PM
Quote from: fred on August 26, 2010, 03:57:41 PM
Quote from: jjwhalen on August 26, 2010, 02:28:31 PM
I didn't see any <boinc_gui_rpc_reply> anywhere - neither did a string search of the entire log :'(
That's not good. Do you use names or numbers for the IP. As far as I can see the first.


[duh]I knew that[/duh].  Nope, just numbers - here's a "re-read config" message stream from my localhost, with the content of remote_hosts.cfg:

Quote
console

417         8/26/2010 09:41:05   Re-reading cc_config.xml   
418         8/26/2010 09:41:05   Config: GUI RPC allowed from:   
419         8/26/2010 09:41:05   Config:   192.168.0.1   
420         8/26/2010 09:41:05   Config:   192.168.0.2   
421         8/26/2010 09:41:05   Config:   192.168.0.3   
422         8/26/2010 09:41:05   Config:   192.168.0.4   
423         8/26/2010 09:41:05   Config:   192.168.0.5   
424         8/26/2010 09:41:05   Config:   192.168.0.6   
425         8/26/2010 09:41:05   Config:   192.168.0.7   
426         8/26/2010 09:41:05   Config:   192.168.0.8   
427         8/26/2010 09:41:05   Config:   192.168.0.9   
428         8/26/2010 09:41:05   Config:   192.168.0.10   
429         8/26/2010 09:41:05   Config:   192.168.0.11   
430         8/26/2010 09:41:05   Config:   192.168.0.12   
431         8/26/2010 09:41:05   Config:   192.168.0.13   
432         8/26/2010 09:41:05   Config:   192.168.0.14   
433         8/26/2010 09:41:05   Config:   192.168.0.15   
434         8/26/2010 09:41:05   Config:   192.168.0.16   
435         8/26/2010 09:41:05   Config:   192.168.0.17   
436         8/26/2010 09:41:05   Config:   192.168.0.18   
437         8/26/2010 09:41:05   Config:   192.168.0.19   
438         8/26/2010 09:41:05   Config:   192.168.0.20   
439         8/26/2010 09:41:05   Config:   192.168.0.21   
440         8/26/2010 09:41:05   Config:   192.168.0.22   
441         8/26/2010 09:41:05   Config:   192.168.0.23   
442         8/26/2010 09:41:05   Config:   192.168.0.24   
443         8/26/2010 09:41:05   Config:   192.168.0.25   
444         8/26/2010 09:41:05   Config:   192.168.0.26   
445         8/26/2010 09:41:05   Config:   192.168.0.27   
446         8/26/2010 09:41:05   Config:   192.168.0.28   
447         8/26/2010 09:41:05   Config:   192.168.0.29   
448         8/26/2010 09:41:05   Config:   192.168.0.30   
449         8/26/2010 09:41:05   Config:   192.168.0.31   
450         8/26/2010 09:41:05   Config:   192.168.0.32   
451         8/26/2010 09:41:05   Config:   192.168.0.33   
452         8/26/2010 09:41:05   Config:   192.168.0.34   
453         8/26/2010 09:41:05   Config:   192.168.0.35   
454         8/26/2010 09:41:05   Config:   192.168.0.36   
455         8/26/2010 09:41:05   Config:   192.168.0.37   
456         8/26/2010 09:41:05   Config:   192.168.0.38   
457         8/26/2010 09:41:05   Config:   192.168.0.39   
458         8/26/2010 09:41:05   Config:   192.168.0.40   
459         8/26/2010 09:41:05   Config:   192.168.0.41   
460         8/26/2010 09:41:05   Config:   192.168.0.42   
461         8/26/2010 09:41:05   Config:   192.168.0.43   
462         8/26/2010 09:41:05   Config:   192.168.0.44   
463         8/26/2010 09:41:05   Config:   192.168.0.45   
464         8/26/2010 09:41:05   Config:   192.168.0.46   
465         8/26/2010 09:41:05   Config:   192.168.0.47   
466         8/26/2010 09:41:05   Config:   192.168.0.48   
467         8/26/2010 09:41:05   Config:   192.168.0.49   
468         8/26/2010 09:41:05   Config:   192.168.0.50   
469         8/26/2010 09:41:05   Config:   192.168.0.51   
470         8/26/2010 09:41:05   log flags: file_xfer, sched_ops, task, cpu_sched   


I got tired of dynamically assigned IPs gumming up the login works, so I assigned static IPs at the router:

IP                      DeviceName              BTComputerName                   
192.168.0.2         VELOCITY_MX228      4+1
192.168.0.3         VGN-FZ320EB           dual 32
192.168.0.7         VGN-FW170J            console   (this is the BT localhost)

The long remote_hosts.cfg is left over from the days of dynamic IPs, since I didn't want anybody to get left out - I also have a SoIP with 2 disk drives, an XBOX 360 and a PDA on my intranet.  (You see why I set static IPs to the 'computers' for BOINC login purposes ;D)

Two questions for my own education:
Back to you, Fred.
Title: Re: Remote computers found, but unable to select them
Post by: fred on August 27, 2010, 07:22:53 AM
Quote from: jjwhalen on August 26, 2010, 08:30:22 PM
I got tired of dynamically assigned IPs gumming up the login works, so I assigned static IPs at the router:

IP                      DeviceName              BTComputerName                   
192.168.0.2         VELOCITY_MX228      4+1
192.168.0.3         VGN-FZ320EB           dual 32
192.168.0.7         VGN-FW170J            console   (this is the BT localhost)

The long remote_hosts.cfg is left over from the days of dynamic IPs, since I didn't want anybody to get left out - I also have a SoIP with 2 disk drives, an XBOX 360 and a PDA on my intranet.  (You see why I set static IPs to the 'computers' for BOINC login purposes ;D)

Two questions for my own education:

  • In my Case 1, should the scan show Tthrottle even though the Connect to Tthrottle option is cleared?
  • Would the scan still pick up Tthrottle if its Enable BoincTasks option is cleared?

Back to you, Fred.

The scan should show TThrottle regardless of the settings in BT.
But in TThrottle the check MUST be set otherwise nothing happens.
Title: Re: Remote computers found, but unable to select them
Post by: RaulB on August 27, 2010, 01:07:02 PM
Hi guys - I've tried everything I can think of, but no change. From the tests above, maybe I should install Throttle - any thoughts?
Following jjwhalen above, I installed Throttle on all systems
Boinc running on all systems
BThrottle running on all systems with BoincTasks enabled
BTasks only running on localhost
Find finds all Win7 systems (but not the XP system), with Throttle Yes, But no Boinc Yes. Ticking the check boxes to add a system will not hold the tick, and you cant add anything other than local hosts.
Scan finds all systems (including the XP system, where the Boinc Yes,Connected is present). Only the XP box can be added, and it works perfectly.
I am suspecting something in the Win7 Firewall or AV - where to next?
Title: Re: Remote computers found, but unable to select them
Post by: jjwhalen on August 27, 2010, 04:14:21 PM
Quote from: RaulB on August 27, 2010, 01:07:02 PM
Hi guys - I've tried everything I can think of, but no change. From the tests above, maybe I should install Throttle - any thoughts?

Raul,

I won't presume to speak for Fred while he's "out of town", but Tthrottle is a useful utility, it coexists with BoincTasks like it was designed to (because it was) and it at least works around the problem of scanning/finding computers in BoincTasks (as of the latest BT release v0.72).  That is to say BT can use the hostname returned by Tthrottle in a Find to "Add selected" :)  Also, you will be able to see your CPU/GPU temperatures plus throttling activity on your BT Tasks display, as an added bonus.

Tthrottle needs a bit of customizing after you install it - setting up rules for throttling etc., but not too strenuous.  One thing you must do, on the Preference tab, is to check "Enable BoincTasks" for the communication with BT to work.  (On BT's Extra>BoincTasks settings>General tab, you will find a corresponding "Connect to TThrottle" checkbox to enable completion of this link & the display of temperatures.)  Once Tthrottle is up and running with "Enable BoincTasks" checked, on the BT Find computers dialog you will see Yes in the Tthrottle column of each found computer indicating that the handshake is working.  Once a computer is added and active on the main Computers display, the Tthrottle version number (currently 2.10) will appear in the appropriate column (similar to the BOINC version number in its column) as long as BT is receiving data from it.  

Tthrottle installation/configuration is pretty straightforward, and its FAQ has good information.  But if you run into problems I'm sure you can find help in its Questions topic.
Title: Re: Remote computers found, but unable to select them
Post by: RaulB on August 27, 2010, 09:07:19 PM
Thanks JJ - I have got Throttle installed  correctly as per your instructions, and it is working well on all systems. However, it's still only the XP system that is connected to localhost. No sure what I should do next.
Title: Re: Remote computers found, but unable to select them
Post by: jjwhalen on August 28, 2010, 07:03:28 AM
Quote from: RaulB on August 27, 2010, 09:07:19 PM
Thanks JJ - I have got Throttle installed  correctly as per your instructions, and it is working well on all systems. However, it's still only the XP system that is connected to localhost. No sure what I should do next.

Well, I figured out what my problem was: I had (temporarily) installed BOINC 6.11.6(β) on all my hosts, and it wasn't responding (or incorrectly?) to the Scan or Find queries from BoincTasks.  It may be that this function isn't implemented in the beta build, though it is sending XML to BoincTasks readily enough.  I rolled all hosts back to 6.10.58 (Recommended version) and all's well now with "Yes ,Connected" or "Yes ,Password" in the BOINC column of Find computers.  I repeated Fred's debug mode test on a Scan address range and got:
Quote27 August 2010 - 22:34:03 , SendRecieve ---- Recieved from Server: <boinc_gui_rpc_reply><unauthorized/></boinc_gui_rpc_reply>

27 August 2010 - 22:34:03 , SendRecieve ---- Recieved from Server: <boinc_gui_rpc_reply><unauthorized/></boinc_gui_rpc_reply>

27 August 2010 - 22:34:04 , SendRecieve ---- Recieved from Server: <boinc_gui_rpc_reply><unauthorized/></boinc_gui_rpc_reply>

27 August 2010 - 22:34:04 , SendRecieve ---- Recieved from Server: <TThrottle><HN:Velocity_MX228><PV 2.10><AC 1><TC 62><TG 79><NV 1><NA 0><DC 100><DG 100><CT0 61.1><CT1 54.0><CT2 59.0><CT3 61.7><GT0 79.0><GT4 0.0><GT5 0.0>
2
(Yes, only 1 host had Tthrottle running during the test.)  In other developments, I upgraded one of my remote hosts today to Windows 7.  And its BOINC client (v6.10.58) is connecting to BoincTasks without problem.  I'll be interested to know from Fred if <unauthorized> is the correct response to a Scan ???  Or do I still have a problem with my remote_hosts.cfg?  I look forward to BT 0.73 with the expanded logging
QuoteAdd: The Find computers dialog, logs additional information in the log. (IP, BOINC reply). (done V 73 )
.

Regarding your problem, Raul, I don't know if any of that stuff helps - maybe the BOINC client version on your remotes?  I reviewed your posts above, and a few things tickled my brain:

1) If (a) you are running BoincTasks 0.72+, and (b) you have Tthrottle installed on the remotes, you should have a white checkbox and be able to tic it for an "Add selected" -- regardless of the status of the BOINC client, in either a Scan address range or a Find.

2) On the main Computers display, you should be able to do a Computer>New computer, manually enter the IP address & Password, and assign BoincTasks "nickname" (that need not match the computer's real name).  You don't need to do a scan or find for that.  (Never use an IP address for the localhost, enter only "localhost".  Also don't use the IP "alias" 127.0.0.1 - trust me, I learned that one the hard way.

3) The Password entered in the Computers tab must match that in the remote client's gui_rpc_auth.cfg file.  This is NOT the password of your account on the host computer.  Hopefully you have replaced BOINC's original randomly generated password (viz. "57e292b69fff39d4da30ab6c83c9c83e") with something you can remember, and the same one on all hosts ;)  ;D

4) All of Fred's advice above still applies.

5) If you do those things and still can't see your remotes in BoincTasks, I have to wonder about your connectivity.  Are all your remotes on the same subnet as localhost?  Is the subnet mask set correctly?  If not on the same subnet, does your router have a hardware firewall that might be locking off certain ports?  All the standard Network Manager-type questions in that vein.
Title: Re: Remote computers found, but unable to select them
Post by: RaulB on August 28, 2010, 08:04:05 AM
JJ amigo - I am running Boinc 6.10.56 on all my systems. BoincTasks is level 0.71, and TThrottle is 2.10.
I turned off the Win7 Firewall, and everything worked perfectly. Scan found all the Win7 systems, they were connected, Boinc Yes was seen - no problems. My XP system is running Symantec Firewall, and it's setting are obviously correct, but I can't find out what to do on the Win7 firewall settings to get WIn7 to work.
At least we now know that its not Boinc, BoincTasks or Tthrottle - is the &^*&^*% Win7 firewall.
Title: Re: Remote computers found, but unable to select them
Post by: Corsair on August 28, 2010, 08:50:11 AM
Quote from: RaulB on August 28, 2010, 08:04:05 AM
is the &^*&^*% Win7 firewall.

could you update in windows 7 firewall exceptions for TThrottle, Boinc & BoincTasks??, use to be automatic this feature, but probably you'll have to set up manually.

check if is there any other software that could do anything like fire-walling, etc. some king of old stuff from NVidia firewall in NVidia NIC.

because is really strange that, I've a mix of w7x64, wxpx32 and wxpx64 and never had the problem of the firewall each other. any case we'll try to solve your fix.
Title: Re: Remote computers found, but unable to select them
Post by: jjwhalen on August 28, 2010, 02:06:02 PM
Quote from: RaulB on August 28, 2010, 08:04:05 AM
JJ amigo - I am running Boinc 6.10.56 on all my systems. BoincTasks is level 0.71, and TThrottle is 2.10.
I turned off the Win7 Firewall, and everything worked perfectly. Scan found all the Win7 systems, they were connected, Boinc Yes was seen - no problems. My XP system is running Symantec Firewall, and it's setting are obviously correct, but I can't find out what to do on the Win7 firewall settings to get WIn7 to work.
At least we now know that its not Boinc, BoincTasks or Tthrottle - is the &^*&^*% Win7 firewall.

Hola Corsair, I've not seen you on the forum for awhile, it's good to see a post from you again.  Have you been sailing the 7 seas?

OK Raul, I'm glad you've been able to localize the problem at least.  A couple of points:

When you speak of the Win 7 firewall I assume you mean the built-in firewall provided by Microsoft with the OS.  I've used Kaspersky Internet Security on all my computers for awhile now, so the native firewall is turned off.  But now that I have a machine with Win 7_x64, I'll turn off Kaspersky, fall back on the system firewall, and see what I can come up with, as Corsair offered to do.  I'll get back to you on that.
Title: Re: Remote computers found, but unable to select them
Post by: Corsair on August 28, 2010, 08:35:57 PM
Quote from: jjwhalen on August 28, 2010, 02:06:02 PM

Hola Corsair, I've not seen you on the forum for awhile, it's good to see a post from you again.  Have you been sailing the 7 seas?

Hi jjwhalen, still at sea now at anchor in Malamocco (Venice Roads awaiting for Pilot) I had some spare time and could answer to this post.
Title: Re: Remote computers found, but unable to select them
Post by: RaulB on August 28, 2010, 09:51:51 PM
Hi guys , it's wonderful to have such support - many thanks for your efforts. Here's the latest:
1. I have upgraded all Boinc to 6.10.58
2. All the Win7 Firewalls did have entries for Boinc Manager, Boinc Tasks and Tthrottle - I didn't change anything
3. I have left Boinc Tasks at 0371 for the moment (it worked fine when I disabled the Win7 firewalls).
4. There is no other firewall present on the Win7 systems, and they are all running with MS Security Essentials
5. The problem is unchanged - the XP system & the Win7 localhost are seen, but no other Win7 systems
I'm going to bed now - will try again in the morning - Good night amigos

Sunday morning- switched off the Win7 firewall in all systems except localhosts - both Find and Scan found them all (but Find didn't find the XP system) - so it seem to be in 'incoming problem' as local hosts had no problems

In Boinc Tasks, what does a Status of 'Connected, Not Connected' mean?
Title: Re: Remote computers found, but unable to select them
Post by: jjwhalen on August 29, 2010, 03:21:34 PM
Quote from: RaulB on August 28, 2010, 09:51:51 PM
Hi guys , it's wonderful to have such support - many thanks for your efforts. Here's the latest:
1. I have upgraded all Boinc to 6.10.58
2. All the Win7 Firewalls did have entries for Boinc Manager, Boinc Tasks and Tthrottle - I didn't change anything
3. I have left Boinc Tasks at 0371 for the moment (it worked fine when I disabled the Win7 firewalls).
4. There is no other firewall present on the Win7 systems, and they are all running with MS Security Essentials
5. The problem is unchanged - the XP system & the Win7 localhost are seen, but no other Win7 systems
I'm going to bed now - will try again in the morning - Good night amigos

Sunday morning- switched off the Win7 firewall in all systems except localhosts - both Find and Scan found them all (but Find didn't find the XP system) - so it seem to be in 'incoming problem' as local hosts had no problems

In Boinc Tasks, what does a Status of 'Connected, Not Connected' mean?

Raoul,

Sorry for the delay in getting back to you.  I've gotten so used to Eugene Kaspersky's approach to security (and his GUI), that I had to go back and relearn some things about an older rule-based system like Windows Firewall.

My (remote) Win7 system is an upgrade from WinVista, and its firewall inherited settings and options learned by the earlier version (see Corsair's post about this).  So I hope your application control list looks something like mine.  With Kaspersky turned off and the Windows Firewall enabled, I was able to play around and get BOINC to work or fail to work with BoincTasks on my localhost at will.

In Control Panel>System and Security>Windows Firewall>Allowed Programs I have an entry "boinc.exe" which is of course the BOINC core client.  It is set (checked) in the Home/Work (Private) column and the left checkbox.  You said above that you have an entry for Boinc Manager, but you didn't list the core client.  It must be listed and enabled in the left checkbox for BoincTasks on another machine to communicate with it while the firewall is active.  Based on what you've said so far, this sounds like your problem.  If boinc.exe isn't listed, adding it via the Allow another program dialog is straightforward--if you don't find it in the default Programs list you can Browse to the C:\Programs\BOINC\boinc.exe and Open then Add it.  Of course if boinc.exe isn't on the allowed programs list, I don't see how it could communicate with the outside world to download work and report results ;)

When I found boinc.exe in the Allowed programs and features list, setting the left checkbox definitely allows the communication with BoincTasks on my localhost, and resetting it broke the link.  (The same goes for Tthrottle.)

Regarding your Win XP system - I suspect that Symantec firewall (paagh!) is blocking some or all of that 'Find" query but is passing the low-level scan of the subnet.  I used to use Symantec but gave up on it ~3 years ago.  You might check it to see if port 31416 is blocked.

Regarding "Connected,Not connected" (huh?) that is a funny one.  But it means that BOINC is connected but Tthrottle isn't.  If you disable Tthrottle's link to BoincTasks at the remote machine, you'll see Connected,Not coneected (it takes awhile, ~a minute, to show up).

Something I remembered overnight: on BoincTasks Settings>Expert tab, check the "=Reconnect every xx seconds" value for something nonzero (typically 60).

Let me know how you make out with this information.  Also, another recommendation: please consider replacing the Windows 7 basic firewall with some full-featured security suite.  I won't endorse any particular one, but I've already mentioned Kaspersky Internet Security (KIS 2011); there's also ESET's NOD32, and ZoneAlarm Pro.  I will say that Kaspersky licenses up to 3 machines for the single purchase--I don't know about the other products in that respect.
Title: Re: Remote computers found, but unable to select them
Post by: RaulB on August 29, 2010, 04:05:49 PM
JJ amigo - I think you've solved the problem. Not one of my Win7 systems had Boinc client in the Firewall allowed list. I added the Boinc client and now the Scan finds the Win7 systems. The Find still has some problems, but I can live with Scan.
Many thanks for your help - you get 10 stars
One more question - all the systems that I have tested are on the same router (some via LAN and some via WiFi). Can I do the same with a system in a different location, but via the internet?
I'll certainly sleep well tonight - muchas gracias
Title: Re: Remote computers found, but unable to select them
Post by: jjwhalen on August 29, 2010, 07:10:45 PM
Quote from: RaulB on August 29, 2010, 04:05:49 PM
JJ amigo - I think you've solved the problem. Not one of my Win7 systems had Boinc client in the Firewall allowed list. I added the Boinc client and now the Scan finds the Win7 systems. The Find still has some problems, but I can live with Scan.
Many thanks for your help - you get 10 stars
One more question - all the systems that I have tested are on the same router (some via LAN and some via WiFi). Can I do the same with a system in a different location, but via the internet?
I'll certainly sleep well tonight - muchas gracias

Como se dice, "No hay de que."  I believe Corsair hinted and got me thinking that Win7's firewall may be dumber (or more restrictive) than WinVista's version.  And a new computer with OEM Windows 7 might need some help.  But it's always good to remember that Boinc Manager (and now BoincTasks!) is just the control panel.  The core client does all the "heavy lifting," but has no real face of its own ;D

Regarding your question, the answer is "conditional" yes. This forum has members with many host computers, and some on different subnets (Corsair, if I recall, has his computer connected while onboard his ship at sea, and he has others crunching away on shore.)  You can use Scan address range for any valid range of IPs.  (Note the information on this subject in the BoincTasks Manual (http://www.efmer.eu/boinc/boinc_tasks/manual.html) as well as the FAQ.)

The conditional part comes in if the other router, not to mention your own, is firewalled (as mine is).  It would need to have the BoincTasks port open to external communication, and you might have to set up access rights for your localhost's IP.  You might even have to set up a "tunnel" (Virtual Private Net [VPN] or some such), depending on the level of security at the other router.  Of course BoincTasks (Boinc Manager for that matter) knows nothing of any of this.  It expects a clear path to the distant range of IPs on its communications port.

¡Buena suerte Raoul!