Resolving CodeMeter License Container Connection Failures in SIMIT Virtual Machines

CodeMeter WebAdmin reports 'no CmContainer connected' in SIMIT virtual machines when network routing conflicts or dual-NIC IP collisions prevent the CodeMeter runtime service from binding to the license server. In multi-adapter VM environments combining static IP plant buses and DHCP management networks, IP overlap or improper adapter metrics route CodeMeter daemon broadcasts (port 22350) across the wrong subnet. Resolving IP address collisions and adding the license server's static IP to the CodeMeter Server Search List restores license container discovery.

CodeMeter Licensing Architecture in Multi-VM SIMIT Systems

Siemens SIMIT simulation software (V10, V11, and newer) utilizes Wibu-Systems CodeMeter technology for hardware dongles and software license containers (CmActLicense). In distributed automation simulation testbeds, engineers deploy multiple virtual machines (VMs) where one or more dedicated VMs function as CodeMeter Central License Servers, while client VMs consume runtime simulation licenses over the local network.

Communication between the SIMIT client executable and the CodeMeter runtime daemon (CodeMeter.exe) relies on TCP and UDP port 22350. By default, CodeMeter uses local broadcast discovery to detect active license servers on the local subnet. When a client VM fails to detect a valid container, SIMIT aborts with "no license dongle connected", and the CodeMeter WebAdmin console displays an inactive, grayed-out CmContainer icon.

Diagnosing Dual-NIC Routing Conflicts and IP Collisions

In virtualized simulation environments (e.g., VMware vSphere, Workstation, or Microsoft Hyper-V), VMs frequently feature dual network interface cards (NICs):
* Adapter 1 (Simulation / Plant Bus): Configured with fixed, static IP addresses for deterministic communication with simulated virtual controllers (S7-PLCSIM Advanced or SIMIT Virtual Controller).
* Adapter 2 (Corporate / Management Network): Configured with DHCP for host communication, remote desktop access, or internet connectivity.

The failure occurs under two primary conditions:
1. IP Range Overlap / Conflict: The DHCP server assigns an address on Adapter 2 that falls into the identical IP subnet configured statically on Adapter 1, creating an asymmetric routing loop in the Windows TCP/IP stack.
2. Incorrect Adapter Binding Priority: Windows sends CodeMeter UDP discovery broadcasts out of the DHCP interface rather than the static simulation network where the CodeMeter license server resides. As a result, even if the user manually triggers a search in WebAdmin and temporarily sees the license server, the background service cannot sustain persistent container keep-alive packets.

Step-by-Step Resolution Workflow

Follow these steps to eliminate network collisions and configure deterministic license server routing:

Resolve IP Address Collisions:
* Open Windows Command Prompt on each VM and run ipconfig /all.
* Verify that the static IP network (Adapter 1) and the DHCP network (Adapter 2) use distinct, non-overlapping subnets (e.g., 192.168.1.0/24 for simulation and 10.10.x.x for management).
* If a collision exists, adjust the static IP range or configure DHCP reservations on the host virtualization switch.
Configure CodeMeter Server Search List:
* Open a web browser on the client VM and navigate to http://localhost:22350 to open CodeMeter WebAdmin.
* Go to Configuration -> Advanced -> Server Search List.
* Click Add New Server.
* Enter the exact static IP address or fully qualified domain name (FQDN) of the VM hosting the SIMIT license container.
* Click Apply.
Configure CodeMeter Server Daemon:
* On the VM acting as the license server, open WebAdmin (http://localhost:22350).
* Navigate to Configuration -> Server -> Server Access.
* Enable the check box Run Network Server.
* Ensure that Windows Firewall permits inbound TCP and UDP traffic on port 22350.
Restart CodeMeter Runtime Services:
* On both server and client VMs, open Windows Services (services.msc).
* Restart the CodeMeter Runtime Server service.

Verification

In CodeMeter WebAdmin on the client VM, inspect the bottom-left server indicator. Verify that the remote server appears with a green status indicator.
Click Container in WebAdmin. Confirm that the SIMIT license container (e.g., SIMIT Simulation Platform V11) is visible and displays available license units.
Launch SIMIT V11 on the client VM. Confirm that SIMIT starts without prompting for a dongle or licensing container.

Limitations and Operational Precautions

CodeMeter versions between different SIMIT major releases must maintain driver compatibility. Ensure that all VMs run identical or backward-compatible CodeMeter runtime versions (e.g., CodeMeter 7.x or 8.x).
Do not expose port 22350 to public networks. Keep CodeMeter license broadcasting restricted to private host-only or internal virtual networks.
Virtual machine cloning must be performed with caution. Cloning a VM hosting a software-based CmActLicense will invalidate the container due to hardware binding mismatch.

Engineer FAQ

Why did CodeMeter search find the server in WebAdmin, but SIMIT still claimed 'no dongle'?
The WebAdmin user interface performs an active browser query, whereas the SIMIT application relies on the local Windows CodeMeter service daemon. If the daemon's Server Search List does not have the target IP saved, background license requests fail.
Can SIMIT V10 and SIMIT V11 share the same CodeMeter license server?
Yes, provided the license server holds valid multi-version licenses or separate containers for both versions, and the CodeMeter runtime version supports both SIMIT releases.
What firewall ports are required for CodeMeter license communication?
TCP port 22350 and UDP port 22350 must be open bidirectionally between the client VMs and the license server.

Technical References

Siemens SIMIT Simulation Platform Operating Manual (A5E50257016-AA).
Wibu-Systems CodeMeter Administrator Manual and Network Configuration Guide.
Siemens Industry Online Support Entry ID 109801081: SIMIT Licensing and Multi-Station Setups.

Related Tags

SIMIT, CodeMeter, Wibu-Systems, Licensing, Virtual Machines, VMware, Networking, Simulation

Resolving CodeMeter License Container Connection Failures in SIMIT Virtual Machines