I'm not sure that's the case. Other servers are working as expected (2016/2019)
Disabled the Windows firewalls on both the client and server systems.
No network firewall blocking is being reported.
The Lansweeper server is using the default port, 9524.
I wonder if there are OS security settings or TLS settings on 2012 and older systems that might be causing issues communicating with the LanSweeper server (2016)
Is there an endpoint I can hit on 9524 with a browser to confirm connectivity? Something like: https://server:9524/lsagent/status
Here is a log from a 2016 server in the same network as the 2012 server, working succesfully.
2020-09-18 00:20:51,803 [7] INFO === Service started ===
2020-09-18 00:20:52,366 [8] DEBUG Detected OS: Windows
2020-09-18 00:20:52,367 [8] DEBUG Client Version: 7.2.110.16
2020-09-18 00:20:52,367 [8] DEBUG Cleaning up older versions...
2020-09-18 00:20:52,368 [8] DEBUG Checking OS
2020-09-18 00:20:52,368 [8] DEBUG 64bit detected: checking registry (64bit)
2020-09-18 00:20:52,369 [8] DEBUG Reading ini file...
2020-09-18 00:20:52,439 [8] INFO CreateReachableEndPoint for xxxxxxxx-xxxx-xxxx-xxxx-xxxxxxxxxxxx
2020-09-18 00:20:52,559 [8] DEBUG Creating InternalCommunicationSender to URL https://internal-server.tld:9524/lsagent
2020-09-18 00:20:52,588 [8] DEBUG Asset is enabled.
2020-09-18 00:20:52,589 [8] DEBUG Retrieving configuration...
2020-09-18 00:20:52,644 [8] DEBUG New agent key: xxxxxxxx-xxxx-xxxx-xxxx-xxxxxxxxxxxx
2020-09-18 00:20:52,644 [8] DEBUG Checking version.
2020-09-18 00:20:52,645 [8] DEBUG Waiting for schedule...
2020-09-18 00:20:52,645 [8] DEBUG Schedule triggered
2020-09-18 00:20:52,645 [8] DEBUG Starting scan
2020-09-18 00:20:52,646 [8] DEBUG Detected OS: Windows
2020-09-18 00:20:53,164 [8] DEBUG Scanning computer...
2020-09-18 00:21:09,249 [8] DEBUG Computerscan completed.
2020-09-18 00:21:09,250 [8] DEBUG Compressing scanfile.
2020-09-18 00:21:09,305 [8] DEBUG Scan has been sent.