# Why does FT Linx encapsulated ports impact OPC UA device connections? **URL:** \ **Category:** Ignition\ **Created:** [June 3, 2025, 10:06pm UTC](https://forum.inductiveautomation.com/t/why-does-ft-linx-encapsulated-ports-impact-opc-ua-device-connections/106987 "2025-06-03T22:06:16Z")\ **Posts on this page:** 5\ **Page:** 1
**Author:** ![pdixon](https://sea1.discourse-cdn.com/inductiveautomation/user_avatar/forum.inductiveautomation.com/pdixon/32/6899_2.png) [@pdixon](https://forum.inductiveautomation.com/u/pdixon)\ **Post date:** [June 3, 2025, 10:06pm UTC](https://forum.inductiveautomation.com/t/why-does-ft-linx-encapsulated-ports-impact-opc-ua-device-connections/106987/1 "2025-06-03T22:06:16Z")
I have an OPC UA device connection to Rockwell Emulate that is setup as described under "How to connect Inductive Automation "Ignition" to local Rockwell Emulate through OPC UA" at [RESOURCES](https://dpas-inc.com/resources). I use the "Ignition OPC UA Server" with the OPC UA device for my Emulate. I found that the device connection that used to work recently showed Reconnect/Wait. It took a while to find the FactoryTalk Linx Browser had "Listen on Ethernet/IP encapsulation ports" unchecked. Check I checked the box the device connected. ![ig_opcua_2025-06-02 at 12.32.07 PM](https://us1.discourse-cdn.com/inductiveautomation/original/3X/8/2/82da55ee21bcc6c8c1b5f2d6557edd1662a93cd3.jpeg) Can anyone explain how this works? Why does this matter? For reference, a lengthy discussion on this topic is found at [OPC to Emulate, still looking for answers - #52 by Simen\_Minerd](https://forum.inductiveautomation.com/t/opc-to-emulate-still-looking-for-answers/80088/52) ---
**Author:** ![pturmel](https://sea1.discourse-cdn.com/inductiveautomation/user_avatar/forum.inductiveautomation.com/pturmel/32/3295_2.png) [@pturmel](https://forum.inductiveautomation.com/u/pturmel)\ **Post date:** [June 3, 2025, 10:41pm UTC](https://forum.inductiveautomation.com/t/why-does-ft-linx-encapsulated-ports-impact-opc-ua-device-connections/106987/2 "2025-06-03T22:41:47Z")
Why would you think FT Linx can accept connections if it isn't listening? (The Encapsulation port is 44818--that's the port real PLCs listen on for EtherNet/IP.) That particular setting is discussed in detail in the linked topic, too. ---
**Author:** ![pdixon](https://sea1.discourse-cdn.com/inductiveautomation/user_avatar/forum.inductiveautomation.com/pdixon/32/6899_2.png) [@pdixon](https://forum.inductiveautomation.com/u/pdixon)\ **Post date:** [June 5, 2025, 1:30pm UTC](https://forum.inductiveautomation.com/t/why-does-ft-linx-encapsulated-ports-impact-opc-ua-device-connections/106987/3 "2025-06-05T13:30:26Z")
Thank you Phil. I can always count on you for a colorful comment. The topic that is referenced does have your comment (number 42) and illustration of the FT Linx browser. Perhaps I am the only one that does not understand the communication path from the gateway OPC UA connection to the OPC UA device to FT Linx through whatever the FT Linx browser is showing and the role of the encapsulation port. If there is something I can read that lays that out, it would help me understand why it can be in ReconnectWait mode if the checkbox is not selected. Particularly, in my case when I am connecting to Emulate I only see Windows Default in the Interface, so there is no IP address that I need to configure. I use LocalHost in the DeviceConnection instead of a hard coded IP. I know the listen on encapsulation ports checkbox fixes it, but not entirely sure why. Is there a reason someone would want this checkbox unchecked? Any illumination or reference would be appreciated. ---
**Author:** ![pturmel](https://sea1.discourse-cdn.com/inductiveautomation/user_avatar/forum.inductiveautomation.com/pturmel/32/3295_2.png) [@pturmel](https://forum.inductiveautomation.com/u/pturmel)\ **Post date:** [June 5, 2025, 1:36pm UTC](https://forum.inductiveautomation.com/t/why-does-ft-linx-encapsulated-ports-impact-opc-ua-device-connections/106987/4 "2025-06-05T13:36:40Z")
It is explained in comments 43, 44, and 45 in that same topic. Which is why comment #47 instructs you to use "michael's tweak". If you don't understand the significance of the `netstat` output, I recommend you look for some fundamental training in how TCP/IP works. > [@pdixon](#): > > for a colorful comment. As to that: I've noted, for a long time now, that you do not read or try to understand what I write, like those listed comments, unless I phrase it ~~harshly~~ _colorfully_. ---
**Author:** ![Felipe\_CRM](https://avatars.discourse-cdn.com/v4/letter/f/dfb087/32.png) [@Felipe\_CRM](https://forum.inductiveautomation.com/u/Felipe_CRM)\ **Post date:** [June 5, 2025, 2:07pm UTC](https://forum.inductiveautomation.com/t/why-does-ft-linx-encapsulated-ports-impact-opc-ua-device-connections/106987/5 "2025-06-05T14:07:52Z")
> [@pdixon](#): > > Is there a reason someone would want this checkbox unchecked? Besides the case where you're not using FT Linx as a server and don't need it, it seems to be there for conflict avoidance: "FactoryTalk Edge Gateway running on a workstation can also listen on this port, resulting in a race condition" > **[FactoryTalk Linx and FactoryTalk Logix Echo binding to port 44818](https://www.rockwellautomation.com/en-in/docs/factorytalk-edge-gateway/distributed-1-00/ft-edge-gateway-help-ditamap/data-sources/data-source-configuration/add-auto-discovery-and-model/ftlinx-and-ft-logix-echo-binding.html)** > > null