RPC-over-HTTP Authenticates But Won't Connect

Okay - Setup RPC-over-HTTP using the instructions on Petri (http://www.petri.co.il/configure_rpc_over_https_on_a_single_server.htm) and everything tested out on the local network, even with the local exchange ports disabled (So it was forced to use port 443).

My problem comes in when I move outside the network; it pulls up the login diialog and everything looks like it connects but then all the connections break. Now I forwarded port 80, 443, 6000-6004 to the exchange server and I turned off everything on the firewall (IPS, Content Filtering, Gateway Virus).

Any ideas?

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.

What is the authentication methode chosen in outlook when you configure for connection from the outside?
ryanj1987Author Commented:
Both are Basic Authentication (Configured on the RPC folder in the default website).
Are you using a home made certificate? What is the internal and external domain name?To which name the certificate is assigned?
za_mkhIT ManagerCommented:
If the certificate used for SSL is 'home-made', you need to add that certificate to the local trust store on your computer for it to work. The easiest way to check this, is to connect to your exchange server OWA using https://..... and seeing what IE throws up to you. Based on this, than you can follow as isaman07 is asking about

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
ryanj1987Author Commented:
That was the issue, I self issued a cert and although it was done correctly (the name on the cert matched the full name it was connecting to) it wasn't actually signed by a real authorative. Went out and bought a SSL, thew it into IIS and it's working perfect!

Thanks guys!
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
Email Clients

From novice to tech pro — start learning today.