Aaarrrgggh wrote:
I guess my concern or question is what exactly are you trying to do on the remote sites? Are you managing the network for your clients, or managing PCs for a client, or managing a subset of a network or PCs at a client?
Are you intending for the ER-X at client sites to be their primary internet gateway, or some kind of unit of segregation from a larger LAN?
My DNS comment was just that you can make entries for client1, client2, etc in DNS so you don't have to do everything by IP.
I'm managing IoT style devices that are sitting on their own network. There aren't any PCs involved.
The ERX will not be the primary internet gateway. It's going to be sitting behind an existing network infrastructure and will be part of a segmented piece of that LAN. All I need is the ability to connect to a site so I can use the licensed, proprietary software on my laptop to manage those devices.
