Calls wrote:
so does one have to initialize the network security map?
Hi, Calls. Here is my experience with how this works:
1. If you install or upgrade NIS with an active LAN connection in place, NIS will automatically configure itself to "see" that network. Thus, the intermediate filter drivers will be installed and the NIS installer will autofill the Firewall entries with the items necessary to perform network discovery.
2. If you install NIS without an active network connection in place, NIS will not automatically configure itself to "see" a network. In that situation it is necessary to plug in the network cable, try and establish a network connection to "the outside world" (IOW, confirm that your browser, external-email and Live-Update processes work properly) and then initialize the Network Security Map. During the Initialization process (which asks you to wait while that activity is performed), NIS does all the "housekeeping" that it would normally do during the installation phase if you were connected to a LAN at that time.
Observations:
1. When I download the latest-'n-greatest Installation Executable for the version of NIS I want to install on a machine - and copy that file to a CD-ROM so I can install it on "virgin" machines - where those machines are not yet connected to the network so they are not at risk of infection during the NIS installation process - I have to Initialize the Network Security Map before I can do anything on the LAN - once I plug the network cable from the Router into the Machine.
2. In the above scenario, I can browse the web, get Live Updates, use Outlook Express or Outlook to pick up my external mail from my ISP - but I cannot share files, see other machines on the LAN or connect to Network Printers unless and until the Network Initialization process is completed.
3. In some circumstances, NIS does not properly install the Intermediate Filter Drivers. This is known to occur if the Network Card Drivers are installed after NIS is installed - on a virgin OS installation. In that case, NIS will not "see" its connection to the network until something tells NIS to "check your integration with the network - and bring yourself in sync with the rest of the OS". Initializing the Network Security Map is one way to perform this operation.
Note: Rebooting the machine performs a similar integrity check - and is sometimes required for NIS and the OS to "get their brains in order". 
4. Older versions of Network Card Drivers are often the cause of problems with the automatic network-integration process. This is especially true with Network Cards based on Realtek Chipset designs. I strongly recommend the user research the network card chipset used by their machine - download the latest-'n-greatest Network Card Drivers from the Network Chipset Manufacturer's website - and install those before installing NIS.
Note: Do not rely upon the motherboard manufacturer's website to have the latest network card drivers for your motherboard. It is quite common for the motherboard manufacturer's website to be completely out-of-date in this regard. This is especially true with network drivers under continuous development - such as the Marvell Yukon Network Chipset drivers, the Realtek Network Chipset drivers and the Intel Network Chipset drivers.
Hope this helps.