Resolving TIA Portal V11 Ethernet Interface Not Detected in VM

Problem Overview

A field engineer has archived TIA Portal V11 SP2 Update 4 project files belonging to an S7-300/S7-400 PLC. To operate the legacy software, the engineer deploys a Windows 7 32-bit virtual machine because the original V11 build does not install on modern Windows 10/11 hosts reliably. The PLC responds to ICMP echo requests (ping) from the host operating system, and the host's physical network interface shows link and activity LEDs when traffic flows to the controller.

Despite the healthy Layer 3 path, the TIA Portal "Online > Accessible Nodes" or "PG/PC Interface" dialog only enumerates two transports: Teleservice (S7Online over the MPI/Profibus adapter) and S7USB (the USB-to-S7 cable). The S7ONLINE (STEP7) -> TCP/IP -> <intel network connection> entry that the engineer selected inside the Set PG/PC Interface control panel applet is not surfaced as a usable target inside the V11 Portal project tree.

Symptoms in the V11 environment:

• The Set PG/PC Interface applet shows the wired Intel NIC bound to S7ONLINE (STEP7) -> TCP/IP, but V11 Project Navigator "Accessible Backstations" returns empty.
• Diagnostic trace in Step7\S7wsserc does not show TCP socket attempts on port 102 (ISO-on-TCP / RFC1006) to the PLC IP.
• Reinstalling V11 SP2 Update 4 inside the VM does not restore the adapter. Bridged networking is configured, but the VM is sharing the host's single physical NIC.
• V17 installed on the host operating system can discover the PLC online but fails to upload the project (a known V11-V13 upload limitation discussed later in this article).

Root Cause Analysis

Three interacting failure modes produce this exact symptom set. Each must be ruled out independently.

1. Shared/Bridged NIC Capture in Virtualized Environment

When TIA Portal runs inside a virtual machine and the VM is configured to share (NAT mode) or bridge the host's single physical Ethernet adapter, the guest operating system does receive a virtual NIC. However, V11 SP2 predates the era of robust virtual NIC emulation. The Windows 7 guest's tcpip.sys stack binds the Intel NIC driver that V11's Set PG/PC Interface applet enumerates, but V11's S7Online helper service performs its adapter discovery through a Win32 GUID enumeration that frequently fails to match the bridged virtual NIC's device instance path to the one V11 expects from a physical adapter.

The result is that the binding appears correct in the control panel, but the S7DOS helper (the S7 communication service that brokers access to S7ONLINE) refuses to bind a socket to the virtual adapter, and Portal falls back to enumerating only adapters with known device-class GUIDs for Teleservice and S7USB transports.

2. Missing ISO-on-TCP / RFC1006 Bindings in V11 SP2 on Windows 7 32-bit

V11 SP2 Update 4 was engineered primarily for Windows XP SP3 and Windows 7 64-bit installations. On Windows 7 32-bit, the install of the Siemens S7DOS helper occasionally fails to register the TCPIP.S7ONLINE protocol stack binding if the host already has a stale Set PG/PC Interface registry hive from a previous TIA Portal V10.5 or V13 install. The relevant registry key is:

If this key is missing for the bridged NIC, the adapter will not appear as a selectable S7ONLINE target, even though the standard Windows network control panel shows the NIC is enabled and has an IP address.

3. CPU Architecture Mismatch with V11 SP2 Binaries

V11 SP2 Update 4 ships both 32-bit and 64-bit binaries, but several COM components (notably s7wb53ax.dll and s7otbxdx.dll) are only x64-aware. On a Windows 7 32-bit guest, these components fall back to WoW emulation, but the S7 helper services that scan for ISO-on-TCP bindings are not fully functional under WoW. This is why the same V11 SP2 UPD4 install on a Windows 10 32-bit host showed the wired adapter correctly: Windows 10 ships updated WoW thunking that bridges the gap.

4. Firmware/Version Compatibility Boundary

Siemens maintains a hard compatibility matrix between TIA Portal versions and the firmware of the target CPU. The Pro-face/Siemens integration guide for TIA Portal Ethernet drivers (sie_tiae.pdf) states that TIA Portal versions STEP 7 V11 through V20 can connect to most S7-300/S7-400 CPUs whose firmware is in the published support list, but V11 SP2 does not support newer S7-1200 V4.x firmware (introduced with V13 SP1) and cannot upload from S7-1500/ET200SP CPUs at all. If the project targets any controller with firmware newer than the V11 cutoff, the discovery succeeds at the link layer (hence the ping reply) but V11 cannot form an S7 communication relationship, and the interface is silently suppressed from the accessible nodes view.

Solution: Dedicated Network Adapter for the Virtual Machine

The single most reliable fix is to remove all sharing/bridging of the host's primary NIC and present TIA Portal V11 with a physical, dedicated network adapter that is captured 100% by the VM during operation. This is the approach that experienced automation engineers use when reverse-commissioning or uploading legacy projects.

Prerequisites

Step-by-Step Procedure

1. Insert the USB-Ethernet adapter into a USB 2.0 port (USB 3.0 ports occasionally cause enumeration issues with V11's older USB stack). Connect the adapter directly to the PLC's PROFINET port, or to the managed switch port that the PLC is connected to.
2. Verify the host sees the adapter in Device Manager. Confirm the host's primary NIC remains bound to the corporate network; the USB adapter is a second network interface.
3. Configure the VM to capture the USB adapter:
   • VMware: VM > Removable Devices > [Adapter Name] > Connect (Disconnect from Host). The adapter disappears from the host's network connections list once captured.
   • VirtualBox: Devices > USB > [Adapter Name]. Enable USB 2.0 (EHCI) controller in the VM settings if not already.
4. Inside the guest OS, allow Windows 7 to install the Realtek/ASIX driver automatically (or use the manufacturer driver disc). Confirm a new "Local Area Connection #2" appears with a valid link LED.
5. Assign a static IP in the same subnet as the PLC, e.g. PLC = 192.168.0.1, adapter = 192.168.0.10/24. Disable any firewall on this adapter within the guest.
6. Verify connectivity by opening a command prompt and executing ping 192.168.0.1 -t. You should see replies within 1 ms if the link is direct, or <10 ms through a switch.
7. Open TIA Portal V11 SP2. Navigate to Options > Set PG/PC Interface. You should now see S7ONLINE (STEP7) -> TCP/IP -> <USB Ethernet Adapter> as a selectable entry. Select it and click OK.
8. Open the project in the Project Navigator, right-click the PLC, and choose Online & Diagnostics > Accessible Nodes. The PLC's PROFINET/IP address and rack/slot should appear.
9. Initiate the upload with Online > Upload from device (software). Note the upload caveats discussed in the next section.

Repair Procedure if Adapter Still Not Detected

If the captured USB-Ethernet adapter still does not appear in the Set PG/PC Interface dialog, perform the following in order:

1. Open Control Panel > Programs and Features and run Repair on the "Siemens TIA Portal V11 SP2" entry. This re-registers the S7DOS helper and re-writes the registry bindings.
2. Reboot the VM. V11's S7DOS service is started late in the boot sequence; a reboot is required for registry-only changes to take effect.
3. If still missing, uninstall TIA Portal V11 SP2 completely, delete the registry key HKEY_LOCAL_MACHINE\SOFTWARE\Siemens\Automation, and reinstall from a known-good DVD image. Reinstall after the USB adapter is captured and visible in the guest.
4. As a last resort, run the V11 install with the USB adapter not captured (released to host), let the install complete, then re-capture the adapter to the VM. Some builds of V11 SP2 only register adapter GUIDs that exist at install time.

Verification Steps

Confirm the configuration is correct using the following diagnostic checks.

Layer 3 Verification

Expect 0% loss, round-trip < 10 ms through a switch. If loss exceeds 2%, suspect a duplex mismatch; force the guest USB adapter to 100 Mbps Full Duplex in the adapter's Advanced properties (Realtek adapters default to auto-negotiate, which can fail with older managed switches).

Layer 4 Verification (ISO-on-TCP Port 102)

This PowerShell command (available on Windows 7 with the appropriate management framework) confirms that TCP port 102 is open on the PLC. A "TcpTestSucceeded : True" response indicates the S7 communication channel is reachable. If the port is filtered, check for any VLAN ACLs and confirm the PLC's PROFINET interface has ISO-on-TCP enabled in STEP 7 hardware configuration (it is by default for S7-300/400 CPUs).

S7DOS Helper Verification

The service "S7DOS" (or "S7 Online DOS Helper" on older localization) must be in the RUNNING state. If it is stopped, start it manually with sc start S7DOS and set its startup type to Automatic (Delayed Start).

TIA Portal Online Test

Open the V11 project, right-click the PLC device, and choose Online > Online and Diagnostics. If the connection succeeds, the project tree populates with online values within 5-10 seconds, and the lower status bar displays a green "Online" indicator with the PLC's IP address and rack/slot.

Upload Limitations of V11 and Why V17 Cannot Recover the Project

Even with the Ethernet interface fully functional, a V11 SP2 upload is an inherently lossy operation. The following limitations are documented behavior, not bugs:

If the original project was created in V13 or later, V11 cannot upload it at all - the format is forward-compatible but not backward-compatible. The engineer's V17 host can see the PLC online but is unable to perform an upload because the project format on the PLC was written by a tool newer than V17 knows how to reverse-engineer.

Troubleshooting Matrix

Best Practices for Legacy TIA Portal Reverse-Commissioning

• Document the CPU firmware version before any online operation. Read it with Online & Diagnostics > Diagnostics > Memory > Module Information. Compare against the V11 SP2 compatibility list at Siemens Industry Online Support.
• Use a dedicated industrial Ethernet NIC for the VM, not the engineer's Wi-Fi or docking station adapter. Industrial environments have strict isolation requirements, and a dedicated NIC prevents accidental broadcast storms from reaching the corporate network.
• Take a full PLC backup with Online > Backup from device (when supported) before any project upload attempt. The backup is a binary snapshot of the PLC's memory card contents and is far more complete than any upload-derived project.
• Verify the S7DOS service is healthy with sc query S7DOS at the start of every reverse-commissioning session. The service can become unresponsive after a Windows 7 guest sleeps or hibernates.

Safety and Operational Constraints

FAQ