Link to home
Start Free TrialLog in
Avatar of ibtaya
ibtaya

asked on

RPC over HTTPS on Exchange 2003 working for iphone but not outlook

were running exchange 2003 on one box and the DC is on another box.

Configured RPC over https using this article:
http://www/amset.info/exchange/rpc-http-server.asp as provided by the god sembee

I've also ran the tests on www.testexchangeconnectivity.com and it errors out with not being able to ping the rpc proxy.

Any ideas where I could look to find this solution.  The exchange server is running 2003, the domain controller is still running 2000.

To make this even odder, my iphones are able to sync with no problems.  
Avatar of Glen Knight
Glen Knight
Flag of United Kingdom of Great Britain and Northern Ireland image

There is a guide here on configuring RPC-HTTPS: http://www.petri.co.il/how-can-i-configure-rpc-over-https-on-exchange-2003-single-server-scenario.htm

Are you entering the proxy server into the exchange client?
Avatar of ibtaya
ibtaya

ASKER

Thanks,  
Yes the outlook client is set up to point to the exchange in the connections tab.

This article is alot like sembee's article.  My confusion comes in why iphones are working but email clients are not.

This article also pertains to a single server deployment, I'm using multiple.
iphones use ActiveSync not RPC-HTTPS

Sorry you didn't make it clear you were in a multiple environment.

The Amset article covers it, is this the one you are looking at?
http://www.amset.info/exchange/rpc-http.asp
Avatar of ibtaya

ASKER

this is the article that I followed if you click on the server link from there.
The way that iPhones connect and the way that RPC over HTTPS connect are completely different.

This is your problem: "the domain controller is still running 2000"

RPC over HTTPS has strict requirements - one of those is that the domain controllers must be at least Windows 2003. You cannot use the feature at all with Windows 2000 domain controllers. You will have to upgrade.

My article on setting up RPC over HTTPS does state that right at the start.

Simon.
ASKER CERTIFIED SOLUTION
Avatar of ibtaya
ibtaya

Link to home
membership
This solution is only available to members.
To access this solution, you must be a member of Experts Exchange.
Start Free Trial
That isn't a supported configuration and you will not get full functionality. It requires Windows 2003 domain controllers for full functionality.

No one should have Windows 2000 anywhere near production these days.

Simon.
I missed the reference to 2000

Windows 2000 was officially unsupported in 2002.

Its easy enough to do an inplace upgrade to 2003 (which incidentally was unsupported as of April this year)
Avatar of ibtaya

ASKER

I agree with the 2000 comment, but what do you do?
What was the solution?