RPC over Http

Hi,

Thanks for contacting Microsoft. I have started to work on your issue and will get back to you as soon as possible.

Thanks,

Harjit.

Hi,

I have found the following articles on Microsoft Site. Please let me know if you had a chance to go through them and if it helps to resolve your issue.

Microsoft Exchange Server 2003 Client Access Guide:

http://technet.microsoft.com/en-us/library/bb123645.aspx

Exchange Server 2003 RPC over HTTP Deployment Scenarios:

http://technet.microsoft.com/en-us/library/92f1a371-86dc-4839-9732-5a85525a0874.aspx

Thanks,

Harjit.

Harjit,

Thanks for the information but i seems to have stumbled upon the answer with my collegue. What the issue was is that, on the initial screen where it asks for the exchange server name and usernamer (u know where it will underline the name if it finds the server) i needed to put the mailbox store's server name, then go into exchange proxy settings in advanced menu options on the client configurations screen and put, mail.XXXX.com, click on fast connection check box and i left the mssds(i believe this was the bottom portion setting) blank. So i have it working.

Since i was external to the location, for example in pop mail usually u enter the external dns resolution for the external server which is mail.XXXX.com or ip address, which is what i was putting in the initial screen where i should have put the actual internal server name, which is what the problem was.

Hope that made sense. If it doesnt please send me an email and i will email you screenshots of what i am talking about. All the articles i found anywhere tell me i should have mail.XXXX.com in both places which is wrong. Please have microsoft update the docs, as this was a big headache just for having the wrong servername setting.

Also thanks for the time and efforts you have taken out in trying to assist me in finding a solution.

Sunny

Also, another question i have is that i'm told that by using RPC over HTTP, the protocol is actually logging into the OWA and pulling the attributes from OWA into outlook client using RPC over HTTP, is this true Is RPC over HTTP only a transport medium to view OWA in a more user friendly full outlook client

thanks again.

Hi,

The first bit of information is correct. Initially, in Outlook 2003, when we enter our server information it¡¯s requesting the actual mailbox server name. This could be the NETBIOS or FQDN of the ¡°back end¡¯ mailbox server (ex. mbserver.contoso.com). After clicking ¡°More Settings > Connection tab¡±, under ¡°Exchange over the Internet¡± check the ¡°Connect to my Exchange mailbox using HTTP¡± check box. Then click ¡°Exchange Proxy Settings¡­¡± This is where you enter the RPC Proxy server which is usually the ¡°front end¡± server¡¯s external FQDN (ex. mail.contoso.com).

All this information is available in the white papers. The links of the white papers were posted by me in the past.

As per the second question. This is totally untrue. The white paper, explains how RPC over HTTP works. Essentially Outlook connects to the ¡°front end¡± server, which is where a lot of users get OWA anyway (that could be where the confusion lies). This ¡°front end¡± server PROXIES the Outlook RPC requests directly to the mailbox server that houses that particular user¡¯s mailbox.

The data stream looks somewhat like this:
For Outlook RPC over HTTP:
Outlook client <-HTTPS protocol-> front end mailbox server (RPC proxy server) <-RPC protocol-> back end mailbox

For OWA:
IE browser <-HTTPS protocol-> front end mailbox server (OWA server) <-HTTP protocol-> back end mailbox server

Please let me know if you have any questions.

Thanks,

Harjit.