Hi Dave,
I'm surprised Linksys does not have that configuration option.
Is your laptop connected wired or wirelessly?
I had not tried browsing a shared folder while the map was stuck in "refresh".
Do you see this by simply restarting say your laptop, does the security map on the desktop update its status for the laptop when it is back online?
Allen
I just looked again at my router settings and I don't see anyone to reserve or specify an address to a device.
Of course I have a MAC filter but thats just for allow and deny.
All my laptops are usually wireless, it's rare for me to need to plug them in to a LAN.
The only one I ever really monitor is my wifes at home. I check the statis on it remotely so I don't have to actually "use" it.
I never tried monitoring it through a restart or anything else. I do updates, backups, and matinence on it every week or 2 and in between just check the remote monitoring once in a while to make sure it's on and being updated. Or look to make sure nothing was detected or quarantined that I may have to do some extra checks or scans.
Although I'm sure she would say something if it ever had a red warning or anything.
On my laptops I never bother, I just look at the icon when I start it.
DaveH wrote:I just looked again at my router settings and I don't see anyone to reserve or specify an address to a device.
Of course I have a MAC filter but thats just for allow and deny.
Interesting. I am sure glad I have that option on my router because I have one special "weather" hub device which used to have problems when the IP address changed. That is actually when I first started configuring static IP addresses on the router. 
atomicbubba, sorry about the recent rambling.
Please let me know on my last post which is here. I just want to verify for sure what your final results are and then I can provide some guidance on configuring a firewall rule which should then resolve this for you.
Best wishes.
Allen
HI atomicbubba,
Earlier in the thread, delphinium raised a question about whether you have any other security software installed on your desktop. Please see:
I had not seen a response from you on this. Do you have any other security software installed?
I want to make sure we have all the bases covered.
Best wishes.
Allen
Both showed full trust. I did lock down addresses but the only thing that happened was the green circle ended up on the new laptop.
atomicbubba wrote:Both showed full trust. I did lock down addresses but the only thing that happened was the green circle ended up on the new laptop.
Hi atomicbubba,
Thanks for clarifying. Again you are getting different results on the wired laptop test than I am which is a bit confusing.
I really need to know if you have any other security software installed besides NIS. Do you have any other 3rd party firewall installed besides NIS? Also, please confirm that your Windows firewall is OFF as it should be.
Delphinium mentioned to you before that it is not normal when you uninstall and reinstall NIS to have to enter the product key again as it should be picked up automatically. This leaves a concern on our part about the overall status of your NIS installation.
I see the same problem as you when I connect my laptop wirelessly and the firewall rule I am proposing resolved that problem completely. But before I give you that procedure I need to know about other security and/or firewall software you might have installed besides NIS and to confirm the status of your Windows firewall.
Otherwise if I give you that procedure now and it does not correct the problem it will cause more frustration on your part.
Best wishes.
Allen
only nis and windows fire wall is off
HI atomicbubba,
Thanks for confirming.
OK, please try the following on your laptop.
Go into Network Settings > Smart Firewall > Advanced settings and click Configure to the right. Then when the next window comes up click on General Rules > Configure. In the General Rules window click on Add near the bottom left.
On the first screen click on Allow (should be the default), then click Next. Click on Connections from other computers. There should be a checkmark on this then and click Next. On the next window click on Any computer in the local subnet and then Next.
On the next window select TCP from the drop down list on the upper left. Click on Only communications that match all types and ports listed below. There should now be a checkmark on this selection. Click on Add and on the Specify Ports window click on Individually selected ports. There should now be a checkmark on this selection. In the box provided type in 31077 and OK. This should match the port number configured in Network Settings > Network Security Map > Communication Port. Then click Next again.
On the next window click on Create a security History log entry if desired and click Next.
On the next window type in a name for your firewall rule and Click Next.
On the final window click on Finish. Now back on the General Rules window keep clicking on Move Up until this new rule is at the top of the list. Then click OK. Click OK out of the Advanced Settings window and OK again on the Settings window.
Check for the problem again. You can also add this same rule to your desktop but in my testing I did not need to do so to resolve the problem.
Please let me know your results.
Best wishes.
Allen
It's 2:30 in the morning and I am happy to announce that it works perfectly. I have shutdown my system and restarted three times with everything seeing everything and everything with security status. Thank you so much for your time. It seems like our combined approach should strike fear into the heart of Norton. You have accomplished what they couldn't!!!! Have a great evening (Morning actually!).
I hope Norton fixes this in the next patch. BTW, where should I apply the fix? The one not getting the remote monitoring (XP Lappy) or the one that get the remote monitoring (but not being monitored by the other) (Win7 Lap)?
Tywin7 wrote:I hope Norton fixes this in the next patch. BTW, where should I apply the fix? The one not getting the remote monitoring (XP Lappy) or the one that get the remote monitoring (but not being monitored by the other) (Win7 Lap)?
In the testing I've done, the only one which seems to need this is the one which is connected wirelessly, typically the laptop.
I would only add the rule to the desktop if it is actually required to solve the problem.
Best wishes.
Allen
Hi atomicbubba,
You are most welcome. 
I will also reply again after I hear back from Symantec. I think there is a problem here which should be resolved with NIS. I honestly only consider the addition of a manual custom firewall rule as a workaround.
Best wishes.
Allen
AllenM wrote:
Tywin7 wrote:I hope Norton fixes this in the next patch. BTW, where should I apply the fix? The one not getting the remote monitoring (XP Lappy) or the one that get the remote monitoring (but not being monitored by the other) (Win7 Lap)?
In the testing I've done, the only one which seems to need this is the one which is connected wirelessly, typically the laptop.
I would only add the rule to the desktop if it is actually required to solve the problem.
Best wishes.
Allen
How about if BOTH are connected wirelessly?
Tywin7 wroteHow about if BOTH are connected wirelessly?
Hi Tywin7,
In that case you will probably need the custom firewall rule on both computers. This was indicated when I said the computer which is connected wirelessly. It would stand to reason if both are wireless connections that you need the rule on both. 
Best wishes.
Allen
Very, very nice work on an extremely complicated problem, AllenM. Congratulations on a well-earned and hard-won solution.
I am thinking what would happen if you changed the network map to use port 80, the default internet port.
Hi Tywin7,
I would not recommend changing this port number. NIS uses a special port for a purpose to uniquely identify its purpose.
Though we do not normally recommend changing firewall rules, in this case that is far less risky (especially with the highly targeted rule I recommended) than changing port numbers.
Best wishes.
Allen
AllenM wrote:Hi Tywin7,
I would not recommend changing this port number. NIS uses a special port for a purpose to uniquely identify its purpose.
Though we do not normally recommend changing firewall rules, in this case that is far less risky (especially with the highly targeted rule I recommended) than changing port numbers.
Best wishes.
Allen
Ah OK. I thought if I used port 80, which is by default, already open, it might work. I highly urge Norton to make their default component work!!! Strange thing is that the WIn7 can see the XP remote monitoring but not vice versa.
Hi Tywin7,
Port 80 might work but I do not recommend changing that to such a common port. In this case I think the firewall rule is much more targeted and with less potential scope than changing the port number.
As I mentioned earlier I am starting a dialog with Symantec about this issue on the side.
When I tested this it only affected the ability to see security status on the computer which was connected wirelessly. I cannot say if this is the "only" time it happens but that was all I was able to reproduce.
There are default firewall rules (read only) which get created when you enable Remote Monitoring. I think the problem might light in how the default rules are created but hopefully we'll know more later on.
Best wishes.
Allen
I've made this tongue in cheek suggestion in norton product new idea ;) http://community.norton.com/t5/Norton-Product-Ideas/Network-map-Remote-monitoring/idi-p/307538