Wondering about the network connectivity requirements for the T7. We are using these devices inside our network but are having trouble working with them when employees are remote (home, travel, etc) and connected to the coportate environment via VPN. From what I can tell these should just be TCP devices that need line of sight to ports 502/702 and UDP 52362 on their specific IP. I am sure I am missing something because a lot of the use case examples I can find in LabJack documentation refers to jump hosts and port forwarding and what not but I am honestly confused as to why that would be needed.
Any advise is much appreciated!
.png%3Fitok=PHGBxf6M "EEV Blog Reviews LabJack T7-Pro & Software Tools")
.jpg%3Fitok=B1YcuDFK)
.png%3Fitok=Ybt-OlgU "LabJack + JEDI One Can Create a Powerful Distributed DAQ Ecosystem")
Yes, T7s should only need TCP on 502/702 and UDP on 52362 on their specific IP.
What are your remote employees trying that is failing? Are they able to ping the T7?
Port forwarding is for public internet access. If the T7 is a (Modbus TCP) server with a local (private) IP address, that local IP address is not publicly accessible from the internet. Your router has a public facing IP address though. With port forwarding, the router will use a port on that public IP and forward it to the T7's local IP.
Jump hosts exist on the local network, so they can access a T7 using its local IP. You need to run e.g. Kipling on the jump host though, not on the remote host. The remote host is on a different local network that doesn't have the T7 on it, so e.g. local broadcasts on that remote employee's local network on port 52362 will not be forwarded to the T7s local network.