Network Security Map Forgets Manually Entered Info

The NIS13 (20.3.0.36) Network Security Map doesn't remember all of device names or category names that I enter manually.  The strange thing is that it doesn’t forget them immediately.  It can take 30 minutes. After that some of them go back to a question mark.  I originally reported this problem last year with NIS12.  See this post:

 

http://community.norton.com/t5/Norton-Internet-Security-Norton/Network-Map-issue-with-NIS-19-6-1-8/m-p/682519

 

I have three HP laptops running Windows 7 Home Edition 64bit.  This happens on all of them. I tried all the recommended solutions (purging the map, reinstalling, etc).  Nothing seems to fix it.

The NIS13 (20.3.0.36) Network Security Map doesn't remember all of device names or category names that I enter manually.  The strange thing is that it doesn’t forget them immediately.  It can take 30 minutes. After that some of them go back to a question mark.  I originally reported this problem last year with NIS12.  See this post:

 

http://community.norton.com/t5/Norton-Internet-Security-Norton/Network-Map-issue-with-NIS-19-6-1-8/m-p/682519

 

I have three HP laptops running Windows 7 Home Edition 64bit.  This happens on all of them. I tried all the recommended solutions (purging the map, reinstalling, etc).  Nothing seems to fix it.


elsewhere wrote:

Please try the following solution:

 

http://community.norton.com/t5/Norton-Internet-Security-Norton/Bug-with-Network-security-map/m-p/878066/highlight/true#M227127

 

Let us know how you go.

 

 


Thanks for the link.  I tried the solution.  Unfortunately, it didn't work.  On one laptop I made the updates and restarted. The question marks returned on some of the devices.  On another laptop I purged the map and all the old devices returned after about 30 minutes.  Some of them I have not used in a while.


car825 wrote:

Thanks for the link.  I tried the solution.  Unfortunately, it didn't work.  On one laptop I made the updates and restarted. The question marks returned on some of the devices.  On another laptop I purged the map and all the old devices returned after about 30 minutes.  Some of them I have not used in a while.


That additional information about the old devices returning was really helpful, car825. I've reproduced the same behaviour on two Windows 7 32-bit machines. It appears that the only way to apply the manual updates to the Network Security Map is by editing and updating the map and then immediately rebooting the system to commit the changes. This is an issue that Symantec will need to look into further.

 

Please try the following workaround. There are two steps - completely purge the map first and then rebuild it using a system reboot to commit the map changes that you've made.

 

Step 1 - Completely purge the Network Security Map:

 

  1. Close all open applications as you are about to reboot the system.
  2. Open NIS > Settings > Network > Network Security Settings > Network Security Map > Purge and click Yes.
  3. Close NIS and then reboot your system.

Follow the instructions above precisely. When the system has rebooted, proceed to Step 2.

 

Step 2 - Rebuild the Network Security Map:

 

  1. Close all open applications as you are about to reboot the system.
  2. Open NIS > Advanced > Network Protection > Network Security Map.
  3. Update the details for the devices with question mark icons or wrong information and click Close. Do NOT open the Network Security Map window again until after you have rebooted your system.
  4. Close NIS and then reboot your system.

 

You only need to perform Step 1 once as this completely purges your Network Security Map. After that, you can perform Step 2 as many times as you wish. The important thing to remember here with Step 2 is that once you click Close on the Network Security Map window after editing and updating any device details, you must reboot the system. Resist the urge to double-check your security map changes; you can fix any mistakes that you may have made after the system reboots. I've tested typos and wrong categories and all changes were applied successfully to the Network Security Map when I followed the Step 2 procedure above.

 

Please try the workaround above and let us know how you go.

 

Thanks

 

 


elsewhere wrote:

car825 wrote:

Thanks for the link.  I tried the solution.  Unfortunately, it didn't work.  On one laptop I made the updates and restarted. The question marks returned on some of the devices.  On another laptop I purged the map and all the old devices returned after about 30 minutes.  Some of them I have not used in a while.


That additional information about the old devices returning was really helpful, car825. I've reproduced the same behaviour on two Windows 7 32-bit machines. It appears that the only way to apply the manual updates to the Network Security Map is by editing and updating the map and then immediately rebooting the system to commit the changes. This is an issue that Symantec will need to look into further.

 

Please try the following workaround. There are two steps - completely purge the map first and then rebuild it using a system reboot to commit the map changes that you've made.

 

Step 1 - Completely purge the Network Security Map:

 

  1. Close all open applications as you are about to reboot the system.
  2. Open NIS > Settings > Network > Network Security Settings > Network Security Map > Purge and click Yes.
  3. Close NIS and then reboot your system.

Follow the instructions above precisely. When the system has rebooted, proceed to Step 2.

 

Step 2 - Rebuild the Network Security Map:

 

  1. Close all open applications as you are about to reboot the system.
  2. Open NIS > Advanced > Network Protection > Network Security Map.
  3. Update the details for the devices with question mark icons or wrong information and click Close. Do NOT open the Network Security Map window again until after you have rebooted your system.
  4. Close NIS and then reboot your system.

 

You only need to perform Step 1 once as this completely purges your Network Security Map. After that, you can perform Step 2 as many times as you wish. The important thing to remember here with Step 2 is that once you click Close on the Network Security Map window after editing and updating any device details, you must reboot the system. Resist the urge to double-check your security map changes; you can fix any mistakes that you may have made after the system reboots. I've tested typos and wrong categories and all changes were applied successfully to the Network Security Map when I followed the Step 2 procedure above.

 

Please try the workaround above and let us know how you go.

 

Thanks

 

 


This worked perfectly.  Thanks much!

You’re welcome.