Can't connect to your machine - Issues and solutions

9 Sep 2026
Knowledge

Problem

You are trying to connect to your machine, but you are not able to.

This article will provide help in troubleshooting and resolving the problem.

Cause

This can have a wide range of causes, such as incorrect configuration or conflicting IP ranges.

Solution

Try the following first. It may solve the issue without further troubleshooting.

Find your manufacturer article in the left menu and follow its instructions (e.g. "Connect to your Siemens").
- These articles contain settings and specific instructions that may be required for your software. These may deviate from how you connect locally.

If it still does not work, proceed below. The solution can only be found by going over a few checks.

Set up a VPN connection to your edge gateway.
Ping the machine. If you are not sure how, see below.

Show/hide steps

Open Command Prompt (Windows) or Terminal (Mac, Linux).
Run the following command to ping the machine. Replace IP_ADDRESS with your machine's IP address:
```
ping IP_ADDRESS
```

On Request timed out or Host unreachable: Proceed below.

On Reply from <ip address>: Skip to step 7.

Verify that the edge gateway's LAN IP address is in the same IP range as the machine.
- Tip: Find this and other LAN settings at Fleet Manager > Devices > Click on your device name > Network > LAN.
Verify that the edge gateway's LAN Network mask is the exact same as the machine's network mask.
- Tip: In most cases it's 255.255.255.0.
Verify that the edge gateway's LAN Source NAT is enabled or that the machine's default gateway is correctly configured.
- Tip: Only one of these is required. Both are fine as well.
- Note that some software programs require this setting to be turned off. Check your manufacturer article in the left menu for specifics (e.g. "Connect to your Siemens").
- The machine's default gateway is an option in the machine's network settings that should be set to the edge gateway's LAN IP address.
If you made a change in the edge gateway's settings, don't forget to Confirm changes and then Push device config.
- The edge gateway may temporarily disconnect and LAN communication may be temporarily interrupted while it's applying the new settings. This only takes a moment.

If you changed a setting, that may have fixed the issue. Test whether it works now. If it still does not work, proceed below.

Verify that your computer's IP range does not conflict with the edge gateway's LAN IP range. If you're unsure how, see below.

Show/hide steps

Open Command Prompt (Windows) or Terminal (macOS, Linux).
Run the following command to find your computer's local IP range:
Windows macOS Linux
ipconfig
ifconfig
ip addr
See if any network interface has the same IP range or an overlapping IP range with the edge gateway's LAN IP range.
- Tip: Find this at Fleet Manager > Devices > Click on your device name > Network > LAN.
- If you're having difficulty determining what the IP range is, please consult a colleague that is knowledgeable with networks, for example your IT department. If no such person exists or is available, please contact us and explain your problem and question in as much detail as possible.
If there is a conflict, resolve it. One of the two IP ranges will need to be changed. See below for more details.
- Change the edge gateway's LAN IP range.
  - Keep in mind that the IP range of the machine needs to match the LAN IP range of the edge gateway. That means the network settings of the connected equipment will need to be updated as well.
  - Tip: In terms of practical advice it is recommended to first change the network settings of the connected equipment and then change the edge gateway's LAN IP range last. This enables you to make this change remotely.
- Change your computer's IP range.
  - Tip: Perhaps another office network is available with a different IP range. Contact your IT department for available options.

Windows	macOS	Linux
ipconfig	ifconfig	ip addr

Verify that the machine's IP address does not conflict with the IP address of another device in the machine network.
- Tip: The most common conflict is that the edge gateway's LAN IP address and the machine's IP address are the same. This is an incorrect configuration. Every device needs to have a unique IP address.

If you changed a setting, that may have fixed the issue. Test whether it works now. If it still does not work, proceed below.

Additional checks and solutions are available for specific manufacturers or software programs. See if yours is listed below and follow the instructions.

Allen-Bradley (RSLinx Classic / FactoryTalk Linx)

Verify that the edge gateway's LAN Network mask is the exact same as the machine's network mask.
- Tip: In most cases it's 255.255.255.0.
- Tip: Find this and other LAN settings at Fleet Manager > Devices > Click on your device name > Network > LAN.
Verify that firewall software on your computer, like Windows Firewall, is not blocking the PLC's response.
- Windows considers the VPN connection to be an unknown network and therefore treats it like a public network. The automated firewall rule by RSLinx Classic and FactoryTalk Linx does not apply to public networks. Therefore the PLC's response gets blocked by Windows Firewall. Solution: add Public in the RSLinx.exe UDP protocol firewall rules.
- Alternatively, you can also allow specific ports. For specifically RSLinx Classic, allow UDP port 2222 on your computer's firewall. If that doesn't resolve the issue, search online for Rockwell Automation's "TCP and UDP Port Configuration" or contact Rockwell Automation for information on which ports to allow on your computer's firewall so the PLC's response will not get blocked.

CODESYS

Verify that you are using CODESYS V3.5 SP12 or higher. This version contains a crucial bug fix related to remote connectivity.
- If you cannot update your CODESYS in its entirety, instead only update CODESYS Gateway. After the update completes, open CODESYS Installer and set the new version as Gateway Service. Your older CODESYS version will then use the latest version of CODESYS Gateway
Verify that firewall or antivirus software on your computer is not blocking any communication. You can test this by temporarily disabling this software and trying to connect again.

Mitsubishi (GX Works2 / GX Works3)

In GX Works2 and 3, verify that you have a Melsoft Connection Module for each Mitsubishi device (e.g. 1x HMI and 1x PLC = 2x Melsoft Connection Module).

Omron (CX-Designer / NB-Designer)

If in CX-Designer you get error "Failed to process CX Server (05) , (0018)": Restart CX-Designer or restart your computer entirely and try again.
If in NB-Designer your download to an Omron NB Series HMI starts but never completes: Verify that you have enabled communication over VPN in the HMI settings.

Siemens (TIA Portal)

Verify that your edge gateway is running the correct version.
- An IXrouter2 should run firmware 2.9 or higher.
- An IXrouter3 should run firmware 3.4 or higher.
- Tip: For help and important information regarding firmware upgrades, see Firmware upgrade - Important information and step-by-step guide.
Verify that the edge gateway's LAN Network mask is the exact same as the machine's network mask.
- Tip: In most cases it's 255.255.255.0.
- Tip: Find this and other LAN settings at Fleet Manager > Devices > Click on your device name > Network > LAN.
Disable and re-enable the "TAP-Windows adapter"-network adapter on your computer and try again.
- Tip: Simultaneously press the windows key and R to open the Run window and enter "ncpa.cpl".
TIA Portal may not send its PROFINET discovery packet (PN-DCP) over the VPN connection. Restart TIA Portal or, if that doesn't resolve the issue, restart your computer entirely.
- This behavior has been observed in multiple past support tickets.
- Do not skip these actions, as they have proven to resolve this issue.
If your Siemens PLC is connected to a Siemens network switch, that may unintentionally prevent your devices from being found. Connect the PLC directly to the edge gateway or replace the network switch with that of a different manufacturer.
- This behavior has been observed in one or more past support tickets.
- Do not skip these actions, as they have proven to resolve this issue.
If you have another IXON edge gateway on-site that you have connected with their LAN to each other, that may unintentionally prevent your devices from being found. Disconnected the LAN of one of the edge gateways.

Virtual machine

Restart the VM or restart your computer entirely and try again.

If your issue is still not resolved, please contact us and include in your message: a clear problem description, and what you've already checked and done. We will then troubleshoot this further with you.

Title

Can't connect to your machine - Issues and solutions

URL Name

Can-t-connect-to-your-machine---Issues-and-solutions

Can't connect to your machine - Issues and solutions

Introduction

Remote Access

Fleet Management

User Management

Customer Portal

Machine Data

Notifications

Hardware

Open Innovation

Security and Availablility

Release Notes

Knowledge

Can't connect to your machine - Issues and solutions

New Section

Properties

Introduction

Getting Started

Remote Access

VPN connection

VPN Client

Web Access

Connect to your machine

Connection details

Fleet Management

Edge gateway registration

IXagent registration

WAN Settings

LAN Settings

Edge gateway firewall

General device settings

User Management

Setup

Invite and manage users

My account

External Identity And Access Management

Customer Portal

Custom login page and homepages

White labeling

Machine Data

Live Data

Historical Data

Data Source protocols

Pages, cards, and reports

Components

AI assistant

Notifications

Alarms & Notifications

Hardware

Edge gateways and accessories

Open Innovation

Custom development

Marketplace

Security and Availablility

Security

Availability

Release Notes

IXON Cloud

Knowledge

Highlighted Articles

Tips

Related Articles