I suggest to either accommodate the MBCCRules executable to create the ACL as both private and public to apply for either network (if possible, i am not entirely sure how the libraries you've imported work): It seems that the MBCCRules creates the ACL as private only. It also seems to explain why people have intermittent functionality, as each could have their network defined either of the two ways. When i checked my network type in control panel > network & sharing center, i've seen that my network profile is set to public, while the ACL was configured on private, this lead to the ACL to not function as intended. Windows 10 places higher security in the public profile as to protect the machine from unsecure networks such as a wifi spot in a restaurant for example. The issue arrives from how Windows 10 defines network types, public and private (which is defined as a work or home LAN networks). Hello again, i have found the issue and it did had to do with the Firewall ACL.
0 kommentar(er)
