?
Solved

RPC HTTPS FQDN Help!

Posted on 2006-11-27
7
Medium Priority
?
1,699 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
[X]
Welcome to Experts Exchange

Add your voice to the tech community where 5M+ people just like you are talking about what matters.

  • Help others & share knowledge
  • Earn cash & points
  • Learn & ask questions
  • 3
  • 3
7 Comments
 
LVL 16

Expert Comment

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

Expert Comment

by:Sembee
ID: 18020768
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
ID: 18021164
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
Industry Leaders: We Want Your Opinion!

We value your feedback.

Take our survey and automatically be enter to win anyone of the following:
Yeti Cooler, Amazon eGift Card, and Movie eGift Card!

 
LVL 104

Accepted Solution

by:
Sembee earned 2000 total points
ID: 18021261
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
ID: 18021312
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
ID: 18021444
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
ID: 18021621
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

Problems using Powershell and Active Directory?

Managing Active Directory does not always have to be complicated.  If you are spending more time trying instead of doing, then it's time to look at something else. For nearly 20 years, AD admins around the world have used one tool for day-to-day AD management: Hyena. Discover why

Question has a verified solution.

If you are experiencing a similar issue, please ask a related question

After hours on line I found a solution which pointed to the inherited Active Directory permissions . You have to give/allow permissions to the "Exchange trusted subsystem" for the user in the Active Directory...
Unified and professional email signatures help maintain a consistent company brand image to the outside world. This article shows how to create an email signature in Exchange Server 2010 using a transport rule and how to overcome native limitations …
In this video we show how to create an Address List 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 Organization >> Ad…
This video shows how to quickly and easily add an email signature for all users on Exchange 2016. The resulting signature is applied on a server level by Exchange Online. The email signature template has been downloaded from: www.mail-signatures…
Suggested Courses

777 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