The only caveat seems to be that the users do not get their full bandwidth when ZCC is up&running. After the new policy was applied to the clients everything instantly worked. Although this is a fallback option for DTLS it seems it never fell back to TLS automatically, maybe because it worked for initialization of ZCC. Via some extra work and asking users about their providers we found that all these users had one thing in common in their homeoffices: a Vodafone Cable Broadband Internet Access (via Coax).Īs one of the differences between ZTunnel 1.0 and 2.0 is usage of TCP vs UDP (by default DTLS) we forced this users via fwd-profile settings to use TLS. But as we do not want to use ZTunnel 1.0 anymore I found no peace Since we found no salvation in configuring all possible profiles-settings we switched back to ZTunnel 1.0, what immediatly solved the issue. Just solved one issue which haunted us last week: we had 3 (homeoffice) users having trouble connecting to ZPA, Sharepoint Online, sometimes Outlook just disconnected and various unspecific laggy performance when ZCC was in place.
0 kommentar(er)
