RPC over HTTP Client (Full Version)

All Forums >> [Microsoft Exchange 2003] >> Installation



Message

breeze169ca -> RPC over HTTP Client (11.Mar.2004 8:03:00 PM)

I am using a front-end and back-end server to do this.

I followed http://www.outlookexchange.com/articles/HenrikWalther/RPC_over_HTTP.asp.
The RPC Proxy service is installed on the Front-end server (along with an SSL certificate).

OWA over ssl works no problem.

I have applies the hotfix to the client box & when I configure everthing i get a username/password box I enter the users information & then get

"The connection to the Microsoft Exchange Server is unavailable. Outlook must be online or connected to complete this action." It then prompts the dialog for the server name and mailbox name. Hitting OK on this dialog results in the error "Unable to open your default e-mail folders. The information store could not be opened."

This is working fine internal at this point. It doesn't work external.
any thoughts?



Henrik Walther -> RE: RPC over HTTP Client (12.Mar.2004 11:06:00 AM)

When you are prompted for username/password, try right-clicking the Outlook icon in the Systray and choose Connection Status, or open Outlook by clicking Start > Run and type Outlook /rpcdiag.

In the connection status window, does the client try to establish sessions throught HTTPS ?



breeze169ca -> RE: RPC over HTTP Client (13.Mar.2004 1:19:00 AM)

It is connecting, and it freezes for 10 mins and these messages appear:

"The connection to the Microsoft Exchange Server is unavailable. Outlook must be online or connected to complete this action."

"Unable to open your default e-mail folders. The server is not available. Contact your administrator if this condition persists."



Demo Dick -> RE: RPC over HTTP Client (14.Mar.2004 1:34:00 AM)

breeze

I was having the same sort of problems.

check out http://forums.msexchange.org/ultimatebb.cgi?ubb=get_topic;f=14;t=000394 maybe it will shed some light on your issues



breeze169ca -> RE: RPC over HTTP Client (17.Mar.2004 5:10:00 PM)

I've got 2 machine working. But it didn't work with other laptop that I setup.

Any thought?



madcow -> RE: RPC over HTTP Client (21.Mar.2004 4:22:00 AM)

quote:
Originally posted by breeze169ca:
It is connecting, and it freezes for 10 mins and these messages appear:

"The connection to the Microsoft Exchange Server is unavailable. Outlook must be online or connected to complete this action."

"Unable to open your default e-mail folders. The server is not available. Contact your administrator if this condition persists."
Try using the Rpings on the Exchange Server and Rpingc on the client.

[Mad]



jvandestadt -> RE: RPC over HTTP Client (21.Mar.2004 2:53:00 PM)

I have been reading through the posts and tutorials but I am stuck.

I've set everyting up in a lab with help of the following links:

http://www.msexchange.org/tutorials/MF004.html
http://www.msexchange.org/tutorials/Outlook_2003_Connect_Exchange_2003.html
and
http://www.msexchange.org/tutorials/outlookrpchttp.html

Setup:

2003 server
exchange 2003
owa on ssl with certificate installed
rpc over http enabled
<>
firewall (only https open)
<>
xp client
Outlook 2003
The hotfix installed on the client

When I configured my outlook client it worked when connecting with RPC directly to the exchangeserver (on the same segment) but now I took my client in a DMZ and allowed it to communicate only with HTTPS to the server.

It does not work.

What do I see:

Startup outlook...I get the username/pwd box.

ctrl click icon open up "connection status window"

Type int conn status
directory --- connecting
referal https connecting
directory --- connecting
mail https connecting
mail https connecting
mail --- connecting

I fill in the uname/pwd

I get outlook.

Below in the status bar: preparing to send/receive

The connection status window changes to

Type int conn status
directory --- connecting
directory --- connecting
mail --- connecting
mail --- connecting
mail --- connecting
referal --- connecting
referal --- connecting
referal --- connecting

Nothing is exchanged between the client and the server.

When I check out my firewall logging I see the following:

Starts with one https session
then one http session
then a bunch of https sessions
then a bunch of rpc sessions

I can understand that the client switches to RPC when HTTPS failes but what does that http request do ?.

Because it's in a lab it could not hurt to openup also http (just for the heck of it) but also this does not work.

When I opened up all communication from the client to the server I see a mixture of:

HTTPS
HTTP
RPC
port 1025
port 1147
port 1217

But it works....now I have a working outlook client

It seems to communicatie primarily on HTTPs but now and then these other protocols swing by (its in a lab so no polution from other apps)...what am I doing wrong ??



tyronet -> RE: RPC over HTTP Client (3.Apr.2004 8:04:00 PM)

I am having exactly the same problem. When I setup everything initially it worked fine with the firewall turned on Echange was communicating over 443. However, when I setup a VPN for a Windows 2000 user, my client could no longer connect to the server. When checking the firewall logs I can see the client trying to connect to the server using the old RPC ports -- works fine when I turn the firewall off. Any ideas what I'm doing wrong?

This is extremely frustrating. Any insight would be greatly appreciated!



jvandestadt -> RE: RPC over HTTP Client (4.Apr.2004 12:50:00 AM)

Sorry, I still haven't found a solution. I'll give it a rest for a while and take a look at it a bit later.



ttnetworks -> RE: RPC over HTTP Client (4.Apr.2004 7:16:00 PM)

Hi,

I today have successfully managed to get Outlook 2003 to work over HTTPS and RPC.

The articles on this site dont provide the full story, i used google a lot to find the answers.

Have you setup the RPC proxy server ? This needs to installed via windows components, and is under networking services.

Also once you have installed the RPC proxy server you need to make some registry changes on both the exchange server and on the global catalog servers so it knows where to send the HTTPS traffic.

I will compile a list of articles I used and post them.

Thanks

Andrew



Guest -> RE: RPC over HTTP Client (6.Apr.2004 4:45:00 PM)

I'm having the same problem. Outlook for what ever reason still wants to use RPC. When I look at the exchange server connection status window, it shows:

server_name:mail, type:directory interface:(blank), conn: ---, status: connecting

It's showing the above with the addition to the server name as mail.domain.com.

Basicly what's happening from firewall logs is it's trying to establish a connection via HTTPS, however, it is still trying to open a RPC connection and when that fails, it just sits there trying to connect. I've done as much research as I can via google, microsoft's web site, and support sites such as this. Does anyone have any suggestions that I can try to resolve this issue?



Guest -> RE: RPC over HTTP Client (6.Apr.2004 6:22:00 PM)

Problem solved for me... The fix for me was to remove the trailing ';' in the valid ports reg key. It's now connecting through a ISA2004 server using certificate binding. It's funny how something so small can cause the strangest of problems.

BTW Ron, you should update your post and remove the last semi-colon as it might cause others problems.



Guest -> RE: RPC over HTTP Client (7.Apr.2004 12:31:00 PM)

Sorry for stalking this forum... but.... [Smile]

RPC over HTTPs is working for me now through a ISA2004 server. I'm able to send/recieve email, etc. However for some reason the exchange server is trying to establish a HTTPS connection on random ports with the ISA server. All the ports are 28295-28301 (it's going up as more and more connections are esablished). All of these connections are being deined by the ISA server.

Does anyone know why it's doing this, and what these connections are?



aamer -> RE: RPC over HTTP Client (14.Mar.2005 12:10:00 AM)

It seems like there are a ton of poeple online who are having trouble with RPC over HTTPS. I was one of them, but I got a solution now and I wanted to share it with everyone.

I had followed all the RPC instructions on microsoft's web site. And still my Outlook client would hang when I was outside of my LAN. Why?? Well, it turns out that if you have a SSL certificate you created using SELFSSL, then you may have an issue!

First thing you need to do is to make sure that you created the right kind of certificate. Namely, make sure that you set a large enough window for the expiration date and then make sure that \N option says something like "*.mydomain.com" so that you cover all subdomains for that certificate (as most of you probably want to do).

Now try going to the RPC web page by pointing Internet Explorer to https://FQDN/rpc ... do you see a pop up screen giving you a warning about the certificate? If so, then click on "view certificate" and then click on "install certificate". Now you have installed that SSL certificate and you should not see this pop up screen agian. Try shutting down Internet Explorer, restarting it, and then going to that web page again. Now you should not see that pop up warning screen about the SSL certificate.

Hopefully this should fix your problem. It did for me!



quizwedge -> RE: RPC over HTTP Client (30.Oct.2005 11:43:37 PM)

major kudos to aamer!  I was starting to pull my hair out!



Page: [1]