FortiClient connected but no network

Forum|Forum|8 years ago
January 31, 2018
6 replies
22069 views

Hi,

I have a user that connects to my FortiGate 110C.

he uses the latest Forticlient.

What happens is that the client is connected. I can see it is connected, yet the "Bytes Received" is not updating. looks like a false connection or no connection coming through.

I removed the latest forti client and installed an old version vpn-ssl, but it get disconnected almost immidiatly.

Need your help here.

Thanks,

Michael

WhatsApp Image 201__-16 at 12_22_04.jpg

SteveG

New Member

I've seen this on IPSec VPN's when the users home router is dropping IPSec or they haven't enable IPSec pass through on their router. Using SSL gets around this but sounds like something isn't quite right with the SSL config if the session is dropping straightaway.

Nancy_Kivlen

New Member

My problem is that forticlient can't connect with the VPN error message -20900. how do I fix that?

SteveG

New Member

Are you talking IPSec or SSL? The way I tackle IPSec VPN connectivity issues is:

Run a capture on the Fortigate on the WAN interface filtering on the external IP of the FortiClient. You should see protocol 50 (if using IPSec) while IKE is being established, once Phase 1 is up you'll then see UDP 4500 which is actually the encrypted payload (Phase 2). So for instance if you generate a ping form the client PC to something at the other end of the VPN you'll see a packet using UDP 4500 from the FortiClient to the FortiGate, then the return traffic from the FortiGate to the external IP of the Forticlient. In this instance if you don't see UDP 4500 from the Client to the Gate then the local device is filtering IPSec traffic.

Sign up

Login with SSO

Login to the community

Login with SSO