twixt wrote:
Edward572 wrote:
SendOfJive wrote:
I would try unconnecting all the other devices, then purging the Network Security Map, then reconnecting the other devices to the network. Norton should see them as you connect them.
Thank you,
I tried that as well, I purged the cache for the Network Security Map, and then restarted computer and then allowed it to re-
find the devices after they were off and then turned on.
I have read a few post about similar issues and tried these solutions with no luck.
I think what it needed is the software FULL removed and a clean install of NIS 2013, still looking for the link that I had found which related to a removal tool
Hi, Edward572. A couple of ideas:
1. Are you running DHCP on your Router to assign IP addresses to connected devices? If so, have you ensured there are no conflicting IP addresses?
One of the problems with having items return to the DHCP Pool when their leases run out (dynamic DHCP) - is this may create a conflict with devices which cache IP Address data (such as the NIS Network Security Map). This is especially the case with routers that do not have the brains to assign completely-unused IP addresses to newly-discovered-devices until such time as the entire DHCP IP-range has been assigned at least once.
2. The usual fix for the above is a router firmware upgrade. If that does not solve the problem, making DHCP Reservations on the Router for *all* the standard items on your network is the usual solution to this problem.
Note: Routers that reassign IP addresses in the DHCP pool "from the bottom up" will recreate conflicts when older devices are off - their leases have expired - and fresh devices are added to the network - unless the older device IP Addresses are properly reserved by the Router. Thus, it is highly recommended to reserve IPs on routers that work as described at the beginning of this paragraph - if those older devices which are assigned IP addresses by the Router's DHCP are truly items you will see regularly - but those items may be off for long enough periods of time that their leases expire.
Solving the problem of conflicting IP addresses by "brute force" can be done by manually purging the IP and ARP caches on the router itself and on each machine on the network. However, I consider this far too much trouble to be worth the effort - and solve the problem by simply making DHCP reservations on the Router - as a "bulletproofing" procedure - for any items regularly assigned to that Router on that network segment.
3. When it comes to network drivers "new" does not necessarily mean "better" when it comes to WXP. Drivers designed for W7 or later may end up having their IP/ARP caches managed using a different methodology than WXP. Thus, a driver designed for W7 may not keep the WXP IP/ARP caches up-to-date when DHCP is updated by the router - thus leading to conflicts.
As a result, it is entirely possible that using a "newer and supposedly better" driver is a potential source of your problem. I have run into this exact issue with RAID Hard Disk Controller Drivers, Cardbus Card Drivers and Wireless Network Drivers - where I specifically had to experiment with the various released driver versions until I found something that ran reliably under WXP. The newest "good for XP" driver is sometimes 1-3 levels back from the newest release..
DO NOT assume the hardware manufacturers are smart enough to keep the crucial differences between WXP and W7 straight on their own. Too many drink the Microsoft Kool-Aid and assume that "it's certified for W8/W7, it'll work with everything previous" when that is clearly not the case.
Hope this helps.
Thank you for your comments
My Backgroud (Network Administrator) (A+ Certified)
I use static IP's and it worked until I updated my wireless card drivers. I have even used the old drivers and un-installed Purged NIS 2013 with Add/Remove and Norton Software Removal Tool.
Router reset cleared old information, flashed.
1. Worked at first (changed driver), Stopped working.
2. Purged the Network Security Map (50 Times), does not find dives.
3. re-installed Wireless Card drivers, reinstall NIS2013 (10 Times)
This feature works fine on Windows 7 (x64), Windows 7 (x86) computers in my house, but no luck with WinXP.
It also stopped my one computer from sharing, and the other works, I could connect from the problem computer to the Win 7 (x64), but not from the (x64) to the windows XP (x86).
I see this issue in a few posts and have not found any post to fix problem.
If I want to have this work, I need to reinstall windows to get the NIS 2013 out of the registry, install the Wireless network card with the correct driver and then re-install NIS 2013, AND I NOT going there, since I just wasted about 24-36 Hours trying to set this up. How about a complete removal of this software (NIS2013) not just deleting the folders and removing the name from ADD/REMOVE.
Not too Impressed!
Edward