Experiencing a "classic" reconnect wait loop on this device, followed advice from prior topics on the matter but IT is claiming there is no IP Address confliction or firewall issue. Can something else cause this or are they perhaps just wrong.
Wireshark will tell you which is the case.
will install it and give it a try, thank you.
How am I supposed to use wireshark in this instance? Starting it with a filter for that possibly conflicted address then ping said address in command prompt or some other way?
Yes, use a capture filter to only include traffic to/from that device's IP address. Typically in this format:
host 1.2.3.4
Do not use ping. Just watch Ignition make several reconnect attempts. Then stop wireshark, save the file, and post it here.
It will very likely have TCP SYN packets from Ignition, with retransmits, with no responses from that device. Show that to your IT group as proof it is their problem, not yours.
Not sure why but after saving it it seems to vanish from my documents for selection, but it is still there if I go to save another capture.
?
No idea. Overly-aggressive anti-virus?
Yeah I'm not really sure what's going on with that, however I think the wireshark may not be necessary as I can't even ping to that IP address, so maybe it is a physical issue at the point of connection?
Is there something I could just screenshot of the capture while it is still in wireshark?
attempt4atcapture.pcapng (2.6 KB)
Yeah, no connection whatsoever.
Also, your gateway thinks it is on the same subnet with 10.13.130.122. If that isn't true, then IT has screwed up your server's routing table and/or VLANs.
To my knowledge it is actually on the same subnet so I think that's fine, I'll need to investigate the plc physically and see what's going on I suppose. But just to confirm there are no signs of an IP conflict, just total lack of connectivity?
Yes.
Was Wireshark installed and this capture made on the same computer running the Ignition Gateway?
Was my understanding it runs through web browser? If you mean did I have the gateway open at the time then yes.
No, that's not what I'm talking about.
The Ignition Gateway, the actual application, is installed on a computer or server somewhere. If you didn't install Wireshark on, and run the capture from that server, then it's not a useful capture.
1 Like
In that case it is not at all a useful capture, the gateway proper is installed on a server I don't have access to. However, based off an inability to even ping or access the IP in browser I think my problem is a physical connectivity one, that or IT needs to figure it out themselves haha.