In the Remote ports drop-down list, type 88.On the Ports and Protocols tab, in the Protocol drop-down list, click UDP.In the Remote ports drop-down list, type 88, 135, 139, 445.On the Ports and Protocols tab, in the Protocol drop-down list, click TCP.On the General tab, type a name for the rule and click Allow this traffic.In the Configure Firewall Rules dialog box, click Add.Beside Network Threat Protection, click Options > Configure Firewall Rules.In the client, in the sidebar, click Status.To manually enable clients to browse for files and printers Interestingly, I discovered a workaround in that I can white-list all traffic from the subnet the device is on, which meets my needs, but I'm still curious as to why my original approach wasn't successful.Ĭan anyone suggestion a reason why the above endpoint protection rules won't allow me to access windows file shares on the device? Traffic has been blocked from this application: IPv6 driver (tcpip6.sys) When I try to connect, two endpoint protection dialogs pop up saying: Traffic has been blocked from this application: NWLINK2 IPX Protocol Driver (nwlnkipx.sys) I've added a rule (and moved it to the to ensure priority) allowing all hosts access on TDP ports 137,138,138,445 and another rule allowing UDP access on ports 137,138,139. That share is visible locally on the machine and externally visible when I disable the endpoint protection agent. I'm using simply file sharing to expose a particular directory. I'm having some difficulties exposing a standard windows file share on a Windows Embedded Standard 2009 device that is running Symantec Endpoint Protection Agent 5.1.
0 Comments
Leave a Reply. |
Details
AuthorWrite something about yourself. No need to be fancy, just an overview. ArchivesCategories |