Lansweeper IP address server change

[IT_DE]

Hi, 

Would someone point to the correct documentation of what settings should be changed when changing the IP address of the VM server where Lansweeper runs(i.e. Acction Path, Security Options, etc.)

Thanks.

[DavidPK]

There isn’t a single “change IP” wizard or dedicated documentation page specific to updating the Lansweeper server’s IP address, because Lansweeper itself doesn’t store or tie core settings directly to that address. The web console and scanning services rely on their IIS bindings and database connection settings, not hardcoded IPs.

Here’s what you should verify after changing the IP address of the virtual machine hosting Lansweeper:

1. IIS or IIS Express binding –
   If you use IIS (the web‑server software used by Lansweeper on‑prem), open IIS Manager, locate the Lansweeper site, and under Bindings ensure that the new IP address is selected (or set to “All Unassigned”). For IIS Express, check the applicationhost.config file for the same.

2. Firewall and port configuration –
   Confirm that inbound TCP 80/443 (for the web console) and any other custom ports remain allowed for the new IP address. IIS uses port 80 for HTTP and 443 for HTTPS by default.

3. Database connection –
   The Lansweeper database connection string in the configuration files normally uses a hostname or instance name, not the server IP. No change is required as long as the SQL Server instance is reachable.

4. Scanning targets and credentials –
   Review scanning targets if they pointed to the old IP of the scan server. Update any server references in Scanning > Scanning Targets that used the old address.

5. Remote connections or integrations –
   If remote scan servers, LsPush, or external tools referenced the old IP, update their configuration to the new one.