OWA and RPC over HTTPS - Using Port Other than 443

Posted on 2004-11-11
Last Modified: 2012-05-05
I have been running OWA and Outlook RPC over HTTPS successfully in a Win2K3/Exchange Srvr 2003 environment, but recently my ISP blocked Port 443, so now I can only get in via VPN.

Is there a way to change the SSL port to something other than 443?  If so, can someone point me to the relevant documentation?  I assume I need to change both IIS and Exchange Server, and of course the Outlook RPC over HTTPS config and OWA URL.  I think I can handle the last two but could use some help getting started on the first two - as well as knowing what else I might need to change.
Question by:douglasrice
    LVL 104

    Expert Comment

    Can't be done. RPC/HTTPS relies on the SSL/HTTPS configuration running over the standard ports.

    I haven't heard of an ISP blocking 443 before. What was the reason given?


    Author Comment


    I haven't asked why - the DSL user agreement says you can't run a web server and technically this is one (even if it's just for my personal use when I travel. I didn't exactly want to ask them why they wouldn't let me do somthing that the agreement says I can't do.  I'm assuming they block it because of that policy.

    What about OWA?  Could I reach that via https://x.x.x.x/exchange:abc where abc is a port other than 443?
    LVL 104

    Accepted Solution

    Others will say that you can access OWA on another port - I have had problems with it. You must remember that it is a very complex application and it does get upset quite easily.

    If your router/firewall supports it, what you may want to try is leaving IIS port settings alone and redirecting the port. Port 4444 externally will redirect to port 443 internally. It may work, although I haven't tried it. Here in the UK the DSL market is very healthy and if a company blocked a port like that I would dump them immediately for another one.
    I suspect that they will try to sell you a business class service instead.

    The other choice is VPN, then run whatever (OWA, RPC/HTTPS etc) over that.


    Author Comment

    Thanks Simon.  Not the answer I was hoping for, but you can't help that! I have been using VPN as a temporary measure but RPC over HTTP is sooo much easier when you're traveling - not all hotel internet solutions are VPN-friendly.  And I miss OWA when I'm on a public PC.  Will try 4444, then beat up on my DSL service (which is, in fact, business class - just not fast enough to support a website).

    Write Comment

    Please enter a first name

    Please enter a last name

    We will never share this with anyone.

    Featured Post

    Hire Top Freelancers to Complete Exchange Projects

    Source the talented Expert Exchange community
    for top quality work on your Exchange projects.

    Hire the best. Collaborate easily. Get quality work.

    Set up iPhone and iPad email signatures to always send in high-quality HTML with this step-by step guide.
    Check out this infographic on what you need to make a good email signature that will work perfectly for your organization.
    To show how to generate a certificate request 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 Servers >> Certificates…
    In this Micro Video tutorial you will learn the basics about Database Availability Groups and How to configure one using a live Exchange Server Environment. The video tutorial explains the basics of the Exchange server Database Availability grou…

    760 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

    13 Experts available now in Live!

    Get 1:1 Help Now