Overview
The most common Windows scanning errors in Lansweeper are typically caused by:
- Unstable or blocked network connections
- Firewall restrictions
- Incorrect or insufficient scanning credentials
Common errors include:
- RPC Server Unavailable
- Ping Failed
- WMI Access Denied
- Computer is offline or firewalled
Because Lansweeper retrieves most Windows asset data through WMI (Windows Management Instrumentation)—which uses dynamic ports—it is important to verify that your firewall is not blocking WMI traffic.
Troubleshooting Steps
To further diagnose and resolve these errors, review the following:
Credential and Permissions Checks
DCOM and WMI Configuration
- Run the following script on the client machine as Administrator:
http://www.lansweeper.com/files/lansweeper.vbs
- This script reconfigures DCOM and related settings used during the initial RPC connection and may resolve RPC-related errors.
Review Related Knowledgebase Articles
Consider Recent DCOM Security Changes
Escalation to Support
If all settings appear correct and the issue persists, you can open a support case:
https://www.lansweeper.com/contact/contact-support/
Please include the following to ensure efficient troubleshooting:
Required Information
- Screenshot of a testconnection.exe test to the same client machine:
- Run from the Lansweeper server
- Use the same credentials that Lansweeper uses for scanning
- Display the full output window
- The tool can be found in:
Program Files (x86)\Lansweeper\Actions
