Hello,
I'm seeing some interesting behavior with my NATR connections on FTLinx. 2 separate cases are showing the same problem:
The first NATR has a private network connected to 5 HMIs all the same make and model with all 5 being able to be pinged and all being able to be connected with VNC. However, 2 of the PVP7s show up in Linx as their 192 private address and cannot be accessed through there. The other 3 show up as their 172 with the local 192 in brackets as I'd expect.
The second case is a NATR connected to 1 PVP7 that shows the same issue, the 192 on Linx that cannot be interacted with.
As far as I can tell all of the network settings are identical across all HMIs, and the Linx driver they are in is configured to look at the 172 range only, and I'm a bit confused at this error.
I'm seeing some interesting behavior with my NATR connections on FTLinx. 2 separate cases are showing the same problem:
The first NATR has a private network connected to 5 HMIs all the same make and model with all 5 being able to be pinged and all being able to be connected with VNC. However, 2 of the PVP7s show up in Linx as their 192 private address and cannot be accessed through there. The other 3 show up as their 172 with the local 192 in brackets as I'd expect.
The second case is a NATR connected to 1 PVP7 that shows the same issue, the 192 on Linx that cannot be interacted with.
As far as I can tell all of the network settings are identical across all HMIs, and the Linx driver they are in is configured to look at the 172 range only, and I'm a bit confused at this error.
