I work with some engineering guys and they honestly don't know much about IPs and networking. I've told them for years they should be using some VLAN and/or Layer 3 switching out in the field.
They typically have two networks:
#1 - 192.168.0.x/24 (internet access over a USB-A network adapter). This is a hardware device (CradlePoint) that provides AT&T/Verizon access. This device is setup as DHCP and provides IPs that are physically connected.
#2 - 10.0.0.x/24 (built in LAN). This is what they use for communicating with the PLC, etc.
GoToMyPC is used to access the PC over the internet (in through the CradlePoint via 192.168.0.x/24).
Recently they've asked me how to add an additional USB-A ethernet adapter for communicating with a piece of equipment on 192.168.250.x/24.
I received a call earlier that GoToMyPC was not always able to connect and that they also couldn't communicate with the equipment on the 192.168.250.x network.
Wouldn't this be best setup long-term with a Layer 3 switch and clearly defined routes? What would you do?
They typically have two networks:
#1 - 192.168.0.x/24 (internet access over a USB-A network adapter). This is a hardware device (CradlePoint) that provides AT&T/Verizon access. This device is setup as DHCP and provides IPs that are physically connected.
#2 - 10.0.0.x/24 (built in LAN). This is what they use for communicating with the PLC, etc.
GoToMyPC is used to access the PC over the internet (in through the CradlePoint via 192.168.0.x/24).
Recently they've asked me how to add an additional USB-A ethernet adapter for communicating with a piece of equipment on 192.168.250.x/24.
I received a call earlier that GoToMyPC was not always able to connect and that they also couldn't communicate with the equipment on the 192.168.250.x network.
Wouldn't this be best setup long-term with a Layer 3 switch and clearly defined routes? What would you do?

