In this case the best way to overcome the issue would be deleting the node which is considered to be old from the network tree and re-scanning the network. This will ensure that both the old and the new nodes are added and inventoried correctly.

Hi Jeff,

I usually move the old computer to another group called "Spare Systems" and scan for the new one. The problem with deleting the old machine is that we have added a lot of custom data to each node (warranty details, purchase date, asset tag. etc.) and it will need to be entered again if deleted.

Lately I have been having another issue with my weekly scans. Sometimes DHCP assigns an ip address of an offline client to another client. NIA while scanning, overwrites the offline client details with the other clients details. This ruins my network summary and my reports are no longer accurate.

Please help!

Aun said: I usually move the old computer to another group called "Spare Systems" and scan for the new one. The problem with deleting the old machine is that we have added a lot of custom data to each node (warranty details, purchase date, asset tag. etc.) and it will need to be entered again if deleted.

This doesn't look logical to me. If the new node has a different network name than the old node (which IS logical), and it only gets the same IP address, there will be a new node created.

Aun said: Lately I have been having another issue with my weekly scans. Sometimes DHCP assigns an ip address of an offline client to another client. NIA while scanning, overwrites the offline client details with the other clients details. This ruins my network summary and my reports are no longer accurate.

In Settings -> Connection, check that you have "Connect by" node's DNS name enabled, not by IP. Once the erroneous detection of the node occurs, use "ping NodeName" command to make sure that the new IP address is returned, not the old one. In this case the node will be scanned correctly and placed in a separate entry.

1) Both nodes have different IP addresses and computer names but the new node's computer name previously belonged to the old node. Maybe this is why it replaces the old node's details instead of creating a new one?

2) The "Connect by node's DNS name" option was enabled. I tried removing the check mark on "Try both methods if one fails". Will let you know if it works.

Thanks!

Aun said: Maybe this is why it replaces the old node's details instead of creating a new one?

Absolutely. And I really consider this to be correct, as you assigned the same old name to the new node.

I have a similar problem to Aun in so far as I only use DNS names to perform a Network scan. Unfortunately due to the nature of DNS sometimes a look up of a DNS name is incorrect and returns an IP address which is being used by another computer. The result is that some computers show another computers details.

We might be able to fix this in future by hard-tagging scanned computers, which is another drawback of this approach. But you actually replied to your own question, that behavior is caused by DNS caching, not much can be done about it now.