@IT_Tropolis I’ve never come across an easy solution to this problem. It’s one of the reasons why I try to avoid the 192.168.x.x networks for anything to do with a corporate/office network. If they need to access Local LAN resources at the same time as being connected to the office via VPN then one of the networks IP addresses has to change, or be NATed. Maybe you can provide them a small Meraki MX/Z device for use at home (via AutoVPN) and enable VPN subnet translation, https://documentation.meraki.com/MX/Site-to-site_VPN/Using_Site-to-site_VPN_Translation. You’ll need Meraki Support to enable it. However this will most likely then cause you other issues with DNS hostname to IP address mappings. As I said, unfortunately no easy way to fix this one.
... View more
