We help IT Professionals succeed at work.

We've partnered with Certified Experts, Carl Webster and Richard Faulkner, to bring you two Citrix podcasts. Learn about 2020 trends and get answers to your biggest Citrix questions!Listen Now


RPC over HTTPS is not working

hiepho asked
Medium Priority
Last Modified: 2008-02-01
This is to follow up with my previous question here:

i reinstalled a new server and used a different domain name. i still got the same problem. i am not able to connect to it. i think the problem may be my firewall. i have netscreen 5xt  but i am not sure how to configure or allow port 6001-6004 for RPC over HTTPS. is this the problem here?
Watch Question

Expert of the Year 2007
Expert of the Year 2006

You don't do anything to your firewall other than allow port 443 through. No other ports need to be opened as that is the point of the feature.
Furthermore you should be trying to get this to work inside the network first - so the firewall configuration should be playing no part in any problems with RPC over HTTPS. Get it work inside first, then go outside.



thanks for the firewall tips, i have removed the ports that i just opened.

i got the new test server i just built working now both internally and externally. i am not sure what i did other than going over and over all the steps and make sure they are correct. one interesting thing is this:

in client outlook the setting is kind of not right but for some reason it still works.
E-mail accounts > Exchange Server Settings > Microsoft Exchange Server: initial set up i had mail.mydomain.com but once it is connected it changed to servername.mydomain.com instead.

as you can see servername.mydomain.com is not qualified domain but it works for some reason. is this normal? is my RPC over HTTPS working right yet or if it works then it's ok to leave it?
Expert of the Year 2007
Expert of the Year 2006

The initial Outlook configuration will also correct to the server's real name. That is by design and is to be expected.
What I usually suggest is that Outlook is configured in the regular way and verified that it is working correctly. Then add the RPC over HTTPS settings separately. That allows you to rule out a problem with the account or the basic setup.

To verify that RPC over HTTPS is working, add the entries in to Outlook, then close Outlook completely.
Click Start, Run and type

outlook.exe /rpcdiag

and press enter.
This will show you what Outlook is doing. If it shows the connection protocol as https then it is working. If it shows it as tcp/ip then it isn't working correctly.
Take a look at my web site here for a screenshot.



Outlook works normally in regular way before i attempted RPC.

i have done outlook.exe /rpcdiag and it did say HTTPS connection.

i guess i need to figure out why the real server is not working just like the one i just built.

Expert of the Year 2007
Expert of the Year 2006
If RPCDIAG shows https then the feature is working correctly. You will need to compare the configuration of the two machines. If they are both in the same domain, then the registry entries should be different only in the name of the Exchange server - everything else should be the same.


Not the solution you were looking for? Getting a personalized solution is easy.

Ask the Experts


i can't believe it. it was a simple configuration that solve the problem. i don't need to build another test machine now. it works now.  

after i have read through this post here that had the same problem as mine

in IIS > rpc > i need to have it set to "Scripts and Executables" instead of just "Scripts"

Access more of Experts Exchange with a free account
Thanks for using Experts Exchange.

Create a free account to continue.

Limited access with a free account allows you to:

  • View three pieces of content (articles, solutions, posts, and videos)
  • Ask the experts questions (counted toward content limit)
  • Customize your dashboard and profile

*This site is protected by reCAPTCHA and the Google Privacy Policy and Terms of Service apply.


Please enter a first name

Please enter a last name

8+ characters (letters, numbers, and a symbol)

By clicking, you agree to the Terms of Use and Privacy Policy.