# 1783-NATR to 1769-L18-ER v31.11 OPC-UA **URL:** \ **Category:** Ignition\ **Created:** [October 20, 2018, 1:01am UTC](https://forum.inductiveautomation.com/t/1783-natr-to-1769-l18-er-v31-11-opc-ua/20280 "2018-10-20T01:01:18Z")\ **Posts on this page:** 4\ **Page:** 1
**Author:** ![dustin.cooper](https://sea1.discourse-cdn.com/inductiveautomation/user_avatar/forum.inductiveautomation.com/dustin.cooper/32/29963_2.png) [@dustin.cooper](https://forum.inductiveautomation.com/u/dustin.cooper)\ **Post date:** [October 20, 2018, 1:01am UTC](https://forum.inductiveautomation.com/t/1783-natr-to-1769-l18-er-v31-11-opc-ua/20280/1 "2018-10-20T01:01:19Z")
[http://forum.inductiveautomation.com/t/allen-bradley-1783-natr-network-address-translation-router/14515](http://forum.inductiveautomation.com/t/allen-bradley-1783-natr-network-address-translation-router/14515) Similiar to the thread linked, I am unable to connect to a Compactlogix processor with my Ignition gateway (v7.9.9). I can ping the compactlogix from the server with no issues, and I can get online with and program the PLC with no issues. Typically we use 9300-ENA as our NAT devices, but as the 1783 is considerably cheaper, and takes up less panel space, I am trying a POC to use this router instead. NAT rules: ![](https://us1.discourse-cdn.com/inductiveautomation/original/2X/c/ccd3e54f42388b5bfbd4131d194d59f6f2d02162.png) I’ve tried editing the custom rules on the PLC connection. I’ve opened up tcp/udp port 44818, tcp port 49320, but this does not seem to have any effect. I’ve added the device on the gateway, and if I add an “IsConnected” tag, it will show True for about 10 seconds, and then go to bad quality. ![](https://us1.discourse-cdn.com/inductiveautomation/original/2X/4/4781412f366093c0e190203e8eb3518863649ecf.png) If I add any controller tags, they always show up as bad quality immediately. Hoping someone else has run into this same issue and found a resolution they can share. ---
**Author:** ![pphillips](https://avatars.discourse-cdn.com/v4/letter/p/da6949/32.png) [@pphillips](https://forum.inductiveautomation.com/u/pphillips)\ **Post date:** [October 23, 2018, 4:25pm UTC](https://forum.inductiveautomation.com/t/1783-natr-to-1769-l18-er-v31-11-opc-ua/20280/2 "2018-10-23T16:25:21Z")
Been using one of these for a number of years with a CompactLogix L33R v24 on a DLR. Can you show how your Public and Private networks are configured? There is nothing special required on the Ignition side. ---
**Author:** ![19tb21](https://avatars.discourse-cdn.com/v4/letter/1/0ea827/32.png) [@19tb21](https://forum.inductiveautomation.com/u/19tb21)\ **Post date:** [October 23, 2018, 6:51pm UTC](https://forum.inductiveautomation.com/t/1783-natr-to-1769-l18-er-v31-11-opc-ua/20280/3 "2018-10-23T18:51:05Z")
does the OPC device with the tags in question say it is connected? ---
**Author:** ![dustin.cooper](https://sea1.discourse-cdn.com/inductiveautomation/user_avatar/forum.inductiveautomation.com/dustin.cooper/32/29963_2.png) [@dustin.cooper](https://forum.inductiveautomation.com/u/dustin.cooper)\ **Post date:** [October 23, 2018, 7:34pm UTC](https://forum.inductiveautomation.com/t/1783-natr-to-1769-l18-er-v31-11-opc-ua/20280/4 "2018-10-23T19:34:37Z")
I figured out the problem. It had been a long day at the office when I went to setup the device in Ignition. Instead of using the IP address of the PLC, I used the NATR public port address, which was just off by 1 from the PLC. It was throwing me, because the “IsConnected” device diagnostic tag was showing True. I guess the NATR is just enough like a PLC from Ignition’s perspective that it was able to fool Ignition on some level. 😕 Anyway, after posting the question I went back and double checked my settings and realized my mistake. As you’d expect, it’s working perfectly now.