iMate JASJAM-Direct Push no longer works

Forums › Legacy mobile platforms (Windows Mobile, Palm OS, Web OS, Symbian, Meego, Blackberry) › iMate JASJAM-Direct Push no longer works

gskilleter

3 posts

Wannabe Geek

#13011 18-Apr-2007 11:12

iMate announced a software upgrade for JASJAM smarrtphones on the Telstra (Australia) GPRS/3G network. Prior to installing this software upgrade, my JASJAM worked fine - it did everything it was meant to, including Direct Push to my work Microsoft Exchange Server. After the software upgrade, I lost all capacity to connect to the Exchange, over the phone network or via Active Synch to my PC. I finally managed to make a connection to the Exchange Server using Active Sync after I manually installed a series of SSL certificates as root certificates on thhe phone and re-booting it. I still cannot make a connection over the phone network and Direcet Push is not working.

The phone attempts to make the connection, the GPRS network connection is activated and a message indicates that the Exchange is "synchronising folders". Eventually, it logs off, without making the connection. A message on the screen indicates it is "Waiting for the Server" and the Status messages is 0x80072EFD (The server could not be reached). This is the same message I was receiving when trying to connect via Active Sync directly to the PC and which was solved through installation of the security certificates. It has not solved the problemm for Direct Push though.

HELP! Anny suggestions. The technical support line for iMate is to an overseas call centre and their operators do not seem to have ANY idea about what they are doing - one told me the JASJAM was nopt capable of connecting to an Exchange Server.

Thanks,
Greg

freitasm

BDFL - Memuneh
80646 posts

Uber Geek
+1 received by user: 41030

Administrator

ID Verified

Trusted

Geekzone

Lifetime subscriber

#67495 18-Apr-2007 11:18

Welcome to Geekzone... Some suggestions:

1.Make sure you have the correct Root Certificate for your server, if it's not a public one (Self Signed Certificates)
2.Make sure the server name in use is the same one for which the certificate was issued
3.Make sure your Smartphone can actually connect to the Internet, by accesing other servers
4.Try connecting to the Exchange Server with the SSL option turned off on your phone (if it works it can be a problem with your certificate configuration)
5.Enable logging on your Smartphne and see if you noticed any strange message in the log
6.Try accessing the /OWA from your PC and from your Smartphone (/OMA)
6.Ask the Exchange Administrator if the settings for your user are correct and allow user initiated synchronisation
7.Ask the Exchange Administrator if port 443 is not blocked in the firewall

These are just some start points and most likely the culprit is one of these...

Referral links: Quic Broadband (free setup code: R587125ERQ6VE) | Samsung | AliExpress | Wise | Sharesies

Support Geekzone by subscribing (browse ads-free), or making a one-off or recurring donation through PressPatron.

gskilleter

3 posts

Wannabe Geek

#67552 18-Apr-2007 15:04

Thanks for all the suggestions:

1.Make sure you have the correct Root Certificate for your server, if it's not a public one (Self Signed Certificates)
2.Make sure the server name in use is the same one for which the certificate was issued
3.Make sure your Smartphone can actually connect to the Internet, by accesing other servers
4.Try connecting to the Exchange Server with the SSL option turned off on your phone (if it works it can be a problem with your certificate configuration)
5.Enable logging on your Smartphne and see if you noticed any strange message in the log
6.Try accessing the /OWA from your PC and from your Smartphone (/OMA)
6.Ask the Exchange Administrator if the settings for your user are correct and allow user initiated synchronisation
7.Ask the Exchange Administrator if port 443 is not blocked in the firewall

(1) I have installed all the root certificates that seem appropriate, based on the following procedure:

Log onto web outlook via a secure https:// connection.
Clicking on the “lock” icon located next to the address bar and select “View Certificates”
Select the “details” TAB
Select “Copy to file…”
Follow the steps in the certificate export wizard selecting “Base-64 encoded X.509 (.CER)
Select a filename location
Copy to the phone then run the Certificate installer

One thing I noted though, was that the address for the Outlook Web Access was https:exchange.uq.edu/au/exchange, whereas the actual exchange server setting I use for Outlook and access via Activew Sync is uqexmb1.uq.edu.au. I am trying to find out if there is an additional root certificate associated with the latter that I need to install. The certificate that is installed is for access to *.uq.edu.au, so I assumed the * was a wild card allowing access to all uq servers. If this is not the case then your point 2 might explain the situation, but I do not know how to solve this. When I first got the phone, this was not a problem - I only lost Direct Push access after installing the iMate software upgrade.

(3) There is no problem accessing the internet and I can also download email from a pop server and IMAP account without any problems.
(4) I have SSL switched off and this does help. If I have it switched on, I just get a different error message
(6) I have NO problem accessing OWA from the PC or OMA from the smartphone - I can see all my mail from OMA, although the interface is not very good so it is not a solution for actually reading the mail.

(7-8) I am waiting to hear back from our Exchange Administrator BUT given thge Direct Push worked on Monday, prior to the software upgrade, I have no reason to believe that these settings might have been changed.

Thanks again though.

Greg

gskilleter

3 posts

Wannabe Geek

#67570 18-Apr-2007 16:50

Thanks very much for the help. Problem solved. There was yet one more certificate that I had not associated with the Exchange server but seemed to be needed in order to access the system. Not sure why this had to be manually installed, but at least it is now all fixed. Any other users of the JasJam on Telstra (Australia), be wary of installing the software upgrade unless you really need it.

Regards,
Greg