IPv4 (RFC 791 / 950)6 min read

Worked Example: Laptop Cannot Ping the IED — a One-Way Subnet Mask Mismatch

The engineer's laptop and a protection IED have addresses in the same range, yet ping fails. Checking the addressing from both sides shows why, and which laptop address works.

Scenario

Laptop10.13.0.200, mask 255.255.255.0, no gateway
IED10.13.0.14, mask 255.255.255.128, gateway 10.13.0.1
ConnectionLaptop on a spare port of the station-bus switch, same VLAN
SymptomPing times out; the IED's web page does not open

The laptop was set up from an old drawing that showed the station bus as a /24. The IED configuration uses /25.

Step-by-step calculation

Step 1: The laptop's decision

The laptop applies its own mask (/24) to its own address and to the IED's address.

network = IP AND mask
10.13.0.200 AND 255.255.255.0 = 10.13.0.0; 10.13.0.14 AND 255.255.255.0 = 10.13.0.0
Same network → the laptop sends directly to the IED

Step 2: The IED's decision

The IED applies its own mask (/25). Its subnet 10.13.0.0/25 covers 10.13.0.0–10.13.0.127.

Step 3: What happens on the wire

The ping request reaches the IED. The reply is addressed to the router, not to the laptop. Unless the router sends it back onto the same LAN, it is lost — so ping fails although the cable, switch and VLAN are fine.

This is why the check must be done from both sides. Looking only at the laptop, everything seems correct.

Step 4: Choose a working laptop address

Put the laptop in the IED's subnet with the IED's mask. The assistant proposes an address near the top of the usable range (lastHost − 9), away from the IEDs at the bottom and the gateway.

usable range = network + 1 … broadcast − 1
10.13.0.0/25: 10.13.0.1 … 10.13.0.126; 10.13.0.126 − 9 = 10.13.0.117
Laptop: 10.13.0.117 / 255.255.255.128, no gateway needed

Check the IP address register first that 10.13.0.117 is not already used.

Step 5: Test the service

With the new address the assistant reports 'Can talk directly'. Next, test the protocol: IEC 61850 MMS on TCP 102. If ping works but the engineering tool cannot connect, check the Windows firewall and the IED's client-connection limit.

Result summary

CheckRequirementActualStatus
Laptop sees IED as local (/24)Both sides agreeLocal✓ PASS
IED sees laptop as local (/25)Both sides agreeVia gateway✗ FAIL
After change: 10.13.0.117/25Same subnet both waysDirect✓ PASS
The laptop's /24 mask makes the fault one-way. Setting the laptop to 10.13.0.117 / 255.255.255.128 (the IED's subnet and mask) restores direct communication.

Key insight: Each device judges 'local' with its own mask. Two devices only talk directly when both agree.

Try it with your own numbers

Every input in this example is editable in the live calculator — no signup needed.

Open SCADA Connectivity Assistant calculator →

Frequently asked questions

Would adding a gateway to the laptop fix it?

No. The laptop already sends directly; the problem is the IED's reply going to its gateway. Only matching the mask (or a router that sends the reply back) fixes it.

Why not just change the IED's mask to /24?

The /25 is part of the station-bus design; other devices and the gateway rely on it. Change the laptop, not the protection IED.

More in IEC 61850 & Substation Automation

← Back to all worked examples