This article explains how to resolve LsPush socket errors. Lansweeper includes several scanning methods to scan the assets in your network. You can scan the Linux, Unix, Mac and Windows computers, VMware servers and other devices in your network without installing any Lansweeper software on the machines you're scanning. However, you can optionally choose to perform your computer scans with a scanning agent instead. One of Lansweeper's scanning agents for Windows is called LsPush.
LsPush is a small executable that, when run on a Windows computer, scans the computer locally. LsPush scan results can be sent directly to your Lansweeper server for automatic processing or stored in a file, which can be imported into your Lansweeper installation later on. If you choose to send LsPush results directly from your Windows computers to your Lansweeper server for import, certain things like firewall configuration must be taken into account in order for the data transfer to be successful. If you attempt to send LsPush data directly to your Lansweeper server and the connection fails, you may encounter errors similar to the ones below. Specifically, connection errors like these will be displayed in a popup window when including the debug option /showresult in your LsPush command.
To resolve socket errors you may encounter when sending LsPush data directly to your Lansweeper server, do the following:
- If you have not already done so, update to the latest Lansweeper release by following the instructions in this knowledge base article. You can verify whether you are on the latest release by hitting the Check for Updates now button in the following section of the web console: Configuration\Your Lansweeper License
- Make sure you are using the latest LsPush executable, as LsPush is regularly updated. If you are using LsPush in a logon script, group policy or scheduled task, manually copy the up-to-date LsPush executable to any folder referenced by your script, policy or task. When you update your Lansweeper installation, the latest version of the LsPush executable is automatically added to the folder below on your Lansweeper server.Program Files (x86)\Lansweeper\Client
- Make sure you are pointing to the correct Lansweeper scanning server in your LsPush command. Your LsPush socket errors may simply be a result of pointing to a wrong server. Your LsPush command should include the up-to-date name or IP address of your Lansweeper scanning server.
- Start the Lansweeper Server service in Windows Services on your Lansweeper server, if not already started. The Lansweeper service is what processes LsPush data. If this service isn't started, no LsPush data can be imported. By default, the Lansweeper service is automatically started, but someone may have manually stopped it.
- Verify what you have configured as your listen port in the Service Options section of Configuration\Server Options in the Lansweeper web console, as this is the port your Lansweeper service uses to listen for LsPush data.Changing the listen port requires you to restart the Lansweeper Server service.
- If your listen port is anything other than the default port 9524, make sure your LsPush command includes the listen port. If your listen port is the default 9524, including it in your LsPush command is not necessary.
Sample command when sending data to scanning server LAN-001 over default listen port 9524:
lspush.exe LAN-001 /showresult
Sample command when sending data to scanning server LAN-001 over custom listen port 9500:
lspush.exe LAN-001 9500 /showresult
- Make sure inbound traffic over the listen port is allowed on your Lansweeper server. When you install Lansweeper, rules are automatically added to Windows Firewall on your Lansweeper server to allow inbound traffic over listen port 9524. If you use another listen port or firewall though, you'll need to manually configure your firewall to allow traffic over the appropriate port.
- Make sure outbound traffic to your Lansweeper server's listen port is allowed on the Windows computers you're scanning. By default, Windows Firewall does not block outbound connections. If you use a custom firewall or custom firewall configuration though, outbound traffic may in fact be blocked and you may need to reconfigure your firewall.