We are dealing with the same issues and the reality is that FortiClient VPN is garbage. You can easily verify this by monitoring bandwidth usage on your external interfaces on the Fortigate. I don't think split tunneling is the issue here unless you are hitting bandwidth limits. Can you guys help me support the argument for implementing split-tunneling? We have carbon black in place and use SCEP. Any tips on making the case? I know his argument is going to be, "we work in finance, we're highly regulated, security comes first.". Now to convince my infrastructure engineer to do that. I expect my connection to be slower when on VPN but 60% slower seems high to me.ĭoes anybody have any ideas on where/what to look for to identify any problems or, possibly, optimize our VPN for better performance?Įdit: Marking as solved since many of you seem to agree this is split-tunneling issue. They might be getting 20 Mbps down on their phone but maybe 5-6 on the VPN connected laptop. When I connect with the affected users I see the same. For example I tested off the VPN at 40 Mbps this morning and then about 15 Mbps once I got on the VPN.
I'm half inclined to chalk these cases up to poor home internet connection but one thing that does seem to be consistent is that we are all seeing about a 60% reduction in internet speed tests when on the VPN vs.
Good morning all, we use FortiClient v 6.0.7 and we've had maybe 10% of our, now, 100% remote workforce report slowness and frequent disconnects.
0 kommentar(er)
