@NolanHerring    Thank you very much for the clarifications.   ... View more

@daniel_bostock  @JainD21  @BrechtSchamp    Hello guys! IP 192.168.20.1 is on MX and there are no specific Firewall rules configured on MX.     As you reinforced to check the firewall rules in Windows, today I revised the rules again and discovered the problem.   The client that was on the Corporate network (192.168.20.65), was running a kaspersky antivirus and was blocking ICMP and RDP, we made the antivirus adjustments on packet rules and now everything is working as expected.     @PaulCoad    I hope you can solve it too!   Guys, thank you for your help! ... View more

I have a similar problem! The VPN client (Windows 10) successfully connects and receives IP 192.168.100.97 from subnet 192.168.100.0/24, but this VPN client does not ping devices from the Corporate network from subnet 192.168.20.0/24, but the reverse works.   192.168.100.97 (VPN) -> 192.168.20.0/24 (CORP) - NOK PING 192.168.100.97 (VPN) -> 192.168.20.1 (CORP) - OK PING 192.168.20.0/24 (CORP) -> 192.168.100.97 (VPN) - OK PING   The VPN client (192.168.100.97) can only reach the gateway 192.168.20.1 (CORP).   I already disabled Windows firewall and VPN client antivirus.   Do I need to configure any routes? I can not identify the fault. ... View more