ClientConnector v3.1.0.88 - Stays on Tunnel v1.0

All,

We have used several versions of Windows Client Connector - using Tunnel v2 - without problems for a long time. I’m obviously testing new Windows Client Connector release v3.1.0.88. But this new version stays on Tunnel v1.0 so can’t be deployed. I can’t figure out why it stays on Tunnel v1.0 while App Profile Policy is unchanged and it dictate; use Tunnel v2.

Does anyone experience the same issue, and have you found a solution for it?

Thanks,
/Jesper

I’m running v2.0 - DTLS without any issues.

Case 02649487 submitted to find root cause.

Thanks,
/Jesper

Zscaler Support Tech has filed a bug, so something is not right.

Also running Z-Tunnel 2.0 with DTLS here. No issues so far.

Zscaler Support came back to me asking if issue has disappeared, and yes, now test clients show “v2.0 - DTLS” and work as expected. Lovely.

Thanks,
/Jesper

Zscaler Support has informed me that this was caused by an expired certificate on public Node in Copenhagen.

Over & Out,
/Jesper