When listing laptops, you sometime get 2 inventory items per computer. I figured that it's probably that laptops have 2 Network Interface Cards: LAN and Wi-Fi. I assume those with duplicate are the ones having the 2 NICs connected to the network.

One of the NICs has "No open ports for this device were found to be responding." I can't tell which one.

The situation exists since at least the last 3 Spiceworks upgrades

Situation:

How do you deal with duplicates caused by laptops having 2 NICs?

Workaround:

None. Changing the user habits (e.g., stop using one of the 2 NICs) is unfortunately out of question.

Instead of an IP range, you can put the name of a computer in the range. If you want to scan more than one computer, the trick is to use spaces between the names, not commas as you need with multiple IP ranges.

We're using DHCP so I assume the NIC using the hidden IP would come back after the DHCP lease is over.

Yes, it definitely would and using DHCP would definitely be a problem if the users moved around a lot from one location to another and were subject to IP address changes. For example we have 14+ locations with a ton of VLANS. If someone moves across the building on WIFI they occassionally end up with a new IP. Our DHCP leases are extremely short for that reason on our WIFI.

Gele wrote:

Also, assuming we'd setup fixed IP addresses. What if users change their habit and connect using the NIC with excluded IP?

If you come across a user who changes their habits... fire them. Users never change. :)

I've only got a couple systems (servers) that I track which have multiple IPs so excluding one of the IPs wasn't too big of a deal. We're talking about using SW in multiple locations for end user machines at some point so we're going to run into the same issue.

I wonder if having one of the two connections not register itself with DNS would help solve the issue by having that IP/machine not show up with a name and therefore make it easy to exclude from a report.

I wonder if having one of the two connections not register itself with DNS would help solve the issue by having that IP/machine not show up with a name and therefore make it easy to exclude from a report.

Instead of an IP range, you can put the name of a computer in the range. If you want to scan more than one computer, the trick is to use spaces between the names, not commas as you need with multiple IP ranges.

Instead of an IP range, you can put the name of a computer in the range. If you want to scan more than one computer, the trick is to use spaces between the names, not commas as you need with multiple IP ranges.

It works like a charm, it's just a pain to have to do this for every laptop. We must have >30 of them.