Norton recognises my wired internal network as "public"?

I have been having many problems since the latest version of Norton installed, however didn’t stop to think it might be related, as the problems have been increasing slowly…

I now see that Norton is set to “restricted”, because it thinks my private wired network is public… This must have changed without warning and has caused me and others in the household endless problems…

Hello Dave. Although I am no longer on version 24.xx to give you real time info, this, along with other “built-in” automatic decisions made with the 24.xx version is the reason I reverted. The NEW Norton/Avast engine decides for us how our networks should be used is the bottom line, I wouldn’t expect that to change anytime soon, if ever. Changing your network to Private will only be reverted back to Public the next time you reboot your machine no matter what settings you change. My suggestion is to revert all your machines back to version 22.24.8.36, disable automatic updates on them all, and manually download/install definitions to stay current. I am doing so on my machines until the 24.xx functionality gets to a point where I can again use my 2 NAS devices and 2 rack servers again without Norton killing their connections. If you wish to revert we can assist you with how and links to those resources.

There are those who will say Norton is “solid” for them and for those few that may be the case. Being forgotten are the users like you who don’t have time to deal with constant issues where nothing we do will make the changes needed and it stay that way. This version is NOT pro-active in any manner and should be pro-active if nothing else. There are those advances users who have home networks with attached storage, smart devices connected and controlled, working remotely. They also don’t have time for troubleshooting when their products that protect them do not perform in a manner where that happens.

SA