Knowledgebase: Windows Mobile 6
Windows Mobile 5/6 Device not syncing when using SSL on the Notify server
Posted by - NA - on 30 June 2009 11:41 AM

Windows Mobile 6:


When using a Windows Mobile 5 or 6 device and SSL on the NotifyLink server, the device does not work properly.  The device may receive the error: 



Unfortunately there is no current work-around for these particular Windows Mobile devices at this time.  The issue is with the .NET Framework on these devices resulting in a problem connecting to the HTTPS address of the NotifyLink server.  You could either allow connections over HTTP so the device is able to successfully sync or replace the device. This bug exists in versions 2.0 and 3.5 of the .net compact framework.  This should be fixed in version 3.5 SP1.  We do not currently have an ETA on when this will become available.  The issue that is being encountered is that the device is improperly handling certain SSL packets.  These SSL packets are legal according to the SSL specs so unfortunately, there is no workaround aside from turning off SSL on the NotifyLink server.

Turning off SSL does not necessarily mean that your information will not be secure.  AES encryption can be turned on for users.  (AES encryption is a FIPS compliant encryption algorithm). When encryption is turned on, the NotifyLink message content is encrypted in much the same way as an SSL encrypted steam.  To turn on encryption you would go into the Administrative Web Console -> Select the user in question -> Select User IT Policies -> Server Policies -> Security.  Here you would select the checkbox to "Enable encryption settings for this mailbox" and set the value to either AES or TripleDES and click "Apply Changes" to save the change.  Once this is done, the users data will be encrypted in the NotifyLink database.