OWA and RPC over HTTPS - Using Port Other than 443

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.
douglasriceAsked:
Who is Participating?
I wear a lot of hats...

"The solutions and answers provided on Experts Exchange have been extremely helpful to me over the last few years. I wear a lot of hats - Developer, Database Administrator, Help Desk, etc., so I know a lot of things but not a lot about one thing. Experts Exchange gives me answers from people who do know a lot about one thing, in a easy to use platform." -Todd S.

SembeeCommented:
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?

Simon.
0
douglasriceAuthor Commented:
Thanks...

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?
0
SembeeCommented:
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.

Simon.
0

Experts Exchange Solution brought to you by

Your issues matter to us.

Facing a tech roadblock? Get the help and guidance you need from experienced professionals who care. Ask your question anytime, anywhere, with no hassle.

Start your 7-day free trial
douglasriceAuthor Commented:
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).
0
It's more than this solution.Get answers and train to solve all your tech problems - anytime, anywhere.Try it for free Edge Out The Competitionfor your dream job with proven skills and certifications.Get started today Stand Outas the employee with proven skills.Start learning today for free Move Your Career Forwardwith certification training in the latest technologies.Start your trial today
Exchange

From novice to tech pro — start learning today.

Question has a verified solution.

Are you are experiencing a similar issue? Get a personalized answer when you ask a related question.

Have a better answer? Share it in a comment.