![]() ![]() ) networks so that the routes of the VPN have a higher specificity, thus capturing all 192.168.1.x requests. First, we had issues with users who were in the 192.168.1.0/24 network at home due to route specificity. Users use the newest FortiClient version. It's a FortiGate 60F on v6.4.4 build 1803 (GA). This seems to happen every 10 minutes or so. A few users, however, can sometimes not resolve hostnames. For the majority of users this works without a hitch. Recently, my company migrated to a FortiGate firewall and use the newest FortiClient VPN to allow our users to connect. EDIT: Solved! Disabling IPv6 as suggested by Slushmania and Craptcha fixed the issue. ![]()
0 Comments
Leave a Reply. |
AuthorWrite something about yourself. No need to be fancy, just an overview. ArchivesCategories |