# V8.0.5 LogixDriver v32.016 ReconnectWait **URL:** \ **Category:** General Discussion\ **Tags:** ignition80\ **Created:** [February 7, 2024, 7:17pm UTC](https://forum.inductiveautomation.com/t/v8-0-5-logixdriver-v32-016-reconnectwait/85400 "2024-02-07T19:17:31Z")\ **Posts on this page:** 13\ **Page:** 1
**Author:** ![fivecents](https://avatars.discourse-cdn.com/v4/letter/f/d9b06d/32.png) [@fivecents](https://forum.inductiveautomation.com/u/fivecents)\ **Post date:** [February 7, 2024, 7:17pm UTC](https://forum.inductiveautomation.com/t/v8-0-5-logixdriver-v32-016-reconnectwait/85400/1 "2024-02-07T19:17:31Z")
A new compactlogix v32.016 device status in Ignition only shows as reconnect wait. From server that ignition is running on we can ping and show status page via webbrowser. Ignition Logs don't appear to show anything related to logixdriver. Does anyone have idea with how to proceed on determining what issue is? Someday we may like to update ignition version but today isn't that day. ---
**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:** [February 7, 2024, 7:25pm UTC](https://forum.inductiveautomation.com/t/v8-0-5-logixdriver-v32-016-reconnectwait/85400/2 "2024-02-07T19:25:57Z")
Have you tried disabling and re-enabling the device in Ignition? Do you get any log entries then? Have you tried running a wireshark capture (with capture filter for the target IP) while re-enabling the Ignition device? Share the pcap here if so. ---
**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:** [February 7, 2024, 7:51pm UTC](https://forum.inductiveautomation.com/t/v8-0-5-logixdriver-v32-016-reconnectwait/85400/4 "2024-02-07T19:51:37Z")
There's no actual traffic in that capture, just TCP/IP overhead. Are you running Wireshark on the gateway? (Required.) Follow this procedure: - Disable the device connection. - Start wireshark, using a capture filter of "tcp and host w.x.y.z", where w.x.y.z is the IP address of the PLC. - Enable the device connection. - Keep collecting packets for a couple minutes. - Disable the device connection. - Save and post the PCAP file. ---
**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:** [February 7, 2024, 10:03pm UTC](https://forum.inductiveautomation.com/t/v8-0-5-logixdriver-v32-016-reconnectwait/85400/5 "2024-02-07T22:03:54Z")
Make sure when you create the connection you're only changing the name of the device and the IP address (Hostname) and leave the rest at defaults. (Although I usually bump up the CIP Connection Size under advanced options to 4000 also.) The only other item you may possibly need to change would be the local address, but this rare. ---
**Author:** ![fivecents](https://avatars.discourse-cdn.com/v4/letter/f/d9b06d/32.png) [@fivecents](https://forum.inductiveautomation.com/u/fivecents)\ **Post date:** [April 30, 2024, 6:24pm UTC](https://forum.inductiveautomation.com/t/v8-0-5-logixdriver-v32-016-reconnectwait/85400/6 "2024-04-30T18:24:52Z")
Workaround was to share data with another controller that gateway driver connects with. Wireshark installed on same machine as gateway isn't practical now. Wireshark on different machine info in green when webserver accessed(success), red and black when using rslinx ![RslinxFail](https://us1.discourse-cdn.com/inductiveautomation/original/3X/e/0/e03097c3c0dc6f89b4b50dbba63097c8d02ec95b.png) ![PowershellTncwithrslinxPort](https://us1.discourse-cdn.com/inductiveautomation/original/3X/0/d/0de0e632ce4348316e5aa0997f26db2b907f9cdc.png) ---
**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:** [April 30, 2024, 7:06pm UTC](https://forum.inductiveautomation.com/t/v8-0-5-logixdriver-v32-016-reconnectwait/85400/7 "2024-04-30T19:06:47Z")
Are you asking a question? Looks like RSLinx cannot connect to that PLC either. But not entirely clear. > [@fivecents](#): > > Wireshark installed on same machine as gateway isn't practical now. Then it isn't going to be practical to help you. Unless you have IT support that can do wireshark through a switch's port mirroring or native capture technology. We need to see the capture between the Ignition gateway and the target PLC. (And not just screen shots. Post the PCAP when you have it.) ---
**Author:** ![fivecents](https://avatars.discourse-cdn.com/v4/letter/f/d9b06d/32.png) [@fivecents](https://forum.inductiveautomation.com/u/fivecents)\ **Post date:** [April 30, 2024, 7:20pm UTC](https://forum.inductiveautomation.com/t/v8-0-5-logixdriver-v32-016-reconnectwait/85400/8 "2024-04-30T19:20:06Z")
No not another question. Rslinx connection to plc broken also. Added wireshark images with the idea that possibly relevant to solution as I don't know what I don't know. ---
**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:** [April 30, 2024, 7:32pm UTC](https://forum.inductiveautomation.com/t/v8-0-5-logixdriver-v32-016-reconnectwait/85400/9 "2024-04-30T19:32:17Z")
I'd say your IT is blocking your connections. ---
**Author:** ![fivecents](https://avatars.discourse-cdn.com/v4/letter/f/d9b06d/32.png) [@fivecents](https://forum.inductiveautomation.com/u/fivecents)\ **Post date:** [May 2, 2024, 2:37pm UTC](https://forum.inductiveautomation.com/t/v8-0-5-logixdriver-v32-016-reconnectwait/85400/10 "2024-05-02T14:37:17Z")
[050224.pcapng](https://forum.inductiveautomation.com/uploads/short-url/wrdbpYAnMLufaODYkfN85eDkhqB.pcapng) (1.7 KB) Uploaded wireshark file running on gateway, filter "tcp and host w.x.y.z" Device connection disabled, enabled 2 minutes then disabled. ---
**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:** [May 2, 2024, 2:41pm UTC](https://forum.inductiveautomation.com/t/v8-0-5-logixdriver-v32-016-reconnectwait/85400/11 "2024-05-02T14:41:56Z")
Yup, connections blocked. The capture is nothing but single packets trying to open a connection. No responses at all. ---
**Author:** ![fivecents](https://avatars.discourse-cdn.com/v4/letter/f/d9b06d/32.png) [@fivecents](https://forum.inductiveautomation.com/u/fivecents)\ **Post date:** [May 3, 2024, 11:49am UTC](https://forum.inductiveautomation.com/t/v8-0-5-logixdriver-v32-016-reconnectwait/85400/12 "2024-05-03T11:49:06Z")
Is there anything indicating that this connection is blocked versus powered down or unplugged from network? That doesn't seem to be true because ping and webserver connect but just for further understanding. ---
**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:** [May 3, 2024, 11:54am UTC](https://forum.inductiveautomation.com/t/v8-0-5-logixdriver-v32-016-reconnectwait/85400/13 "2024-05-03T11:54:53Z")
> [@fivecents](#): > > because ping and webserver Ping is a different protocol entirely, and webserver uses a different TCP port. That those work and EtherNet/IP doesn't is _ **extremely strong evidence** _ of firewall blockage. ---
**Author:** ![fivecents](https://avatars.discourse-cdn.com/v4/letter/f/d9b06d/32.png) [@fivecents](https://forum.inductiveautomation.com/u/fivecents)\ **Post date:** [May 3, 2024, 5:16pm UTC](https://forum.inductiveautomation.com/t/v8-0-5-logixdriver-v32-016-reconnectwait/85400/14 "2024-05-03T17:16:02Z")
We resolved. OEM NAT on LAN side had IP and Gateway set the same. We set LAN Gateway to 0.0.0.0 power cycled and Ignition driver good to go.