Ummmm, BOINC's installer doesn't fiddle around with the firewalls rules. BOINC does not create a network share to the data directory. That must be a left over from something else.
What is supposed to happen is when BOINC is first launched it starts all the components that need access to 31416 in a test mode designed to trigger the firewall's consent dialog. It appears the firewall software is being pretty liberal with its default rule set. ----- Rom -----Original Message----- From: boinc_dev [mailto:[email protected]] On Behalf Of Charles Elliott Sent: Friday, February 13, 2015 3:15 PM To: [email protected] Subject: [boinc_dev] No information from BOINC or its data directory for aweek. After a new version of BOINC is installed: 1. The BOINC data directory is inaccessible from any other computer. Deleting the share and re-sharing the directory has no impact. A soln that works is to give "Everyone" sufficient security privileges manually using the directory properties dialog box. 2. Boinccmds such as "boinccmd -host remoteComputer -get_host_info" no longer work as long as the firewall on the remote computer is active. If two of the four incoming firewall rules that are marked in red, specifically disallowing connections to BOINC, are changed to allow connections, then boinccmd functions again. 3. The firewall rules added by the BOINC installer allow access to all ports. Why does any external program need access to BOINC thru any port other than 31416? Charles Elliott _______________________________________________ boinc_dev mailing list [email protected] http://lists.ssl.berkeley.edu/mailman/listinfo/boinc_dev To unsubscribe, visit the above URL and (near bottom of page) enter your email address. _______________________________________________ boinc_dev mailing list [email protected] http://lists.ssl.berkeley.edu/mailman/listinfo/boinc_dev To unsubscribe, visit the above URL and (near bottom of page) enter your email address.
