First check

  # 1. What is your adapter's address?
ifconfig en0        # macOS
ipconfig            # Windows

# 2. Can you reach the sensor at its known address?
ping <sensor-ip>
  

If ping fails, the rest of the software configuration does not matter — fix the network first.

Cause ranking

#CauseCheck
1Host adapter on a different subnetCompare the first three octets with the sensor’s address
2Adapter set to DHCP and pulled an address from a routerLook for a 192.168.x or 10.x address that is not the sensor’s subnet
3Wrong sensor default address for the modelConfirm on the series page
4Sensor not poweredLink LED off — see Topology
5Software scanning the wrong adapterWi-Fi and VPN adapters can take priority

Fix

Set the adapter manually to a free address in the sensor’s subnet, same mask, no gateway. Step-by-step for both platforms in Network & host setup.

Then rescan. The device should appear within a few seconds.

If it still does not appear

TestInterpretation
Ping the sensor from a different machineIf it answers, the sensor is fine and the problem is this host
Try option C wiring (direct 12 V)Rules out PoE negotiation problems
Check the switch port’s PoE budgetAn over-budget port may never power the device

Next

Once found: First point cloud.