Hello all,
I have an Exchange setup that I am in need of assistance with. I am trying to get RPC over HTTPS working through Outlook 2003 and Outlook 2007 I will try to give as much info without being confusing.
Here is the setup:
I have a domain registered with a registrar (let's say it is domain.org) and a web host hosting the webpage (http://www.domain.org).
The internal domain is also named domain.org and hosts
DC Server = dcsrv
File/App = filesrv
Exchange Server = mail
I have setup subdomains (glue domains) in the web host DNS to point to the static ip for the mail server (mail.domain.org). I also have reverse DNS setup with the ISP. This server also runs the RPC over HTTP service.
I have a Watchguard x55e for the router and have opened up the necessary ports for all exchange functions (or so I think). 1 to 1 NAT with Ports 443 and 25 are open to allow OWA and SMTP through and are verified working. The mail flows in and out just fine as well as OWA works fine.
I set up an internal root CA to issue the certificates which are mail.domain.org and work fine for OWA and the internal cert req. for Outlook 2007.
The filesrv also acts as a vpn server which is also a subdomain (glue domain). This is named vpn.domain.org and is also verified working. Phew, now that the background is done, I will move on to the issue.
If I am connected to the domain via VPN, Exchange works perfectly fine. You can connect right away and do your thing. If I set the Outlook client to use Exchange over https, Outlook will never find the server.
I enabled Outlook anywhere and set it to "listen" on mail.domain.org and it still will not work. I tried a few articles on this site about navigating to https://mail.domain.org/rp
Any insight on where to go from here would be great! Thanks!
This Question has been solved and asker verified All Experts Exchange premium technology solutions are available to subscription members.
Experts Exchange has been collecting answers to technology questions since 1996…3 million and counting! If you have a question, chances are we already have your answer.
If you can't find the exact answer you're looking for, ask our exclusive community of 50,000 experts. You’ll get a personalized answer from a trusted professional.
Thousands of free tech tips, tricks, how-to’s and tutorials are available in our peer reviewed articles section. See for yourself how smart our experts are, no login required.
Save solutions to your questions, answers you’ve discovered through searching plus helpful articles in your personal knowledgebase for easy future access.
Access the answers to your technology questions today.
30-day free trial. Register in 60 seconds.
Members of the expert community talk about why the experience at Experts Exchange is different than what you will find anywhere else.
Try it out and discover for yourself.
30-day free trial. Register in 60 seconds.
Join the community of experts here and help other tech pros by answering question in your area of expertise. You can earn FREE access to all Experts Exchange's premium features and resources.
A lot of your questions are already answered above.
SSL cert works fine. I installed the chain via /certsrv
OL 2007 works fine for auto discover internally. Is there a difference outside the organization? Your blog isn't linked.
RPC Proxy: Already stated
Funny thing is it works on some computers but not others. Do I have to setup exchange first then introduce HTTPS after the mailbox is set up?
Business Accounts
Answer for Membership
by: ATIGPosted on 2007-08-24 at 10:44:54ID: 19764035
what cert do you have on the CAS server?
when you do the install exchange creates a self signed certificate in IIS.
did you install the cert for yourdomain.com?
For OL 2007 you need to setup the autodiscover features to make everything work read my blog for how to do that.
if you open a web browser and type https://mail.yourdomain.co
Also, did you install the rpc proxy service on the server?