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: 270
  • Last Modified:

RCP over HTTPS problems

I have read several articles on rcp over https and it look as though I'm not the only one having diffculty and I have reached a point where my lack of technical knowledge can't bridge the gap between these articles and this project.

I have followed the instructions prescribed these articles and I can't seem to get the url https://<servername>/rpc to ask for credentials - not even while performed at the server.
http://support.microsoft.com/default.aspx?kbid=833401 
http://www.amset.info/exchange/rpc-http.asp

I can't help but to think that it has something to do with the CA or Server Certificates - I haven't found any how-to's that show you how to configure these components specifically for rcp over https, not to mention, this is my first experience using Certificates.

My System
Single server install with Server 2003 Enterprise and Exchange 2003 and it's the only server in the domain.

Any help will be greatly appreciated.

Thanks

0
phytomer
Asked:
phytomer
1 Solution
 
map000Commented:
have you installed a CA server?
0
 
SembeeCommented:
Lets go right back to the beginning. As the author of the second web site, I tend to pick up most of the RPC/HTTPS questions.

1. Are you using a home grown certificate or a purchased certificate.
If the former, you should be doing the later. While you can do RPC/HTTPS with your own certificate it causes additional complications. Go to freessl.com and get one of their 30 trial certificates.
When it comes to purchasing the certificate - a starterSSL from the same source is fine.

2. Check the authentication on the /rpc virtual directory in IIS Manager, Directory Security, Authentication.
It should be integrated and basic ONLY. Anonymous should be disabled.
It doesn't have to ask you for credentials - if the pass through authentication is working correctly then it may not. The key things with the web browser test is that you don't get a certificate prompt and you get the "correct" error message.

Simon.
0
 
phytomerAuthor Commented:
Uhh!!! It was so easy that I am embarrassed - I took your advice and freessl's ssl worked.  Any ideas what might be wrong with my "home grown" cert?  

Thanks,
Brad
0

Featured Post

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!

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