I exchanged forum and email with you about this on the old forum server. Our users connect remotely via the Balance 380. We used PPTP, now L2TP, with the Windows built in client. Used it for many years. I am aware of the requirement for an inbound firewall rule to permit LAN client access (the vpn client shows as a LAN device).
I needed more than 254 LAN addresses, so I changed our LAN subnet from 255.255.255.0/24 to 255.255.254.0/23. Thats when the remote user access stopped working. When a remote client connects it is assigned a DHCP address, usually the lowest number available. See the example where the client received 18.104.22.168. The Balance 380 client table shows the same IP for that remote client.
I can’t ping any LAN device from the remote client. I can’t even ping the router’s own LAN address, which is 22.214.171.124. See attached example.
Everything works if I change the LAN subnet back to 255.255.255.0/24, but then of course I don’t have enough LAN addresses. I think that proves there are no issues with the client settings. I’ve tried this on various client devices.
I stopped worrying about this because I had another device on the LAN which could serve as a PPTP server. That is an older device that can’t supply the new requirements for Windows 10 VPN client authentication, so I am back to trying to connect with the Balance.
The last time we tried this, you duplicated the settings on a device in your office and said it worked. See attached, do you see something I’m doing wrong?