Which prevents the 'availability' or subnets that are not available to that user on the HQ side.įor example, if you list Google on your DMZ that address to the end user appears down the tunnel, if there's no rules setup for them to access, they'll not ever make it to Google. To remedy it, create SSL routed groups, essentially defining the subnets in which are available across the tunnel which are injected into the end users PCs routing table. We've had some issues with this, where 3rd party suppliers have tried to access addresses we list on our dmz, which caused them to route down the tunnel and not get anywhere. If you do choose the Fortigate/Forticlient, just consider the use of split tunnelling. I've been trying to do some searching around, and haven't come up on anything direct, so I hoped I could just ask here quickly. Many of my users are not super technically inclined, so a simple enough solution is also important. As I understand it, there's no speed difference.

I'd rather do more work now, for a better experience for my users. I do hear that people have had some issues with the Windows 10. The client we would still probably manually configure. The Windows 10 would be simpler for us as we could configure and push out via Group Policy. I'm looking for some advice on which route to take with the FortiGate. Users are still presented with a login box, and on the back end, we have it configured were their profile must be part of a specific security group, which gives me one additional layer of security, even if it's fairly minor. We are small enough of a company that we typically just manually configure for each user. It's pretty simple, allows us to configure the client to auto launch with Windows and auto connect. With Sonicwall we've always used a client.

I'm told there's an optional vpn client, or we could go with the Windows 10 built in.

We are looking at upgrading our firewall, migrating over from a Sonicwall that's end of life.

Fortinet vpn client requirements