Comments
-
Solution from support: "For the policy you created to access Ikev2-Users, can you go in the advanced tab of the policy and disable Dynamic NAT?" I did that and now it works. Thank you all.
-
Thanks for the answer. Tried that. No change. Meanwhile i opened a support case with watchguard for this issue. Will let you know the solution.
-
In fact I tried both ways. The client (connected via mobile vpn with ikev2) can ping the firewall (And any other host in the internal network from the firewall). When i try to ping the client from the firewall, that's what not working. I tried making a rule with an any packet filter from Network 192.168.200.0/24 to network…
-
Via Windows CMD from Client (10.36.10.14) to Firewall (192.168.200.254): C:\Windows\system32>ping 192.168.200.254 Ping wird ausgeführt für 192.168.200.254 mit 32 Bytes Daten: Antwort von 192.168.200.254: Bytes=32 Zeit=119ms TTL=64 Antwort von 192.168.200.254: Bytes=32 Zeit=30ms TTL=64 Antwort von 192.168.200.254: Bytes=32…
-
Thank you for your answers! The traffic is somehow blocked on the firewall. The clients answer to ping if they are in another network. Nevertheless i tried disabling the local firewall - made no difference. In the traffic monitor i get no deny messages. I tried to add a policy which enables the traffic from my internal…