# Allen-Bradley Logix Driver works on one gateway but not another **URL:** \ **Category:** Ignition\ **Created:** [August 12, 2024, 9:48pm UTC](https://forum.inductiveautomation.com/t/allen-bradley-logix-driver-works-on-one-gateway-but-not-another/94562 "2024-08-12T21:48:40Z")\ **Posts on this page:** 9\ **Page:** 1
**Author:** ![blackdog](https://avatars.discourse-cdn.com/v4/letter/b/d26b3c/32.png) [@blackdog](https://forum.inductiveautomation.com/u/blackdog)\ **Post date:** [August 12, 2024, 9:48pm UTC](https://forum.inductiveautomation.com/t/allen-bradley-logix-driver-works-on-one-gateway-but-not-another/94562/1 "2024-08-12T21:48:40Z")
I have a gateway that has 8 OPCUA Devices configured. 3 of them are not working properly. One is an A-B Logix Driver that is configured exactly like one on another gateway talking to the same PLC. This one that doesn't work is not the only A-B Logix Driver on the new gateway. Some work and some don't. The one that is troubling me is the one that works on the other gateway but doesn't work on this gateway. Both gateways are running v8.1.41. Any suggestions? ---
**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:** [August 12, 2024, 9:50pm UTC](https://forum.inductiveautomation.com/t/allen-bradley-logix-driver-works-on-one-gateway-but-not-another/94562/2 "2024-08-12T21:50:57Z")
Hmm. Some difference in the gateways that we can't see? 🤪 Share more details. ---
**Author:** ![michael.flagler](https://sea1.discourse-cdn.com/inductiveautomation/user_avatar/forum.inductiveautomation.com/michael.flagler/32/26272_2.png) [@michael.flagler](https://forum.inductiveautomation.com/u/michael.flagler)\ **Post date:** [August 12, 2024, 9:52pm UTC](https://forum.inductiveautomation.com/t/allen-bradley-logix-driver-works-on-one-gateway-but-not-another/94562/3 "2024-08-12T21:52:38Z")
What model of PLC? ControlLogix, CompactLogix? What firmware revision? Are they on the same network subnet? How many connections do you have configured (are you overloading the PLC?). Make sure you can ping the PLC and have the correct slot number configured in the configuration. As Phil said, we need a lot more details as there's no way for us to read your mind or your config. ---
**Author:** ![blackdog](https://avatars.discourse-cdn.com/v4/letter/b/d26b3c/32.png) [@blackdog](https://forum.inductiveautomation.com/u/blackdog)\ **Post date:** [August 12, 2024, 10:03pm UTC](https://forum.inductiveautomation.com/t/allen-bradley-logix-driver-works-on-one-gateway-but-not-another/94562/4 "2024-08-12T22:03:22Z")
I expect there is but I'm not sure where to look. I've checked obvious things. ---
**Author:** ![blackdog](https://avatars.discourse-cdn.com/v4/letter/b/d26b3c/32.png) [@blackdog](https://forum.inductiveautomation.com/u/blackdog)\ **Post date:** [August 12, 2024, 10:06pm UTC](https://forum.inductiveautomation.com/t/allen-bradley-logix-driver-works-on-one-gateway-but-not-another/94562/5 "2024-08-12T22:06:07Z")
That's why I'm concentrating on the one that works on one gateway but not the other. This shouldn't have anything to do with the PLC then. Also, I disabled the other gateway's driver in case the PLC was overloaded, but still no joy with the new gateway for that same PLC. When I re-enable it on the other gateway, it reconnects just fine. ---
**Author:** ![blackdog](https://avatars.discourse-cdn.com/v4/letter/b/d26b3c/32.png) [@blackdog](https://forum.inductiveautomation.com/u/blackdog)\ **Post date:** [August 12, 2024, 10:17pm UTC](https://forum.inductiveautomation.com/t/allen-bradley-logix-driver-works-on-one-gateway-but-not-another/94562/6 "2024-08-12T22:17:08Z")
I can ping the PLC. The configuration is exactly the same as it is in the other gateway. This is the timeout message: ```python java.util.concurrent.CompletionException: io.netty.channel.ConnectTimeoutException: connection timed out after 2000 ms: /192.168.130.104:44818 at java.base/java.util.concurrent.CompletableFuture.encodeThrowable(Unknown Source) at java.base/java.util.concurrent.CompletableFuture.completeThrowable(Unknown Source) at java.base/java.util.concurrent.CompletableFuture$UniCompose.tryFire(Unknown Source) at java.base/java.util.concurrent.CompletableFuture.postComplete(Unknown Source) at java.base/java.util.concurrent.CompletableFuture.completeExceptionally(Unknown Source) at com.digitalpetri.enip.EtherNetIpClient.lambda$bootstrap$8(EtherNetIpClient.java:391) at io.netty.util.concurrent.DefaultPromise.notifyListener0(DefaultPromise.java:590) at io.netty.util.concurrent.DefaultPromise.notifyListeners0(DefaultPromise.java:583) at io.netty.util.concurrent.DefaultPromise.notifyListenersNow(DefaultPromise.java:559) at io.netty.util.concurrent.DefaultPromise.notifyListeners(DefaultPromise.java:492) at io.netty.util.concurrent.DefaultPromise.setValue0(DefaultPromise.java:636) at io.netty.util.concurrent.DefaultPromise.setFailure0(DefaultPromise.java:629) at io.netty.util.concurrent.DefaultPromise.tryFailure(DefaultPromise.java:118) at io.netty.channel.nio.AbstractNioChannel$AbstractNioUnsafe$1.run(AbstractNioChannel.java:262) at io.netty.util.concurrent.PromiseTask.runTask(PromiseTask.java:98) at io.netty.util.concurrent.ScheduledFutureTask.run(ScheduledFutureTask.java:153) at io.netty.util.concurrent.AbstractEventExecutor.runTask(AbstractEventExecutor.java:173) at io.netty.util.concurrent.AbstractEventExecutor.safeExecute(AbstractEventExecutor.java:166) at io.netty.util.concurrent.SingleThreadEventExecutor.runAllTasks(SingleThreadEventExecutor.java:470) at io.netty.channel.nio.NioEventLoop.run(NioEventLoop.java:569) at io.netty.util.concurrent.SingleThreadEventExecutor$4.run(SingleThreadEventExecutor.java:997) at io.netty.util.internal.ThreadExecutorMap$2.run(ThreadExecutorMap.java:74) at java.base/java.lang.Thread.run(Unknown Source) Caused by: io.netty.channel.ConnectTimeoutException: connection timed out after 2000 ms: /192.168.130.104:44818 at io.netty.channel.nio.AbstractNioChannel$AbstractNioUnsafe$1.run(AbstractNioChannel.java:261) ``` ---
**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:** [August 12, 2024, 10:21pm UTC](https://forum.inductiveautomation.com/t/allen-bradley-logix-driver-works-on-one-gateway-but-not-another/94562/7 "2024-08-12T22:21:34Z")
> [@blackdog](#): > > `connection timed out after 2000 ms` The packets are getting dropped. Ping is not a definitive test--it just checks the ICMP path, not the port actually needed (44818). > [@blackdog](#): > > I've checked obvious things. In the future, **tell us** these obvious things. We can't help you without them. ---
**Author:** ![michael.flagler](https://sea1.discourse-cdn.com/inductiveautomation/user_avatar/forum.inductiveautomation.com/michael.flagler/32/26272_2.png) [@michael.flagler](https://forum.inductiveautomation.com/u/michael.flagler)\ **Post date:** [August 12, 2024, 10:29pm UTC](https://forum.inductiveautomation.com/t/allen-bradley-logix-driver-works-on-one-gateway-but-not-another/94562/8 "2024-08-12T22:29:43Z")
Ping is just used as a quick test to see if the network is routing packets properly. Although it's not always a good test if there's a possibility of an IP conflict and you're pinging the wrong device. How are the networks configured on the 2 gateways? Is there any VPN software that could be interfering with the communications where a network on the VPN is the same network as a local LAN? If it's not on the same network subnet, make sure the firewall/router between the networks isn't blocking/filtering traffic on port 44818 from the gateway to the PLC. ---
**Author:** ![blackdog](https://avatars.discourse-cdn.com/v4/letter/b/d26b3c/32.png) [@blackdog](https://forum.inductiveautomation.com/u/blackdog)\ **Post date:** [August 13, 2024, 7:29pm UTC](https://forum.inductiveautomation.com/t/allen-bradley-logix-driver-works-on-one-gateway-but-not-another/94562/9 "2024-08-13T19:29:16Z")
There was much confusion regarding this with our IT department but it turns out it was just a firewall rule issue. Thanks.