Make PCS 7 OS Servers Visible on the Terminal-Bus LAN

If the ES can browse OS server/client shares only over an administration LAN and cannot download an OS project over the terminal bus, configure SIMATIC Shell and the PCS 7 PC station to use the terminal-bus adapter, then verify that each station name resolves to its terminal-bus address. The source's successful fix added host-file mappings and prioritized NIC metrics, and it configured the target OS from the ES. Use these as topology-specific actions, with the network team confirming mappings and routes.

Role of SIMATIC Shell and the Terminal Bus

SIMATIC Shell participates in PCS 7 station discovery and communication settings. In a multihomed station, select the network adapter assigned to the terminal bus. Siemens' PC Configuration documentation also uses a selected network connection when configuring or downloading PC stations.

Configure the Target OS from the ES

The source response instructs the engineer to configure the target OS station from SIMATIC Manager on the ES. Confirm the OS server and OS client are correctly represented as PC stations in the project and can be discovered through the selected terminal-bus network before attempting the transfer.

Resolve Discovery and File Access

In SIMATIC Shell settings on the ES, select the terminal-bus NIC and initialize network communication.
Check that OS server and client names resolve to their terminal-bus IP addresses.
Confirm the intended shared project folder is accessible over the terminal bus and that access rights are correct.
If multicast must cross a router that does not pass it, configure the documented multicast proxy on a reachable station in the other subnet.
Configure the target OS from SIMATIC Manager and select the terminal-bus connection for target access.
Test station visibility and project transfer before changing production settings.

Use Hosts and Interface Metrics Carefully

The user reports resolving this network case by adding host/IP entries in C:\Windows\System32\drivers\etc\hosts and setting interface metrics to prefer the terminal-bus NIC. These changes can affect other station communication, so ensure the mapping is complete and the route priority matches the approved architecture. Do not copy the reported numeric metric values to a different network without checking Windows and PCS 7 requirements.

Verification

Verify that both OS server and client appear in SIMATIC Shell over the terminal bus, that the target can be selected and configured from the ES, and that the OS project transfer succeeds. Check plant-bus and administration traffic separately after the change.

Limitations and Operational Precautions

The exact Windows configuration, routing, DNS, project share, and network security design are not supplied. The source reports a working host-file/metric change but provides no independent topology validation. Keep plant bus and terminal bus separated and follow the site's network change process.

Engineer FAQ

Select the terminal-bus adapter in SIMATIC Shell, ensure hostnames resolve through that interface, and configure the target OS from SIMATIC Manager. The user's hosts-file and metric change is one topology-specific resolution.

Technical References

Siemens, PCS 7 – PC Configuration (V9.1), terminal-bus and SIMATIC Shell settings: https://support.industry.siemens.com/cs/attachments/109794377/ps7pck_b_en-US.pdf
Siemens, PCS 7 Virtualization, §6.3.5 “Communication over multiple subnets,” multicast proxy guidance: https://support.industry.siemens.com/cs/attachments/109737277/Manual_PCS7V81SP1_Virtualization_en.pdf
Siemens, PCS 7 Software Update V9.1, PC station configuration and download: https://support.industry.siemens.com/cs/attachments/109794380/ps7swm_b_en-US.pdf