on 08-06-2024 10:59 AM - edited 2 weeks ago
This page covers some frequently asked questions regarding Lansweeper's Network Discovery.
Lansweeper's Network Discovery enables you to discover all IT and OT assets within your network. If you'd like to learn more about Network Discovery, head on over to Install Network Discovery.
Yes, these can be ran on the same machine.
We've observed that this process may run slower on certain machines. The slowdown could be due to factors such as a slow hard disk, low memory, or limited CPU resources. We are currently investigating the root cause of this issue.
To resolve this message during the installation:
HKEY_LOCAL_MACHINE\SYSTEM\CurrentControlSet\Control
or copy-paste the location in the navigation bar.When the installer terminates with an exit code during the pre-installation phase, no actions have been executed with no files or changes left behind.
In the event the installer terminates during the installation, a rollback will occur and no files or changes will be left behind.
The ranges are the following:
Exit Code | Description | Position |
---|---|---|
0 | The installer finished with success. | |
20-39 | Issues regarding OS, installer, or current installation. | Pre-installation |
20 | Another installation is already in progress. Please finish that installation before starting a new one. | |
21 | This installer is being run on an unsupported operating system. Please update your OS if possible. | |
22 | The existing installation is newer than the version you want to install. Installer will be closed. | |
40-59 | Issues regarding user input. | Pre-installation |
40 | You must accept the terms of use before continuing with the installation. Please use the accepteula parameter for this. | |
41 | A valid linking code to your Lansweeper Site is required to continue. Please use the cloudtoken parameter for this. | |
42 | A valid proxy configuration is required to continue with the installation. Please use both the proxyserver and proxyport parameters (or none). | |
43 | A valid proxy port is required to continue with the installation. Please use the proxyport parameter correctly. | |
44 | No module was selected to be installed. Installer will be closed. | |
60-79 | Issues during the installation (installation will be rolled back). | Installation |
60 | PowerShell script execution is not enabled on your computer. Ensure your computer is configured to allow PowerShell script execution. | |
61 | A link to your Lansweeper Site could not be made. (IT Agent only) |
|
62 | A required component service could not be started. | |
80-99 | Warnings during installation (installation will be kept). | Installation |
80 | The installation succeeded but a link to your Lansweeper Site could not be made. (Network Discovery only) |
/tmp/Lansweeper-Network-Discovery_exitcode.log
. We’re remapping all data to a universal data model. As we’re doing this in phases, you’ll only see certain data sections available on the asset page.
Currently, these sections are available:
This list is continuously being extended.
Auto update is enabled by default in an 8 hour time window varying between 08:00 am and 06:00 pm. Though not recommended, you can still disable the auto-update behavior after installation by running the following command on the machine running Network Discovery:
sc config "Lansweeper Network Discovery Update service" start= disabled sc stop "Lansweeper Network Discovery Update service"
You can also disable auto-updates for specific groups in your Lansweeper Site by following these steps:
This will prevent the group's Discovery Systems from applying updates automatically, although currently, updates will still be downloaded.
To block downloads entirely in the meantime, you can block outgoing connections by executing the following steps:
nslookup download.lansweeper.com
This should return:
Block the IP addresses by executing the following firewall rules:
netsh advfirewall firewall add rule name="Block auto-update Lansweeper" dir=out action=block remoteip=18.239.208.15 enable=yes
netsh advfirewall firewall add rule name="Block auto-update Lansweeper" dir=out action=block remoteip=18.239.208.60 enable=yes
netsh advfirewall firewall add rule name="Block auto-update Lansweeper" dir=out action=block remoteip=18.239.208.108 enable=yes
netsh advfirewall firewall add rule name="Block auto-update Lansweeper" dir=out action=block remoteip=18.239.208.83 enable=yes
This will still allow access to discovery-gateway.lansweeper.com, which is needed for data synchronization.
Please note that your Lansweeper Site requires a minimum version of Network Discovery to maintain synchronization. To that end, we recommend to re-enabling the auto-update feature when possible.
Yes, you can:
After unlinking, Network Discovery will continue to scan, and will keep trying to send its data to your Lansweeper Site. To avoid this from happening, we recommend you uninstall Network Discovery on the machine it was installed on. We’re looking to automate this process so you don’t have to manually uninstall Network Discovery installations you no longer want to track.
Yes, you can:
C:\Program Files\Lansweeper Network Discovery\hub
).Some ports may not be open, or specific access might be missing between your sensor and the asset.
To verify if a port is not open, or if access is missing:
The result will appear in Discovery results where you can for instance compare the open ports to this list, to see if any required ports are missing.
If you are using Lansweeper IT Agent Discovery, Network Discovery, or Cloud Discovery in your Lansweeper Site, you may encounter warning messages when you approach or exceed your license limit.
While assets discovered through these Discovery systems are counted toward your licensed asset total, exceeding the limit will not immediately restrict access to insights—this will only happen once our Lansweeper Site subscription process is finalized.
Yes, you can but be aware duplicates are still likely to occur.
Please refer to the next section for guidance on managing duplicates when using both Lansweeper On-premises and Lansweeper Discovery within the same site.
In this hybrid scenario where you use Lansweeper IT Agent Discovery, Network Discovery, or Cloud Discovery together with Lansweeper On-premises in a single Lansweeper Site, we recommend either of the following options:
If the above is not an option:
Both Lansweeper On-Premises and Lansweeper Network Discovery can work alongside one another; you don’t convert one into the other, as you can install and uninstall both independently.
Lansweeper Network Discovery automatically attempts to discover as many assets as possible. It does this using Network Visibility, a passive detection method that captures IP and MAC addresses from broadcasted network packets across all network interfaces of linked sensors. Additionally, it performs active discovery actions within the IP range and Active Directory domain where these sensors are located.
To view assets detected by Network Visibility, navigate to Reports > All assets detected by Network Visibility (example: Lansweeper report).
If needed, you can refine or disable discovery actions by going to Scanning > Discovery actions, where you can add filters or remove actions entirely.
For full control, you can also entirely disable passive detection. To do this, go to Scanning > Discovery groups and select a discovery group. In there, disable Network Visibility.
This will stop sensors from inspecting network packets, and restrict asset discovery to the targets defined in Scanning > Discovery actions.
services.msc
on Windows or Activity Monitor app on macOS or sudo ps -aux | less
on LinuxAs the data is already in LS Site, it stays there. Just make sure to unlink LS Classic or that the cleanup rules are no longer removing assets automatically after x time. As long as the sync server remains connected, the cleanup rules remain active. Network discovery acts as a new installation in LS Site. Each hub is considered an installation. Don't think of it as a one-off replacement; think of it as a secondary installation.
This means the assets from an LS Classic/On-Prem install already syncing to Cloud will remain in Cloud even if you add a Network Discovery Hub in your LS Site. If you then unlink/uninstall LS Classic/On-Prem and choose to keep the data in LS Site, those manually created/updated assets will have been synced to LS Site earlier and will remain there. Adding a network discovery will only add new/update existing assets.
There's no load balancing in a discovery action yet. So right now, if you assign lots of targets in an action to multiple sensors, they will all be contacted by the first listed sensor in the action. Once we’ve added load balancing capabilities (foreseen in 2025), you will be able to indicate which sensor takes which part of the entire target list.
Depending on the type of asset, access, and provided credentials, it takes several minutes to scan an asset with network discovery.
Yes, as long as the Linux operating system (and version) is mentioned in the supported operating system list, found here.
Yes, only by the specific Hub, but you can easily "sync" credentials from one hub to another by going to Lansweeper Site > Scanning > Discovery credentials. There, you can easily add extra hubs that need to send the specific credential to their sensors. By adding extra hubs, the original hub will send the credential to the other hub, over LS Site, with full encryption both in transit and at rest.
Currently, Network Discovery on Linux can’t get the details yet from a Windows device due to access restrictions. If you do enable Windows Remote Management between the Windows asset and the Linux sensor, you might already get more information. See How to configure WINRM for HTTPS - Windows Client | Microsoft Learn on how to enable it on your Windows asset.
Lansweeper sends discovery messages with a maximum packet size of 8191 bytes for any non-PowerShell-based request, and 32766 bytes for PowerShell-based requests.
The maximum response message size is up to 4 MB for Windows Server during an initial scan. However, typical response sizes are much smaller, especially during rescans, as not every item on a Windows system is rescanned.
Yes, they update automatically using your Linux package manager, such as apt or yum. For more information on automating updates and upgrades, you can refer to resources such as apt - Automate Updates and Upgrade.
Experience Lansweeper with your own data. Sign up now for a 14-day free trial.
Try NowExperience Lansweeper with your own data. Sign up now for a 14-day free trial.
Try Now