TouchDown

Anyone else having issues with Touchdown not working after upgrading a Nexus 5 to Android 6.0? We've had four users in the past few days that were working fine but as soon as they upgraded to Marshmallow, Touchdown stopped working. Trying to reinstall Touchdown stops on a Server Certificate Verification screen which we can't get past.

Here is the exact error that our users are receiving:

"Handshake failed: Exception performing request ActiveSync version check returned negative, but still trying for 12.1"

Any thoughts?

Thanks!

Hi Craig,

Would you please contact us at Touchdown-support@symantec.com and we can set up logging for this issue. Thanks!

Hi, has there been any update to this?  We're experiencing the same across the board in our company.

Hi-

I have e-mailed the above address to setup logging for this issue.

Thanks!

Same issue with Nexus 6 running TD 8.5.00094 / Android 6.0.  It would nice if Symantec would confirm that there is a problem and provide an ETC for a fix.

The reason for this is not really because client is broken. What has happened is that with Android M, Google has actually made some changes to how the default network deals with certain server ciphers and protocols. Some of the ciphers have have been unsupported and some others are supported but not enabled by default. When this happens, as the client tries to connect to a server that uses a non supported or non-enabled-by-default cipher or protocol, the handshake fails. This is why some servers continue to work while some others fail. The right fix for this is to ensure that the server is actually made compliant (eg. disable sslv3, enable tls). The "workaround" fix (not the most secure one) would be to force the client to override Androids choices and at least try to enable the supported ciphers. We have a version of the app that does this, and you can get it if you write to support to see if it will fix the issue. 

regards

-g

We've found that by only allowing strong ciphers on our Sentry exchange proxies (MobileIron), that our TouchDown problem has been resolved.

We are having the same issue with a Motorola X Pure Edition.  It worked fine until one of our people updated to Marshmallow and then lost all synching of email and we are using Mobileiron already so I've sent an email to the above address.  

Our MobileIron implementation was not up to date. Once updated MobileIron server (not App/Client) to latest ver 7.xx (that includes the strong cifers), TouchDown connects and works just fine. Michael Reiser's post here helped us look in the right direction.