Primary IP selection incorrect for dual‑NIC assets

[BLUEID]

Subject: Primary IP selection incorrect for dual‑NIC assets
Description:
When scanning assets with two NICs (one for internal machine communication on 192.168.x.x and one for corporate LAN on 10.x.x.x), Lansweeper consistently selects the 192.168 address as the primary IP.
Expected Result:
The primary IP should be the corporate LAN address (10.x.x.x), which is the interface used to communicate with the Lansweeper server and is relevant for asset management.
Actual Result:
Assets show the 192.168 address as the primary IP, causing them to appear under “undefined” locations and breaking reporting accuracy.
Impact:
• Incorrect asset classification
• Reports and dashboards unreliable
• Manual workarounds required to filter for 10.x addresses
Request:
Please provide a way to configure primary IP selection so that the IP used for server communication (corporate LAN) is always chosen, or allow administrators to define preferred subnets for primary IP assignment.

[FrankSc]

Dear, 

We have received a few similar requests in the past on this matter. We have this listed as a future product improvement.
At the moment, it has not been assigned to a short-term roadmap. But we hope to handle this in the future.

Now, we mainly use the IP address that initiated the scan, when scanned by IP. But indeed, having the visibility of the second NIC, makes sense.