You open Studio 5000 to go online with a ControlLogix controller that you were connected to 20 minutes ago. The project opens, you click Go Online, and the “Communication Path Not Found” message appears. Nothing physically changed — the Ethernet cable is in the same port, the controller is running, the IP address in the project path is the same one it has always been. This RSLinx Classic communication path not found error fix for Studio 5000 covers the complete diagnostic sequence from RSLinx driver verification through path correction, VPN adapter conflicts, and registry-level repair. The most common cause is not a network issue: it is that RSLinx Classic lost its driver configuration after a Windows update, a USB disconnection event, or an RSLinx service restart. The second most common cause is that the IP address in the Studio 5000 communication path does not match the controller’s current IP. When neither of those explains it, the cause is almost always one of two things competitor guides skip entirely: a VPN adapter silently taking driver priority over the plant NIC, or Windows Registry corruption in RSLinx’s own driver-configuration keys that makes a fix from Step 2 revert itself on the next reboot.
- Root Cause Quick Reference
- What “Communication Path Not Found” Means in the RSLinx/Studio 5000 Architecture
- Step 1: Verify RSLinx Classic Service Is Running
- Step 2: Verify and Reconfigure the RSLinx EtherNet/IP Driver
- Step 3: Verify the Communication Path in Studio 5000
- Step 4: Use RSLinx RSWho to Browse to the Controller
- Step 5: Check Windows Firewall — RSLinx Port Requirements
- Step 6: IP Address or Slot Number Mismatch in Studio 5000 Path
- RSLinx Classic Version Compatibility with Studio 5000
- Step 7: VPN Adapter Conflicts and Windows Registry Corruption
- Technical Validation
- Frequently Asked Questions
Root Cause Quick Reference
| Root Cause | Diagnostic Signal | Quick Fix |
|---|---|---|
| RSLinx driver not configured / wrong adapter | No driver appears in RSLinx Configure Drivers, or wrong NIC selected | Add EtherNet/IP driver pointing to plant NIC (Step 2) |
| Communication path wrong in Studio 5000 | “Communication Path Not Found” error on Go Online | Set path via Who Active → select controller (Steps 3–4) |
| RSLinx Classic version incompatible with Studio 5000 | Consistent errors after Studio 5000 upgrade; older RSLinx version | See Step 5: RSLinx Classic vs RSLinx Gateway version check |
| VPN adapter taking driver priority | Error appears only when VPN is connected; works fine at plant without VPN | Disable VPN adapter or lower its metric (Step 7) |
| Windows Registry corruption | Same path fix has to be reapplied after every reboot | Rebuild CIP Drivers registry subkey (Step 7) |
What “Communication Path Not Found” Means in the RSLinx/Studio 5000 Architecture
Studio 5000 does not communicate directly with the controller — it uses RSLinx Classic as a communication broker. The communication path has three layers:
- RSLinx Classic service — a Windows service that must be running
- RSLinx driver — a configured EtherNet/IP, USB, or serial driver that points to the network or device
- Controller path — the specific address within the driver’s network (IP address + chassis slot for ControlLogix)
“Communication Path Not Found” can originate at any of these three layers. The diagnostic sequence moves top-down: service first, driver second, path third. If the service is not running, diagnosing the driver is pointless. If the driver is not configured, diagnosing the path is pointless.
Step 1: Verify RSLinx Classic Service Is Running
Method 1 — Windows Services:
Windows → Services (services.msc) →
Find: "RSLinx Classic" →
Status must be: Running
If the service is Stopped: right-click → Start. If it fails to start, check Windows Event Viewer → Application log for RSLinx Classic error entries — typically indicates a license file issue or RSLinx installation corruption.
Method 2 — Task Manager:
Ctrl+Shift+Esc → Details tab →
Find: rslinx.exe → Status: Running
If RSLinx Classic is not visible in the process list, the service is not running. Start it via services.msc.
Method 3 — RSLinx Classic directly: Open RSLinx Classic from the Start menu (Rockwell Software → RSLinx Classic → RSLinx Classic). If the application opens and shows a red indicator or “Service Not Running” banner, the service needs to be started or reinstalled.
Step 2: Verify and Reconfigure the RSLinx EtherNet/IP Driver
RSLinx Classic uses “drivers” — configured communication adapters — to communicate with controllers. The most common driver for Studio 5000 over Ethernet is the “EtherNet/IP” driver (also called “AB_ETHIP” or “AB-ETHIP-x” depending on the RSLinx version).
Verify the driver exists and is working:
RSLinx Classic → Communications → Configure Drivers →
Check the driver list for an EtherNet/IP driver
Status column must show: Running (not Error, Paused, or Not Running)
If no EtherNet/IP driver exists (common after RSLinx reinstall or Windows update):
Communications → Configure Drivers →
Add New →
Driver Type: EtherNet/IP →
Select the correct network adapter (the NIC connected to the PLC network) →
Finish → Close
If the driver exists but shows Error status:
Select the driver → Properties →
Verify: the correct network adapter is selected
(not a VPN adapter, not a virtual adapter like VMware Network)
→ Apply → OK
After reconfiguring the driver, the Status must change to “Running” within 5 seconds. If it remains in Error, the selected network adapter may not be connected or may be disabled in Windows Device Manager.
Step 3: Verify the Communication Path in Studio 5000
The communication path in Studio 5000 is the specific address used to reach the controller. For ControlLogix controllers accessed over Ethernet, the path format is:
[Driver Name] → [Controller IP Address], [Backplane Slot Number]
Example: AB_ETHIP-1 \ 192.168.1.1 \ 0 means: use EtherNet/IP driver, connect to IP 192.168.1.1, controller is in backplane slot 0 (for ControlLogix, the controller module slot in the 1756 chassis).
Access the path in Studio 5000:
Studio 5000 → Controller Properties → General tab →
Communication: Path field → Edit (pencil icon)
The path dialog shows the current configured path. If the path is empty or shows a device that no longer exists (e.g., an IP address that changed), the path must be updated.
Update the path using RSWho browser (described in Step 4).
Step 4: Use RSLinx RSWho to Browse to the Controller
RSWho is the RSLinx Classic device browser — it shows all devices visible through each configured driver. If RSWho shows the controller, the communication path can be set by pointing Studio 5000 directly at the RSWho result.
Access RSWho:
RSLinx Classic → Communications → RSWho
OR: Studio 5000 → Controller Properties → Path → Edit →
Browse button → This opens RSWho within the path dialog
RSWho navigation:
Expand the EtherNet/IP driver node (AB_ETHIP-1 or similar) →
The driver node shows all devices on the Ethernet network →
Find the ControlLogix controller (shows chassis icon) →
Expand the chassis node → shows the controller module in its slot →
Double-click or select the controller module → path is populated
RSWho cannot see the controller: – The Ethernet driver is not configured or not running (Step 2) – The controller is on a different subnet (RSWho browses the local subnet only) – The controller is powered off – The workstation NIC is not on the same subnet as the controller (check Windows IP configuration)
For controllers on a different subnet, RSLinx requires a “Specify Path” approach: instead of browsing through the EtherNet/IP driver to find devices, use the “Ethernet” driver type and enter the controller IP address directly. This approach bypasses subnet discovery requirements.
Step 5: Check Windows Firewall — RSLinx Port Requirements
Windows Firewall can block RSLinx Classic communication even when the RSLinx service is running and the driver is configured. After Windows updates, firewall rules are sometimes reset or overridden.
Ports required by RSLinx Classic for EtherNet/IP communication:
| Port | Protocol | Purpose |
|---|---|---|
| 44818 | TCP | EtherNet/IP connection establishment |
| 44818 | UDP | EtherNet/IP implicit messaging |
| 2222 | UDP | EtherNet/IP I/O data |
| 1756-based ports | TCP/UDP | ControlLogix backplane communication via the 1756-EN2T module |
Quick test — disable Windows Firewall temporarily: If the Communication Path Not Found error resolves after disabling the Windows Firewall, a firewall rule is blocking RSLinx. Create permanent inbound and outbound rules for rslinx.exe (allowing all ports), then re-enable the firewall. Do not leave the firewall permanently disabled.
Create RSLinx firewall exceptions:
Windows Defender Firewall → Advanced Settings →
Inbound Rules → New Rule → Program →
Browse: C:\Program Files (x86)\Rockwell Software\RSLinx\rslinx.exe →
Allow the connection → Apply to all profiles → Name: RSLinx Classic
Repeat for Outbound Rules.
Step 6: IP Address or Slot Number Mismatch in Studio 5000 Path
The most frequent final cause — once the RSLinx service and driver are confirmed working — is that the IP address or slot number in the Studio 5000 communication path no longer matches the physical controller configuration.
IP address mismatch scenarios: – The controller’s IP address was changed by another technician (from the controller keypad or via RSLinx) – The controller’s IP is assigned by DHCP and has changed since the project was created (all industrial controllers should have static IPs) – The project was copied from a different system with a different controller IP
Slot number mismatch scenarios: – The ControlLogix controller module was moved to a different slot in the 1756 chassis – The project was created for a different chassis configuration where the controller was in slot 0, but the current chassis has the controller in slot 2
Verify the controller’s actual IP and slot:
RSLinx RSWho → Browse the EtherNet/IP driver →
The chassis node shows the IP address used to reach it
Expand the chassis → each module shows its physical slot number
The controller module's slot number is required in the path
Update the Studio 5000 communication path to match the actual IP and slot number shown in RSWho. For the complete Allen-Bradley fault code reference used after successful connection, see Allen-Bradley Controllogix Fault Codes Complete List Studio 5000. For EtherNet/IP connection timeout faults that may co-occur with communication path issues, see Allen-Bradley Ethernet/Ip Connection Timeout Fault Controllogix Fix. For the Siemens TIA Portal equivalent of connection path issues and diagnostic buffer reading after establishing connection, see Tia Portal How To Read Diagnostic Buffer Online Step By Step.
RSLinx Classic Version Compatibility with Studio 5000
Not all RSLinx Classic versions communicate cleanly with all Studio 5000 versions. After a Studio 5000 upgrade, the “Communication Path Not Found” error can appear even when the driver and path were previously working — and the root cause is an RSLinx Classic version that predates the Studio 5000 release.
Check your versions: – Studio 5000 V33 and later requires RSLinx Classic V3.90 or later – Studio 5000 V32 requires RSLinx Classic V3.80 or later – RSLinx Classic V2.x (from RSLogix 5000 V20 era) is not compatible with Studio 5000 V30+
RSLinx Classic vs RSLinx Gateway: RSLinx Classic is the standard single-machine communication server — it manages driver-to-controller connections on one PC. RSLinx Gateway (a separate licensed product) extends RSLinx Classic connections to other network nodes. If your plant uses RSLinx Gateway and you are trying to configure a path through it, the path syntax differs: instead of selecting a local driver, you specify the Gateway server IP and the path continues from there. “Communication Path Not Found” through a Gateway is diagnosed at the Gateway server, not at the local RSLinx Classic instance.
Version upgrade fix: If the version mismatch is the root cause, download the latest RSLinx Classic from the Rockwell Automation Product Compatibility and Download Center (PCDC) matching your current Studio 5000 version. Uninstall the old RSLinx Classic first, then install the new version — do NOT layer-upgrade without uninstalling, as residual registry entries can cause persistent path errors.
Step 7: VPN Adapter Conflicts and Windows Registry Corruption
If Steps 1 through 6 all check out — service running, driver shows Running, RSWho browses the network fine, path matches the controller — and the error still appears, or it clears temporarily and comes back after every reboot, the cause is one of two things almost no other RSLinx troubleshooting guide documents.
VPN adapter taking driver priority:
Corporate laptops with a VPN client (Cisco AnyConnect, GlobalProtect, FortiClient, Pulse Secure) install a virtual network adapter that Windows treats as a higher-metric route than the plant Ethernet NIC, even when the VPN itself is disconnected. RSLinx’s EtherNet/IP driver binds to whichever adapter Windows currently ranks first. When the VPN client’s virtual adapter is enabled — even idle, not connected — RSLinx can silently bind to it instead of the NIC physically wired to the plant network, and EtherNet/IP broadcasts never reach the controller.
Diagnosing the VPN conflict:
Windows → Control Panel → Network and Sharing Center → Change adapter settings →
Note every adapter, including disabled and virtual ones (Cisco AnyConnect, TAP-Windows Adapter, GlobalProtect, etc.) →
For the plant NIC: right-click → Properties → Internet Protocol Version 4 → Advanced →
Note the metric value (lower = higher priority)
Fix: disable the VPN client’s virtual adapter while doing plant work (Device Manager → Network adapters → right-click the VPN adapter → Disable), or manually set the plant NIC’s interface metric lower than the VPN adapter’s metric (netsh interface ipv4 set interface "Ethernet" metric=1 from an elevated command prompt) so Windows — and RSLinx — always prefer the wired plant connection.
Windows Registry corruption — the “fix reverts after every reboot” symptom:
RSLinx Classic stores its driver configuration (driver type, bound adapter, IP settings) in the Windows Registry under:
HKEY_LOCAL_MACHINE\SOFTWARE\WOW6432Node\Rockwell Software\RSLinx\CIP Drivers
If this registry branch is partially corrupted — most commonly after an interrupted Windows Update, an antivirus quarantine action on an RSLinx DLL, or a forced shutdown while RSLinx was writing driver state — RSLinx can appear to reconfigure successfully in the Configure Drivers dialog (Step 2), show Running status, and then silently discard the change on the next service restart or reboot, reverting to the broken state. This is the specific pattern that distinguishes registry corruption from a simple misconfiguration: the same fix has to be reapplied after every restart.
Fix — repair the registry branch:
1. Close RSLinx Classic completely and stop the RSLinx Classic service (services.msc).
2. Back up the key first: regedit → navigate to HKEY_LOCAL_MACHINE\SOFTWARE\WOW6432Node\Rockwell Software\RSLinx → right-click → Export → save a .reg backup file.
3. Delete the CIP Drivers subkey entirely (not the parent RSLinx key).
4. Restart the RSLinx Classic service, then reopen RSLinx Classic — it rebuilds the CIP Drivers subkey from scratch with default (empty) state.
5. Reconfigure the EtherNet/IP driver from Step 2 on the clean subkey.
If the fix now survives a reboot, the original registry branch was corrupted. If RSLinx fails to start at all after the service restart, restore the exported .reg backup and proceed to a full RSLinx Classic uninstall/reinstall instead — the corruption extends beyond the CIP Drivers subkey.
RSLinx Classic EtherNet/IP driver configuration, path structure, and RSWho browser operation from the Rockwell Automation EtherNet/IP Communication Modules User Manual. RSLinx driver setup and EtherNet/IP communication path configuration for Studio 5000 from The Automation Store RSLinx EtherNet/IP Driver Configuration Guide. Industrial PLC networking and communication training from Moraine Park Technical College PLC manufacturing boot camps.
Frequently Asked Questions
RSLinx RSWho shows the controller but Studio 5000 still says “Communication Path Not Found” when trying to go online. What could explain this?
If RSWho shows the controller but Studio 5000 cannot connect, the Studio 5000 project’s communication path configuration does not match what RSWho is using. The most common cause: the project has a hardcoded path (IP address entered directly, not browsed through RSWho) that differs from the IP RSWho discovered. Fix: go online → Communication Path dialog → use the Browse button to select the controller through RSWho rather than typing the IP address directly. Also verify the chassis slot number — RSWho shows the controller in its physical slot, and the path must specify the correct slot.
RSLinx was working this morning, but after a Windows restart it shows “Communication Path Not Found.” RSLinx seems to lose its configuration after reboots. Why?
RSLinx Classic driver configuration can be lost after Windows updates or if the RSLinx service starts before the network adapter is fully initialized. Fix: set the RSLinx Classic Windows service to “Automatic (Delayed Start)” instead of “Automatic” — this ensures RSLinx starts after the network stack is fully ready. Go to services.msc → RSLinx Classic → Properties → Startup type: Automatic (Delayed Start). This prevents RSLinx from initializing before the NIC is ready and avoids the lost-driver symptom.
Can Studio 5000 communicate with a ControlLogix controller without RSLinx Classic being installed?
Studio 5000 V21 and later supports direct connection to Logix5000 controllers over Ethernet without RSLinx Classic — this is called “Logix Designer Direct Connect.” The direct connect option appears in the controller path dialog when RSLinx is not installed. However, RSLinx Classic remains required for: (1) communication with older controllers (MicroLogix, SLC 500, PLC-5) that do not support direct connect, (2) connections over serial or DF1 rather than Ethernet, (3) FactoryTalk applications (FactoryTalk View, FactoryTalk Historian) which still use RSLinx as their communication layer. For a standalone Studio 5000 installation with a single ControlLogix controller on Ethernet, direct connect eliminates the RSLinx dependency entirely.
To configure Logix Designer Direct Connect: Controller Properties → Communication → Path → Edit → select Ethernet as the driver type → enter the controller IP address and chassis slot directly. The path format is Ethernet\[Controller_IP]\[slot] — for example, Ethernet\192.168.1.1\0 for a ControlLogix controller at 192.168.1.1 in backplane slot 0. No RSLinx driver configuration is required before using this path.