OK, I finally took the plunge and upgraded from NIS 2012 to 2013 a couple days ago. No major problems yet, but one annoyance ...
When I try to open a Microsoft Office 2007 document that's stored on a NAS drive on my local network, it just hangs on the splash screen. After giving it several minutes, I have to use Task Manager to close the Office app. Opening an Office document on the local hard drive does not do this. If I turn off the "Microsoft Office Automatic Scan" setting the NAS file problem immediately goes away. I think I had Office scans turned on with NIS 2012 and never had this problem. Running Windows 7 SP1.
I couldn't find similar complaints with a quick search, just wondering if anyone else has seen this.
I'm not sure but this could be one of the improvements to v20. Norton is trying to protect you by checking everything that is coming into your computer regardless of origin.
Turning off the scan shouldn't cause any problems so long as all of the documents are local. If you go online to get things it might be wise to turn that feture back on - just in case.
Try giving your NAS full trust in the network security map. If it has a fixed IP Address, also check the box to exclude it from IPS scanning (Intrusion prevention firewall).
BTW- The document scan is off by default now because it really is not very helpful anymore with the way Norton protects you on demand for any files accessed. I think it is mostly there because people have used it so long they feel better having it although I don't know of a single case where the document scan somehow caught something that the product would miss.
Thanks, giving the NAS full trust on the network map did it. It has a DHCP assigned IP address so I didn't try the IPS exclusion. But yeah, I think I'll leave the Office scan turned off since I've seen several comments on here saying that it's not that important any more.
I'm glad that worked and since it's your NAS you should be able to trust it.
I have personally seen a performance increase in large file transfers across the network by turning off the IPS scanning so you may want to keep that in mind, especially if you use it as a backup destination.
I have not had any troubles with having a mix of fixed and DHCP assinged addresses on any of my networks.
Obviously it would be a pain to assign an address to a laptop that you use in different locations.
But it seems like windows always goes for the same address that was used before so after setting up the systems with fixed IP's, as long as the others can connect the first couple times I never have a problem with conflicting addrsses regardless of what system boots first.
Just keep that in mind if you ever feel that the transfers are not as fast as they should be in certain situations.