Reply
Thread Tools
Posts: 182 | Thanked: 40 times | Joined on Apr 2010
#1
Hi

I have a problem with the N900 that I hope you guys can help me with. I've put this in the giant MfE thread, but it didn't elicit any responses - so hopefully a separate thread can.

So this is the setup: I have a personal Exchange account on a server running at home I'd like to sync on the N900. I sync work Exchange accounts on other phones and ideally, I'd like the Nokia to do my personal. If necessary I'll swap this around, and I suppose the problems are resulting from my cheapskating - but maybe there's a way around it, I hope.

So, I have an Exchange (2007) server. It's self-signed with the domain foo.com (example, of course). However, it's behind a dynamic DNS account. So I have a dyndns account, foo.dyndns.com. Now that didn't fully work out, so since I have control of the domain foo.com, I CNAME'd remote.foo.com -> foo.dyndns.com

So now, going to remote.foo.com successfully directs me to foo.dyndns.com and to my Exchange server. And via the Maemo web browser, I can do webmails fine - I still get the certificate error, but I can add the exception. Other smartphones with Exchange clients work fine - the N900 is the only one which doesn't so far.

I installed the .pfx certificate from the Exchange server onto my N900, but that didn't work. What else could I try (apart from paying for an SSL cert thru DynDNS)?
 
Posts: 3,617 | Thanked: 2,412 times | Joined on Nov 2009 @ Cambridge, UK
#2
Originally Posted by punto View Post
Hi

I have a problem with the N900 that I hope you guys can help me with. I've put this in the giant MfE thread, but it didn't elicit any responses - so hopefully a separate thread can.

So this is the setup: I have a personal Exchange account on a server running at home I'd like to sync on the N900. I sync work Exchange accounts on other phones and ideally, I'd like the Nokia to do my personal. If necessary I'll swap this around, and I suppose the problems are resulting from my cheapskating - but maybe there's a way around it, I hope.

So, I have an Exchange (2007) server. It's self-signed with the domain foo.com (example, of course). However, it's behind a dynamic DNS account. So I have a dyndns account, foo.dyndns.com. Now that didn't fully work out, so since I have control of the domain foo.com, I CNAME'd remote.foo.com -> foo.dyndns.com

So now, going to remote.foo.com successfully directs me to foo.dyndns.com and to my Exchange server. And via the Maemo web browser, I can do webmails fine - I still get the certificate error, but I can add the exception. Other smartphones with Exchange clients work fine - the N900 is the only one which doesn't so far.

I installed the .pfx certificate from the Exchange server onto my N900, but that didn't work. What else could I try (apart from paying for an SSL cert thru DynDNS)?
Is your self-signed certificate a CA certificate? If not, you won't be able to import it on the N900, and it won't work with MfE.
 
Posts: 376 | Thanked: 56 times | Joined on Jan 2010
#3
Robin my problem with the certs was sorted in the end by making the cert at work have the CA from the ISA box

But the problem I have is that it *only* works when I am connected to the works wireless (ie on the works LAN) it will not work at all via any other net connection (3g, home internet etc)
 
Posts: 182 | Thanked: 40 times | Joined on Apr 2010
#4
Originally Posted by Rob1n View Post
Is your self-signed certificate a CA certificate? If not, you won't be able to import it on the N900, and it won't work with MfE.
Sorry - I should have been clearer about 'didn't work'. I meant it didn't make any difference to the non-function of MfE.

I did manage to import it into the N900. Now in the Certificate manager it shows remote.foo.com for Server and Email after I imported the cert for those roles.
 
Posts: 3,617 | Thanked: 2,412 times | Joined on Nov 2009 @ Cambridge, UK
#5
Originally Posted by punto View Post
Sorry - I should have been clearer about 'didn't work'. I meant it didn't make any difference to the non-function of MfE.

I did manage to import it into the N900. Now in the Certificate manager it shows remote.foo.com for Server and Email after I imported the cert for those roles.
Ah, okay. Have you looked at http://wiki.maemo.org/Mail_For_Excha...rtbeat_and_FAQ - there's some certificate debugging steps towards the bottom. There's also instructions for enabling debugging, which should help to indicate where the error is coming from. You could also check the web server logs on the Exchange server to see what responses the client is getting.
 

The Following User Says Thank You to Rob1n For This Useful Post:
Posts: 182 | Thanked: 40 times | Joined on Apr 2010
#6
OK - well I'm getting an error not specified in the guide: Verification failed: unable to get local issuer certificate
 
Posts: 3,617 | Thanked: 2,412 times | Joined on Nov 2009 @ Cambridge, UK
#7
Originally Posted by punto View Post
OK - well I'm getting an error not specified in the guide: Verification failed: unable to get local issuer certificate
Did you run the latter part - dumping out the retrieved certificate? If so, could you post the openssl output (there shouldn't be anything private in there).
 
Reply

Thread Tools

 
Forum Jump


All times are GMT. The time now is 00:10.