Hi all, I get in trouble by an VPN issue. Fortigate 110C 4.3-ptf12 with
two WAN connections therefore we use Policy-Route for all routings. All
works fine if the vpn' s are branch-to-branch or SSL-VPN. With
dailin-ipsec-client we can reach all resour...
Some of our user have the problem when they try to connect through our
firewall via vpn ipsec with a customer fortigate, that the connection
break after some seconds. Our firewall (tested 111C + 300C) runs on the
4.03-ptf9. Before ptf9 version there ...
I looking for a way to connect different devices to our Fortigate. For
the test i have FGT111c 4.3-7 and FGT111c 4.2-11. I can' t find a way to
get iphone and windows (with Forticlient) as dialin to one box if i use
two different dialin-interface-mod...
For me, I think there are different problems. First: In Interface-Mode
you can not ping into a ipsec dialin connection (from Fortigate to
client). I have had a call at fortigate it works under V4 but not in V5.
They give up and don' t find a way to g...
Hello all, yes we get the same problem. Since 5.0.4 I get this error.
Fortinet Support told me, they will fix it in 5.0.5. But tests show me,
they didn' t fix it. We get the error on all kind of boxes from 40C to
300C. All of our customers are affect...
I wrote under vpn that there seems to be a problem with ipsec through
the firewall. Update from 4.3.8 to 4.3.9 without problems (111C + 300C).
Ipsec-Client could connect to other Fortigates through the 4.3.9
Version, but after some seconds the connec...
Hi mEj, I' ve seen similar errors with providers who have certain ports
blocked - vodafone blocked vpn for example during start. You have to
unlock it by call. Good luck too.
Hi, first i would update to 475, in 474 you cannt run Windows-update or
a few https sides, with 475 its no problem. Its good to change and test
again. JM