Set a PLC Commissioning Laptop IP Without Losing Access

A technician connects a laptop to an unfamiliar controller, but the programming software cannot discover it. Before changing the PLC, inspect the laptop's network configuration. A mismatched subnet, duplicate address, or active wireless route can explain the failure. This guide focuses on a temporary, controlled laptop address for commissioning. It does not assume every PLC ships with the same default IP.

Capture the starting configuration

Record the Ethernet adapter's current IPv4 address, subnet mask, gateway, DNS settings, and DHCP status. Note any VPN, virtual adapters, and Wi-Fi connection. Save a screenshot or change record so the original configuration can be restored. Coordinate with the plant network owner before attaching to a production segment. An unapproved duplicate address can interrupt an existing device.

Use the operating system's adapter settings to inspect or change the address. Microsoft's network adapter guidance explains the distinction between automatic DHCP assignment and a manually specified address. Its procedure targets Windows Server; menu labels on a particular laptop may differ.

Identify the controller address first

Check the model-specific OEM manual, the panel drawing, or the project's approved network plan. If the controller was previously commissioned, its factory default is not evidence of its current address. A label may also be outdated. Vendor discovery tools can help, but discovery behavior depends on the protocol and network topology.

Where permitted, inspect the attached segment with a managed switch or packet capture. Wireshark's ARP explanation describes how Ethernet hosts map IPv4 addresses to MAC addresses. ARP traffic can provide clues, but silence does not prove an address is unused. A device may simply not have transmitted while you were listening.

Choose a temporary, unique laptop address

For a direct test, assign the laptop an unused IPv4 address within the controller's intended subnet. Keep the subnet mask consistent with the approved plan. For example, a controller at 192.168.10.20/24 and a laptop at 192.168.10.30/24 can communicate directly, provided neither address conflicts. These values are examples, not defaults for any manufacturer.

A default gateway is usually unnecessary for a direct, same-subnet link. Do not copy a gateway from another plant network without approval. If a routed connection is required, ask the network owner for the proper gateway and firewall path. Avoid disabling endpoint protection merely to make a programming session work.

Before applying the address, check the network inventory and perform an approved conflict check. Then change only the intended Ethernet adapter. If the laptop has multiple active interfaces, verify which route the operating system selects. A successful Wi-Fi internet connection says nothing about the wired PLC path.

Test in layers

1. Confirm link LEDs and the switch port or direct cable connection.
2. Read the laptop's effective address and mask after saving the change.
3. Check the local routing table and ARP neighbor entries.
4. Use an approved ping test if the controller permits ICMP.
5. Try the OEM engineering software's discovery or online connection.

Ping failure alone does not establish a bad address; some devices block ICMP. Conversely, ping success does not prove the engineering protocol is available. Check the controller's port, project path, firmware compatibility, and access policy before changing any PLC configuration.

Leave the network in a known state

After commissioning, disconnect from the machine, restore the laptop's recorded DHCP or static settings, and verify ordinary connectivity. Record the final controller address in the approved documentation. If a setting must change on the PLC, use the site's change-control process and confirm the impact on HMI, I/O, and peer connections.

For segment architecture and repeatable troubleshooting evidence, see our industrial network design guide. The laptop procedure here answers a narrower question: how to reach a controller temporarily without leaving an unintended address behind.