Want to protect your cyber security and still get fast solutions? Ask a secure question today.Go Premium

x
  • Status: Solved
  • Priority: Medium
  • Security: Public
  • Views: 383
  • Last Modified:

iPhone / Exchange 2003 Deployment

I've recently deployed OWA on Exchange 2003.  I have a public IP that points to my domain which hosts a webserver and my Exchange Server.  Default HTTP and SSL ports are being used for webserver access.  I configured 2 different ports (HTTP (81) & SSL (444)) for the default website on my Exchange Server.  So my OWA URL is:

https://mydomain:444/exchange

I also imported my web SSL cert on my Exchange Server.  IMAP is enabled on port 993 and I've configured Activesync on the Exchange Server.  OWA and website access are fine.  

My issue is that we are thinking of migrating from BlackBerry to iPhones.  The COO has recently purchased one and having an issue connecting to the server.  I'm trying configure it with Activesync direct push.  Firewall rules for IMAP SSL ports (993 & 143) and  iPhone SMTP port (587) have been opened.

Thanks Guys !
0
Niples
Asked:
Niples
  • 3
  • 3
1 Solution
 
MesthaCommented:
You can't use ActiveSync with alternative ports. It can only use port 80 and port 443. That is hard coded within the system and cannot be changed. Therefore if you want to use ActiveSync then you will need setup Exchange to work as it was designed.

ActiveSync does not use IMAP or SMTP, so those ports can be closed. If you are not going to use ActiveSync I would stick to Blackberry devices, preferably with a BES.

Simon.
0
 
NiplesAuthor Commented:
OK, have an update

I've configured SSL back to default port of 443.  I configured the /exchange website on the exchange server to use a cert that we received from Network Associates (*.mydomain.com) for our corporate website.  OWA works fine!

Now I receive the popup that the cert cant be verified.  I click ok to that then I receive the dreaded "Password Incorrect" popup on the iphone.  I know the password is correct and I can't get passed this point...

The other thing i failed to mention is that internally we have 2 child domains with a trust.  let just say that the exchange sits on the sub1.domain.us.

Any suggestions???
0
 
MesthaCommented:
Wildcard certificates can be a problem. I don't know if the iPhone has resolved that - it was an issue with earlier versions of ActiveSync.
Where Exchange sits doesn't really matter as long as the authentication works correctly.

Run it through the Microsoft test site with a test account.
https://testexchangeconnectivity.com/

Simon.
0
Simplify Active Directory Administration

Administration of Active Directory does not have to be hard.  Too often what should be a simple task is made more difficult than it needs to be.The solution?  Hyena from SystemTools Software.  With ease-of-use as well as powerful importing and bulk updating capabilities.

 
NiplesAuthor Commented:
I setup a test account and ran the analyzer and results showed that DNS was resolving, traffic was successfully hitting the port, but cert failed due to name mismatch.  I found this odd because the hostname resolves to the same name on the cert.

Any ideas?
0
 
NiplesAuthor Commented:
Another update,

I finally got the account to verify on the iPhone.  It appears that HTTP over RPC wasn't configured properly.  So now the account set's up and no mail or calendar comes down.  After account setup I go to mail and popup says unable to connect to server...

This is getting old!
Any more suggestions?

Thx!
0
 
MesthaCommented:
RPC over HTTPS has nothing to do with ActiveSync configuration. Therefore the fact that RPC over HTTPS wasn't working had nothing to do with it.

Can you browse to the server from the device?

Simon.
0

Featured Post

Simplify Active Directory Administration

Administration of Active Directory does not have to be hard.  Too often what should be a simple task is made more difficult than it needs to be.The solution?  Hyena from SystemTools Software.  With ease-of-use as well as powerful importing and bulk updating capabilities.

  • 3
  • 3
Tackle projects and never again get stuck behind a technical roadblock.
Join Now