IPSEC IKEv2

Forum|Forum|4 months ago
April 29, 2026
6 replies
120 views

When i use IPSEC with IKEv2 and in the forticlient I use DNS on the remote gateway then the client can connect to the VPN but can’t reach to anywhere.

If i switch using IP Address for Remote gateway then the client is able to connect to the LAN.

Anyone facing same issue with me or this is know issue for IKEv2?

funkylicious

SuperUser

to be fair i dont quite understand your problem, the way you are describing it.

are you saying that you get some DNS servers while connecting to the VPN but with those you cannot resolve anything from LAN and upon changing them with some other DNS servers you can?

"jack of all trades, master of none"

HS08Author

Contributor III

Let say my Public IP is 11.11.11.11 and the DNS name is vpn.mydomain.com.

Then on the forticlient if i use vpn.mydomain.com as remote gateway then the vpn is connected but there no any traffic (the client can’t reach to anywhere). If i use 11.11.11.11 as remote gateway then the client is able to reach to the LAN.

sjoshi

Staff

Hi @HS08

can you show below output once the vpn is connected using fqdn as remote gateway.

route print » from the pc

From FGT

diag snif packet any ‘host x.x.x.x and icmp’ 4 0 l » where x.x.x.x is the lan IP

Thanks, Salon

Toshi_Esumi

SuperUser

Do you happen to have a certificate for “vpn.mydomain.com” or a wildcard certificate “*.mydomain.com” installed and using it with the phase1-interface config like “set certificate [certificate_name]”? And more importantly, is the cert still valid, not expired?

Toshi

FortiMentor

New Member

Please try to deaktivate the IPv6 Protocol in your Network Card and in the FortiClient Network Adapter, too.

Sign up

Login with SSO

Login to the community

Login with SSO