Solved

RPC HTTPS FQDN Help!

Posted on 2006-11-27
7
1,687 Views
Last Modified: 2008-02-01
What we are attempting to achieve is to have OUTLOOK users connect to Exchange using RPC and HTTPS.

Setup:

Exchange SP1

What is done so far from http://www.petri.co.il/configure_rpc_over_https_on_a_single_server.htm

1.      I installed the RPC component on EXCHANGE SP1 and I see RPC and RPCWITHCERT under IIS.

2.      When I browse the RPC virtual directory, it prompted me for a login 3 times and afterwards returns back a HTTP 401.3 Error. This is normal?

3.      A SSL cert is installed from VERISIGN and it is working perfectly for OWA at https://mail.domain.com internally and extenrally

4.      I used  RPCNoFrontEnd from http://www.petri.co.il/configure_rpc_over_https_on_a_single_server.htm to changed the ports.

Questions:

What is my FQDN?

When I ipconfig/all it is ex.internal.local

My OWA is https://mail.domain.com

What should I put in OUTLOOK to connect thru HTTPS?

Or Am i missing something else?

Thanks in advance!

0
Comment
Question by:ethanfox
  • 3
  • 3
7 Comments
 
LVL 16

Expert Comment

by:poweruser32
Comment Utility
it should be mail.domain.com -the name that it is known as on the internet
0
 
LVL 104

Expert Comment

by:Sembee
Comment Utility
Any reason you are not on Exchange 2003 SP2?
Do you meet the requirements for RPC over HTTPS?

Exchange 2003 on Windows 2003
Domain is at least mixed Windows 2003 with at least one Windows 2003 DC/GC.
Have you made the registry change on the domain controller as well?

The error on the virtual directory is normal. It is used to test for certificate prompts. If you get a certificate prompt then the feature will not work.

The FQDN is what your certificate is issued to. If your certificate is mail.domain.com then that is what you put in to Outlook.

Simon.
0
 

Author Comment

by:ethanfox
Comment Utility
Yes, I'm Sorry...I am on Exchange SP2

Should I install the RPC component on the DC as well?

How should I test afterward? RPCPING from a client computer?

Thanks!
0
Free Trending Threat Insights Every Day

Enhance your security with threat intelligence from the web. Get trending threat insights on hackers, exploits, and suspicious IP addresses delivered to your inbox with our free Cyber Daily.

 
LVL 104

Accepted Solution

by:
Sembee earned 500 total points
Comment Utility
You do not need the RPC component on the domain controller. However if this is a single Exchange server deployment then you do need to make a single registry change on the DC for the feature to work.

I don't bother with any other testing apart from browsing to the virtual directory. The feature either works or it doesn't. Once I have made the registry changes, I simply adjust the Outlook client. Take a client configured in the usual way and test. Once you know Outlook is working, add the additional settings that RPC over HTTPS requires. Do not change your usual settings - just add. Then test again, using the rpcdiag switch on Outlook to confirm if the feature is working or not.

Simon.
0
 

Author Comment

by:ethanfox
Comment Utility
Yes!

I did the Registry change on the DC. Tested with outlook.exe /rpcdiag and im connecting thru HTTPS now.

Thanks for the quick response Simon!

0
 

Author Comment

by:ethanfox
Comment Utility
How do connect thru TCP/IP when I'm internal now?

Or should I leave it to connect thru HTTPS internal and external?

Thanks again!
0
 
LVL 104

Expert Comment

by:Sembee
Comment Utility
I always set RPC over HTTPS to work with HTTPS whether inside or outside. The users can come and go as required and it has no impact on the performance of Exchange or Outlook.

Simon.
0

Featured Post

Highfive Gives IT Their Time Back

Highfive is so simple that setting up every meeting room takes just minutes and every employee will be able to start or join a call from any room with ease. Never be called into a meeting just to get it started again. This is how video conferencing should work!

Join & Write a Comment

Check out this infographic on what you need to make a good email signature that will work perfectly for your organization.
Exchange server is not supported in any cloud-hosted platform (other than Azure with Azure Premium Storage).
In this video we show how to create a Distribution Group in Exchange 2013. We show this process by using the Exchange Admin Center. Log into Exchange Admin Center.: First we need to log into the Exchange Admin Center. Navigate to the Recipients >>…
This video discusses moving either the default database or any database to a new volume.

743 members asked questions and received personalized solutions in the past 7 days.

Join the community of 500,000 technology professionals and ask your questions.

Join & Ask a Question

Need Help in Real-Time?

Connect with top rated Experts

21 Experts available now in Live!

Get 1:1 Help Now