CoGu
asked on
Setting up an iPhone when using a 'dnsalias.org' address linking to the Exchange server
I have a client who has the front-end set as 'compayname'.dnsalias.org, which can be used to access the OWA using '/exchange'.
My problem is with getting the iPhone to synchronise with the exchange server - which seems to be related to the certificate which I have issued from the server. The certificate is self-signed (through CA on Windows Server 2003 for SBS), is a top-level root certificate and contains the principal name 'companyname'.dnsalias.org .
The iPhone itself connects through Vodafone with no problems, can access WAP, Wireless, POP3, Google Mail etc. When the Exchange account is setup (after installing the certificate profile) a message is displayed stating that the Exchange account cannot be verified. All of the user credentials are correct, and the e-mail address is valid and fully functional.
The server is running Exchange 2003 (SP2), which does support PUSH and all of the required settings and forwards are in place.
Any ideas?
My problem is with getting the iPhone to synchronise with the exchange server - which seems to be related to the certificate which I have issued from the server. The certificate is self-signed (through CA on Windows Server 2003 for SBS), is a top-level root certificate and contains the principal name 'companyname'.dnsalias.org
The iPhone itself connects through Vodafone with no problems, can access WAP, Wireless, POP3, Google Mail etc. When the Exchange account is setup (after installing the certificate profile) a message is displayed stating that the Exchange account cannot be verified. All of the user credentials are correct, and the e-mail address is valid and fully functional.
The server is running Exchange 2003 (SP2), which does support PUSH and all of the required settings and forwards are in place.
Any ideas?
ASKER
Thank you for reply, but I do not believe the problem is with the certificate being self-signed - I have setup several iPhones on similar setups and they have worked flawlessly.
My main suspicion revolves around the 'companyname'.dnsalias.org setup (which was implemented by the previous IT company) and how this relates the issuing server on the certificate. I have set the fully qualified name of the server and tried the full 'companyname'.dnsalias.org name, but neither of these two arrangements allow the iPhone to synchronise.
My main suspicion revolves around the 'companyname'.dnsalias.org
Is this company using dnsalias as they have no fixed ip?
Adam
Adam
ASKER
The company does have a static IP, I believe that this service was used to simplify the connection to Remote Web Workplace etc. I personally would remove this service and setup an A record on their external DNS, but no one in the company or the previous IT company have the login details for the DNSAlias account.
ASKER CERTIFIED SOLUTION
membership
This solution is only available to members.
To access this solution, you must be a member of Experts Exchange.
ASKER
Thank you for your response, I did this in-line with a couple of other changes and everything works!
no worries, gald your sorted!
Did you use self signed cert or was it a trusted one?
Adam
Did you use self signed cert or was it a trusted one?
Adam
These can be purchased inexpensively if you look at the likes of http://www.instantssl.com or http://www.godaddy.com
Adam