IMD SolutionComputing LibraryShop main store

Troubleshooting

Remote PLC access stops after a service plan change

Remote access and virtualization Published 8 min read

Short answer

When remote PLC access dies after a service plan change, the cloud entitlement layer failed, not the gateway, the LAN or the PLC. Test the four layers in order — gateway power and LAN, gateway configuration, service entitlement, user access — and repair only the layer that fails; no reset, cable change or PLC edit restores a removed subscription.

On this page
  1. Why did remote PLC access stop after the service plan changed?
  2. Which of the four layers is actually broken?
  3. What do I test on the gateway before blaming the subscription?
  4. Can a factory reset or PLC change bring the remote service back?
  5. How do I confirm what the new plan still includes?
  6. How do I restore access without weakening the controls?
  7. When is the retired gateway worth keeping?
  8. How do I decommission it without leaving a hole in the network?
  9. Questions asked

Remote access that dies the day a service plan changes is an entitlement failure, and the rest of the path is probably still healthy. The gateway still powers up, the site switch still passes traffic and the PLC still answers on its LAN; what went away is the cloud service that authenticates the user and brokers the session. That distinction decides the whole repair. Test the four layers in a fixed order, find the one layer that fails, and fix only that layer. Treat any urge to factory-reset the gateway, rewire the cabinet or edit the PLC program as a wrong turn until the entitlement question has a written answer from the vendor.

Why did remote PLC access stop after the service plan changed? #

A service plan change removes the cloud entitlement layer and nothing else, so the gateway, the site LAN and the PLC usually keep working and only the brokered, authorized remote session disappears.

A remote access gateway and the service behind it are separate parts of one path. The on-site box terminates the serial or Ethernet side and tunnels the traffic out; the vendor's cloud service authenticates the engineer, matches the session to the gateway's serial and enforces what the current plan allows. A plan change acts only on that second part. The reported symptom — a device that powers up and serves its LAN while remote sessions are refused — is evidence about the entitlement layer alone, and it says nothing about power, configuration or user access. That is why the same failure keeps getting misdiagnosed as dead hardware: healthy LEDs and a reachable PLC are real observations, but they sit in layers the plan change never touched.

Which of the four layers is actually broken? #

Test the path as four layers in a fixed order — gateway power and local LAN reachability, gateway configuration, cloud service entitlement, approved user access — because the first layer that fails a test is the layer that owns the repair, and a plan change breaks only the third.

  1. Gateway power and local LAN reachability — power LED and LAN link LED on, and a ping reply from a laptop on the same switch.
  2. Gateway configuration — the local management or status page opens and shows the site's addressing survived.
  3. Cloud service entitlement — the vendor account portal lists the gateway's serial with a plan level actually active.
  4. Approved user access — the connecting engineer holds a named account with a role the current plan still permits.

Worked example, with illustrative numbers from a bench setup: a laptop at 192.168.10.77 pings the gateway at 192.168.10.5 and gets replies in 0.4 ms, pings the PLC at 192.168.10.20 with replies in 0.6 ms, the gateway's local management page loads, and a remote client dialing in over a phone hotspot is refused with a message that amounts to no active service on this device. Score the path: 4 of the 5 checks pass, 4 ÷ 5 = 0.8, so 80% of the tested path is healthy and the single failing check is the entitlement layer. The repair belongs to the subscription, not the cabinet. Treat 0.4 ms and 0.6 ms as example readings only — the pass condition at this stage is any reply at all, not a particular millisecond figure.

What do I test on the gateway before blaming the subscription? #

Confirm power, a lit LAN link LED and a ping reply from a laptop on the same switch before touching the subscription, because a gateway that passes those three tests has already ruled out the physical and network layers, leaving configuration and entitlement as the suspects.

Work down the checks in order and record each result: power LED, LAN link LED, ping to the gateway, ping to the PLC, load of the gateway's local management page. A reply on every line ends the hardware and network questions in about five minutes at the cabinet. One trap distorts these tests: a gateway that answers on its WAN side or shows a cloud status icon is proving reachability, not LAN connectivity — the distinction the page why a WAN ping is reachability, not LAN connectivity draws in detail.

Run the checks from a laptop on the site switch, not from an engineering VM: a VM remote PLC connection behind a NAT adapter can fail for virtual-switch reasons the gateway knows nothing about. So if any of these checks fail, the plan change was never the problem — fix power, cabling or addressing first and retest the remote path afterwards.

Can a factory reset or PLC change bring the remote service back? #

No — a factory reset only wipes configuration stored in the box, a PLC change touches a layer that was never broken, and neither action reaches the account entitlement that the plan change removed in the vendor's cloud.

A reset acts on configuration stored in the box, and the entitlement lives in the vendor's account database, where nothing at the site reaches. Re-flashing, factory resets and new patch cables all leave the account exactly as the plan change made it. Editing the PLC is worse than useless: it damages a healthy layer, and on a running process it is a direct process risk. Never edit or reset PLC code on a running process — bring the line to a safe state in a planned window before anyone opens the program. When the entitlement layer is the failure, the only restoration is commercial — a renewed entitlement or a supported replacement — and technical work on site is preparation for that, never a substitute.

How do I confirm what the new plan still includes? #

Log into the vendor account portal and read the entitlement status attached to the gateway's serial number, then get in writing from the vendor or distributor which features and operating modes the current plan still supports for that model and firmware.

Put the boundary questions in writing: which features the current plan covers, which operating modes remain supported for that model and firmware version, and what happens to the stored configuration if the unit is later re-registered on a different plan. CISA's guidance on managing remote access for industrial control systems treats a remote path as a controlled channel with defined authentication, authorization and monitoring; use those three as the checklist when the vendor states what the plan still enforces. A sales page or a colleague's recollection is not an entitlement — only the account record and a written answer from the vendor or distributor are.

How do I restore access without weakening the controls? #

Renew the entitlement or move to a supported gateway, then re-verify that named users reach only the intended PLC network through the approved path, because a fix that opens inbound ports or shares one credential among engineers is not a fix even when the session connects.

IEC 62443 models a control network as zones joined by conduits, and a remote access path is a conduit: what it may reach, who may pass and what gets logged are part of its definition. A restored or replacement service is only valid if the conduit keeps those three properties — the same layered argument made for layered OT security controls on a network path. The working rules are narrow: named accounts with the fewest rights that work, the vendor's broker enforcing authentication instead of a shared login, the tunnel limited to the PLC network it serves, and session logging left on. A candidate fix that cannot answer who connected, to what and when, fails on that alone, whether or not the session connects.

When is the retired gateway worth keeping? #

Keep it only when the vendor or distributor confirms in writing a supported mode — a paid plan, a documented local broker mode or another documented use — that still meets your authentication and logging requirements, because a device that powers up proves nothing about support.

Sort the unit into one of three states. Keep it in service when the vendor confirms in writing a supported, paid mode that still meets the authentication and logging bar from the section above. Keep it as a cold spare only when its firmware and configuration restore remain documented and obtainable from the maker. Otherwise retire it. If retirement is the outcome, the replacement is ordinary plant hardware: an industrial mini PC in the cabinet running the access service you license, with the segmentation rules carried over unchanged. Whichever state you choose, record it with the vendor's written answer attached, so the next terms change starts from evidence instead of LEDs.

How do I decommission it without leaving a hole in the network? #

Remove the unit from the vendor account, revoke its users and their active sessions, delete the firewall rules that pointed at it and wipe its configuration, because an unregistered but powered gateway on the OT network is an unmonitored path into the PLC zone.

  1. De-register the gateway's serial in the vendor account, so the unit can no longer broker sessions.
  2. Revoke the user side: remove the accounts and have the identity service end active sessions, because a revoked account can still carry valid session tokens until the service itself kills them.
  3. Delete the port forwards, NAT rules and firewall entries that pointed at the unit at the site firewall.
  4. Wipe the stored configuration with the vendor's documented factory-reset procedure, run only after the steps above are recorded.
  5. Log the disposal: serial number, date, who performed it and where the replacement path is documented.

The closing decision is the one this whole article turns on: a plan change removed one of four layers, the tests above locate it in minutes, and the repair happens at the entitlement — renewed, replaced or retired — while power, configuration and user access stay exactly as they were.

Questions asked

Does the gateway still pass local traffic when the cloud plan is gone?

Usually yes: the device keeps switching and serving its local network functions because those run on the box, not in the cloud. Whether its local forwarding modes remain supported under the current terms is a vendor question, so confirm before relying on the leftover behavior in production.

Can I reflash the old gateway for a different vendor's remote service?

No supported path usually exists: gateways authenticate to their maker's broker with certificates tied to the model, and running another service on them is unsupported and outside the documentation. Ask the maker about documented local or offline modes before spending time on firmware experiments.

What should I have ready before calling the vendor about the plan?

The gateway model and serial, its firmware version, the account name and plan level, the date remote sessions stopped, the exact message the client shows, and your local test results: which pings and pages passed and from which device. That set lets support answer in one exchange instead of five.

How do engineers keep working while the entitlement is being restored?

Use a controlled interim path approved by the OT security owner, such as a site firewall VPN with multi-factor authentication limited to named engineers and the PLC network. Personal remote-desktop tools pointed at an office PC or a SCADA host are not an approved path and should not be used.

Keep reading

  • Comparison

    Remote SCADA access through firewalls and proxies

    Put the SCADA application and its data connections on the plant side of the firewall and carry only an authenticated VPN tunnel and a rendered remote session across it. A proxy forwards traffic under its administrator's policy and issues no licenses; session CALs are deployed and tracked on the session host. Restrict tunnel routes to that one host, license by counted people or devices, and keep direct port forwarding to an HMI host out of the design.

    Remote access and virtualization

  • Troubleshooting

    Fixing a VM remote PLC connection with a NAT adapter

    Set the guest's virtual adapter to NAT with DHCP, disable every other guest adapter, and keep the remote-access soft key on the host. The failure that repeats is a second bridged adapter pulling the PLC route away from the NAT path. Test the host path first, then the guest, and check that no local subnet matches the plant network.

    Remote access and virtualization

  • Troubleshooting

    Host blue screen during serial VM connection to a PLC

    A host blue screen during a VM serial session to a PLC is a Windows 10 host crash in the USB-serial and virtualization stack, not a PLC or guest fault. Capture the stop code and version stack, check whether Workstation 14 is documented for your Windows 10 build (Broadcom lists Windows 10 1903 hosts from Workstation 15.x upward), then upgrade Workstation, refresh VMware Tools, and retest before touching adapter or PLC settings.

    Remote access and virtualization