Hello!

I have problems with using BOINCtasks to control win 10 computers.
It works fine with Linux.
The Win computers did have contact once with BOINCtasks - I still have them in the "Computer" list. I had to click on OK in the Win10 Firewall for that.
But after restarting the BOINCstats computer it shows only the lightning bolt icon.

I did the ususal thing - remote_hosts with IP and gui_rpc_auth with the PW in programdata/boinc.

I am totally new to Win10 so maybe I miss something.


edit: I tried the toolbox from eFMer.
As long as the program is open on the remote computer, BOINCstats can find it, but the box to add the computer is greyed out and I cant check it.
If I deactivate the toolbox the remote computer cannot longer be found.

Not found the reason. Again back to the lightning after half an hour not looking at it.

I am totally new to Win10 so maybe I miss something..

Firewall perhaps?
Make sure everything can communicate with each other. BOINC default parts (boinc.exe, boincmgr.exe, boinccmd.exe etc.) require communication on TCP/UDP 31416. I'd suspect BOINCtasks needs that as well, and else you'll have to contact Fred on how to do that. We're not making it or making it work.

---

Had to set an 'incoming' exception rule in the W10 firewall for boinc.exe

---

Coelum Non Animum Mutant, Qui Trans Mare Currunt

Had to set an 'incoming' exception rule in the W10 firewall for boinc.exe

And that will apply to any program that uses the Controlling BOINC remotely protocol - BOINC Tasks, BOINC View, BOINC Manager...

Oddly [with all 'securest' fanfare from MS], no, did not have to set anything for that device v.v. BOINCTasks. Remote BT can now query the W10 device boinc client [with of course the remote rpc setting in cc_config.xml i.e. <allow_remote_gui_rpc>1</allow_remote_gui_rpc>] and from that W10 device, BT can connect to any other device on the LAN, i.e. no outgoing settings needed either , demonstrating W10 Firewall "still" comes across as a Swiss cheese to me.

Edit: And to confirm, just tested the BM and it was unobstructed to connect to the client running on the W7 laptop... IP+PW all that was needed to be entered in the 'select computer' box.

---

Coelum Non Animum Mutant, Qui Trans Mare Currunt

Had to set an 'incoming' exception rule in the W10 firewall for boinc.exe

Depends exactly what rule you set there. If it was the minimal ports 80, 443 for http/https, then the remote protocols couldn't (shouldn't) have been able to connect. If you set ports 80, 443, 31416 - or 'all ports' - then it should work.

The holes in the swiss cheese are for outgoing connections - BOINC Tasks/View/Manager calling out from the machine they're running on, into the remote machines.

All you do [I did] is

1) Add an app or feature through WF
2) Change Settings (to activate the Allow another app... button)
3) Browse to the app, select and add

As an additional feature you can select the Network type and choose to allow it on Private [default], and or Public and OK that.

Done.

Just to be sure nothing gets nervous in the system, or causes surprises and head scratching when the Anniversary build comes out [August 2], or any of the Insider fast ring builds gets pushed, now on 14372, have now added BT and BM too, for private network only. Of course you can use advanced rule facility to narrow things down, but default, not required.

---

Coelum Non Animum Mutant, Qui Trans Mare Currunt

I put them on LAN and it more or less works (after reattaching 2 again to boinctasks).
Now even the one on WLAN(wifi) only works fine.

Whatever the reason was... thanks.