Low coverage in a range usually comes down to one of four things: nothing's actively scanning it, credentials aren't configured, IT agents aren't installed, or required ports are blocked.
These recommendations aren't mutually exclusive: most environments benefit from combining them. Start with the ones that fit your setup.
Create an agentless action
If a range shows a high unrecognized asset count and only the traffic sensor is listed in the Discovery system column, no active scanner is pointed at it yet. The traffic sensor detects that devices exist; an IT sensor identifies what they are.
Create a Network Discovery action that covers the range, or extend an existing one to include it.
For more information, see Create a Network Discovery action.
Add credentials
If a discovery action is already scanning the range but assets remain unrecognized, missing credentials are the likely cause. Without them, Lansweeper can only collect what's visible from the network, not the deeper device data needed for full recognition.
Add credentials for the protocols your assets use (WMI, SSH, SNMP, and others), then map them to the relevant discovery action.
For more information, see Create discovery credentials.
Deploy IT agents
For Windows, macOS, and Linux devices, IT agents provide deep recognition without relying on network scanning. If most of the unrecognized assets in a range are these device types, agents are often the most effective fix, and they work even when ports are restricted.
For more information, see Install IT Agent discovery.
Check required ports
If a discovery action and credentials are configured but coverage is still low, blocked ports are likely the cause. Lansweeper requires specific ports to be open on the target range. This is managed in your firewall settings, outside Lansweeper.
For more information, see View required ports.