On 2017-08-22 21:43, Mayayana wrote:

"Bram van den Heuvel" wrote
| All good questions. Here is a Wireshark screenshot from when I first
| noticed the *outgoing* IP address 104.28.17.56 from my desktop
192.168.1.99
| via my router 192.168.1.1 as shown in this screenshot
| http://img4.imagetitan.com/img.php?i...nshot(603).jpg

I was thinking the same thing as Paul. TCPView will
show what program is going out. You may have programs
or services running that you've allowed to call home,
or that you haven't specifically set not to call home.

You really should look into getting a firewall that allows
you to control outbound traffic.

I use the built-in Windows firewall for that, all you need is an extra
tool called Windows Firewall Notifier, so that you get some notice when
something gets blocked. If I recall, Mayayana, you use Private Firewall?
Is that not just a front end to the Windows built-in Filtering API? i.e.
Same as built-in firewall? Windows Firewall is a bit lame when it comes
to process names (if the process is a 8N3 name, it cannot identify it,
which is the case with Office 2016) and also pretty lame with services
hosted in svchost, but I'm not sure if Private Firewall can do better -
Plus I'd have to migrate all my rules, a real pain...

Best Regards,

--
! _\|/_ Sylvain /
! (o o) Memberavid-Suzuki-Fdn/EFF/Red+Cross/SPCA/Planetary-Society
oO-( )-Oo Pentium of Borg: Division futile; You will be approximated.