→ Celebrate SysAdmin Day 2024 with Lansweeper Enter our Giveaway here

Showing results for 
Show  only  | Search instead for 
Did you mean: 
Engaged Sweeper II

I upgraded to the latest version yesterday, asset radar passed the compatibility checks, I've selected all the network interfaces and it's set to logging only. I've left it a day, on a subnet that should have plenty going on, and it's detected absolutely nothing.

Please could you let me know if there is something else required to get it working, either within Lansweeper or on the server (i.e. firewalls, security software etc.) ?

Engaged Sweeper III
Logic tells me that Lansweeper isn't performing any kind of network miracle. So, the "radar" is just for packets visible to your interface, a lot of which is just going to be associated with your local LAN segment of the Lansweeper host.

I think the missing piece of Radar are deployable "radars" for each "network" you have so automatic collection can be done. Lansweeper would then communicate with the remote radars on each network to retrieve discovered information. Sounds like a future feature that is needed.

The alternative (bad) would be to put the Lansweeper on a span (where that works) to see other networks. Why is this bad? Lots of packets. Possibly too many packets, things will be missed. However, the passive nature of the radar probably means that over time, it will still discover "all things" possible.

Regardless, the latter should probably be spoken about in the documentation for sure... but probably all of this needs to be discussed (and implemented as in the case of the remote radars).