Below is an overview of the ports used by a Lansweeper installation.
Lansweeper service and web console to SQL Server
Lansweeper service to Active Directory domain controllers
Port: 389/TCP (LDAP)
Lansweeper service to scanned Windows computers
Port: 135/TCP (DCOM to establish the initial WMI session with the computer)
Random ports (to send the WMI data)
By default, Windows sends WMI data over random ports, as explained in this Microsoft knowledge base article
. You'll need to either:
• Configure your firewalls in such a way that *all* WMI traffic (over random ports) is allowed. Windows Firewall includes a remote administration exception that you can enable to allow WMI traffic, as explained in this knowledge base article
. For third-party firewalls, you'll need to consult your firewall documentation.
• Configure a fixed WMI port
and allow traffic through that port. Setting a fixed port is supported by Windows Vista and more recent operating systems.
• If you are unable to allow WMI traffic through your firewalls, scan your computers with the LsPush scanning agent
instead, which does not require firewall reconfiguration.
Lansweeper service to scanned Linux, Unix and Mac computers
Port: 22/TCP (SSH) or a custom SSH port of your choice
Lansweeper service to scanned VMware servers
Port: 443/TCP (HTTPS)
Lansweeper service to scanned network devices
Port: 21 (FTP)
Port: 22 (SSH) or a custom SSH port of your choice
Port: 23 (Telnet)
Port: 25 (SMTP)
Port: 80 (HTTP)
Port: 135 (EPMAP)
Port: 139 (NetBIOS Session Service)
Port: 161 (SNMP)
Port: 443 (HTTPS)
Port: 445 (SMB)
Port: 5060 (SIP) or a custom SIP port of your choice
Port: 9100 (Jetdirect)
Scanned Windows computers to Lansweeper service, if LsClient or LsPush is used for scanning
Port: 9524/TCP or a custom port of your choice
This port must be open in the firewall of the Lansweeper scanning server, i.e. the server hosting the Lansweeper Server service.