 |
 | Home | Contact Us | FAQ | Search & Site Map | Link to Us |
 | Sign In | Join | Other 45 Sites in Network |
Windows Server Forum / Exchange Server / Mobility / July 2008Activesync
Sorry for the dumb question I am looking to implement activesync on Exchange 2003 I currently have OWA being fronted by a VPN appliance so I did not need to get a cert My ultimate goal would be that only activesync would be open to the world and OWA would still be required to go thru the VPN appliance Not using ISA at this time I have a verisign cert that is issued to OWA.MYDOMAIN.COM Do I have to publish this name to the public dns servers for Activesync to work. Sorry for the dumb questions but the step by step guide from MS does not address these issues. Thanks VPN appliance is not applicable here, the question is what is acting as your Firewall? You will need to open and port forward 443 to your Exchange Server. As for the Verisign cert, this should work. For the EAS domain on the WM phone you would input OWA.MYDOMAIN.COM.  SignatureJohn Oliver, Jr MCSE, MCT, CCNA Exchange MVP 2008 Microsoft Certified Partner > Sorry for the dumb question > I am looking to implement activesync on Exchange 2003 [quoted text clipped - 12 lines] > > Thanks Thanks for the quick reply The firewall is Checkpoint We were thinking about restricting access in the following virtual server locations Exadmin,Exchange,ExchWeb,OMA,Public to a specific ipaddress (SSL VPN Appliance) Then hopefully only the ActiveSync would be reachable thru 443 the rest of the sites would have to go thru the SSL VPN appliance. Thoughts? > VPN appliance is not applicable here, the question is what is acting as > your Firewall? You will need to open and port forward 443 to your [quoted text clipped - 17 lines] >> >> Thanks So are you requiring OWA to login through SSL VPN Appliance before connecting? As you stated earlier this seem the case. If so, then just open up Port 443 on your Checkpoint to your Exchange Server and you will be good to go. No need to restrict by IP the VD's. You will still be requiring SSL VPN through OWA and now EAS through SSL Cert. Curious, why have the users go through SSL VPN Appliance when they can connect securely through Checkpoint using SSL Cert on the Exchange Server? You can still get 128 bit encryption. Just curious. SignatureJohn Oliver, Jr MCSE, MCT, CCNA Exchange MVP 2008 Microsoft Certified Partner > Thanks for the quick reply > The firewall is Checkpoint [quoted text clipped - 27 lines] >>> >>> Thanks The SSL VPN is a portal to many application including OWA so it makes for one stop shopping. In addition this is a hardened appliance so you lessen the chances of having an unpatched Microsoft server with access from the internet. When you login to the SSLVPN it will pass your credentials to OWA so you get Single-Sign on My hope is that I can make it so only Activesync would be available directly from the internet via the open port on the firewall Access to OWA directly thru the firewall would not work you would have to use the SSLVPN portal > So are you requiring OWA to login through SSL VPN Appliance before > connecting? As you stated earlier this seem the case. If so, then just [quoted text clipped - 37 lines] >>>> >>>> Thanks In that case, you will have to test your procedure to see if it will work. SignatureJohn Oliver, Jr MCSE, MCT, CCNA Exchange MVP 2008 Microsoft Certified Partner > The SSL VPN is a portal to many application including OWA so it makes for > one stop shopping. In addition this is a hardened appliance so you lessen [quoted text clipped - 49 lines] >>>>> >>>>> Thanks |
Reply to this Message |
 Sign In
 Join
 My Latest Posts My Monitored Threads My Blog My Photo Gallery My Profile My Homepage Start New Thread Enable EMail Alerts Rate this Thread
|
©2008 Advenet LLC Privacy Policy - Terms of Use
This website includes both content owned or controlled by Advenet as well as content owned or controlled by third parties.