Split tunneling cisco anyconnect1/6/2023 Is this really a great solution and good alternative workarround for the moment? As I don't want to deploy something wrong to production, but our first tests are looking promissing. Also the Anåonnect Client will say "Split Included" in It's status for IPv6. I can connect to IPv6 Services with the Split tunnel. And when we then copied it and tested it on our POC Profile, where we normally test new Settings for our PROD VPN, it works. I found one great article ( ) which explained the exact issue we faced and a solution for it. And Most said, turning of IPv6 or maybe lowering the Priority in Windows can fix this. I've looked through a lot of articles and so on, to see if they have a solution. We are Using Split Tunnel, so only internal traffic as well as certain IP Traffic is being tunneled to the Datacenter. Our Setup looks pretty plain from the VPN Side, we have two Firewalls for our Anyconnect VPN. Internally we all just running IPv4 only. We came really quickly at a solution which seem to be turning off IPv6, which I don't really like, because who knows when we need it and also in this day an age we should be able to atleast support IPv6, besides IPv4. Over a year now we are investigating a issues where users randomly or right at the beginning connecting to our VPN are facing problems with Office/Teams.
0 Comments
Leave a Reply.AuthorWrite something about yourself. No need to be fancy, just an overview. ArchivesCategories |