Not what you are looking for? Ask the experts!
Windows 10 1803 Norton firewall broken on "private" network
With the Windows 10 upgrade from 1709 to 1803, suddenly the Norton Security firewall started blocking file sharing and ICMP echo (ping) requests. The network is set up as a windows "private" network, with a static IP V4 address set. Further investigation (adding monitor and allow rules in the firewall), showed that the traffic was no longer being processed by the private network (local subnet) rules. It is as if the firewall is simply not recognizing traffic as coming from the local subnet. Just for the heck of it, I changed the IP address to DHCP acquired, and traffic was now being processed correctly by the private rules. Unfortunately, I prefer to set static addresses because of some native sockets apps I use.
Has anyone seen anything similar?
Strangely enough, this problem only exists on one 1803 machine of several I have. Windows 10 Pro, Intel 8700, Asus Z370 mobo, latest drivers and BIOS. Problem exists on a 1709->1803 upgrade, as well as a clean 1803 install. IP addresses and netmasks double checked.
Any enlightenment would be appreciated.