No socket connection to license server manager when upgrading client dll to v18.104.22.168
When upgrading the client dll from:
- v22.214.171.124 build 242433 (ipv6) i86_n3 (lmgr.lib)
- v126.96.36.199 build 268393 (ipv6) i86_n3 (lmgr.lib)
Some of our customers get the error "No socket connection to license server manager" when connecting to a working license server.
When switching the dll back to the old version, the license server can be connected to immediately (no restart, no port changes, etc.)
The license server is using lmadmin-x64_n6-11_17_1_0.exe, with our dhsdelft daemon version v188.8.131.52 build 264148 (ipv6) x64_n6 (lmgr.lib). This setup works when we use the old dll, but gets us the error from the subject when we also update the dll on the client computer.
The license file they use to connect to the server looks like this:
SERVER servername 0000000000 TCP:27010
We are unable to reproduce the issue on our side when using the same operating systems for client and server. When we test, the old and new dll work fine:
- Client: Windows 10 20H2
- Server: Windows Server 2016
We double checked the port status on the client despite the old version working without issue, and the ports are open for access by the client (lmadmin port and vendor daemon port).
The license server shows no entries in the vendor daemon log when the client receives this error.
What could cause this error?