RPC over HTTP setup thru firewall

Exchange 2000

    Sponsored Links


  • 1. setting up a new exchange server to take over existing one
    I had some major issues with our primary exchange 2003 server (running on windows server 2003 standard) a year ago, a second exchange server had to be setup to take it's place - information store was moved over and it ran fine. I need to reinstall exchange on the original server and move the information store over to that one. When installing exchange it asks you if this is the only one on the network or an additional one - if intending to remove the functioning one from the AD network, which should you choose for seting up the new one. Also - the original exchange server is still listed in AD even though it was taken offline a year ago- is there special procedure to remove it from AD - and how will this affect the functioning exchange server.
  • 2. Public Folder IPM.Post to IPM.Note
    Hello, I want to change my incoming messages to my public folders from IPM.Post to IPM.Note. I have found the patch regarding this and the information associated. My question is that the hotfix info mentions that it is not required if Exchange 2003 SP1 is already installed. We have SP2 installed - should I assume that it is already bundled then? If so, is my only remaining step to add the regkey and proper value on all servers that contain the public store? Thanks in advance!!!
  • 3. Exchange Mail Forwarding And Out Of Office
    Hi, I currently have a user who has set their out of office and I need to ammend their message. I know I can change the users password, log on to their account and change the out of office reply, but is there another way without having to do this? Also, I need to forward this users messages on to another member of AD. I have tried setting the user to forward on to in the Delivery options properties box and checked the "Deliver messages to both forwarding address and mailbox " but nothing comes through to the other AD users inbox. Any help would be greatly appreciated. Thanks.
  • 4. Remove old Exchange server
    Hi, I replaced a 2000 Exchange server with a 2003 Exchange server and had planned to removed the old one properly, as in transferring roles, and then using the Exchange 2000 CD to uninstall Exchange. Well, I got as far as transferring roles and mailboxes and then the old server died on me. I'm confident that everything was transferred across, and all is working fine with the new server. How can I go about deleting the old server from Exchange System Manager and AD? Can I just right click the server in ESM and select delete? And then delete the server from AD? Thanks, Gary.
  • 5. Auditing Exchange events in terms of who did it.
    Using Exchange 2003 ... We are in the process of delegating Exchange related task to area ICT staff. We understand all the rights that are required. However a simple thing like changing mailbox right can only be done if staff are given at least "administer information store" rights in Exchange. That means of course the user can stop and start the Information Store. Does anyone have any idea how to monitor/audit/log exchange events such that the account/user/staff member who did the deed is identified? Tool? Script? Diagnostic Logging? Product to purchase? What would be great is logging everything, such as: who created mail-enabled/created a mailbox for a user who increased limits who change rights who stopped the info store who started the info store who added and email address etc anyone?

RPC over HTTP setup thru firewall

Postby SmFsZXhhbmRlcjAx » Tue, 03 May 2005 00:32:03 GMT

I've got Exchange Server 2003 SP1 setup on Windows Server 2003.  I can 
configure an outlook client to connect via RPC over HTTP from inside the 
building and it works.  I can also get to OWA within the building.  However, 
I can't get to either from outside beyond the firewall.  

The firewall is configured to allow incoming port 443 connections to the 
mail server, and when I attempt to view OWA from elsewhere, the traffic comes 
in successfully.  RPC over HTTP connections generate a fistful of successful 
incoming traffic as well, but it doesn't work either.  OWA says "The page 
cannot be displayed" and RPC over HTTP says "Your microsoft exchange server 
is unavailable.  Retry, work offline, or cancel".  

Since I can get to both behind the firewall, I know the exchange server is 
setup right.  Since I see the traffic coming in on 443, I believe the 
firewall is configured properly.  Is there another port I need allowed or 
something for this to work?  

Thanks in advance

Re: RPC over HTTP setup thru firewall

Postby Mark Arnold [MVP] » Tue, 03 May 2005 01:40:23 GMT

On Sun, 1 May 2005 08:32:03 -0700, Jalexander01

No, 443 only if you're using RPC over HTTPS and OWA with SSL.
Is the box a front end server in a DMZ or something? If you have it in
a DMZ there are probably different rulesets to allow LAN>DMZ but
Internet>DMZ>LAN might be incorrect.
Not that the DMZ is the place for an FE, or any other type of Exchange

RE: RPC over HTTP setup thru firewall

Postby QW50aG9ueQ » Wed, 04 May 2005 00:56:07 GMT

I just got RPC working on my network at work and we had to use SSL and have 
users install a cert to authenicate with our Exchange server to allow RPC. 
Additionally we had to make specific firewall rules to allow this to enter 
out network and authenicate. I actually worked on MS on this for a couple of 
days to get this going.

Are you using SSL for the RPC connection?

Similar Threads:

1.RPC via HTTPS passing thru a HTTP proxy?

We have just finished our deployment of RPC over HTTPS, and it's working 
great... with one issue we've run into.

Most of our users tend to work from "offsite" locations - home, hotel, 
client site, etc.  In MOST cases, the RPC over HTTPS functionality is working 
flawlessly.  However, from ONE site, our users are not able to connect to our 
server and access Outlook over HTTPS.  

At this particular site, they are required to configure IE to use an HTTP 
proxy server to access internet sites.  From most of the articles and 
postings I've managed to find on this, it SOUNDS like Outlook should be able 
to "pick up" those settings from IE and use that proxy server to connect.  
However, that doesn't seem to be happening in this case.  When the folks at 
this site attempt to connect, the connection fails.  Unfortunately I can't 
get hands on to their machines to acutally "see" what's happening, but it 
sounds like either the proxy settings are not being used by Outlook 2003 
trying to connect RPC over HTTPS, or that the proxy server configuration is 
such that it's somehow blocking / failing to make this connection.  I'm not 
an expert in proxy servers by any means, so I'm wondering if anyone here has 
either run into this, or may have some suggestions on where to start looking 
for troubleshooting or workaround ideas?

I do know what the IE settings are for the proxy server, as well as having 
the proxy.pac config file that is used as the automatic configuration script 
for the proxy settings.  Looking at that file, it LOOKS like access to our FE 
server should just cause the system to be set to the "baseline" proxy server 
(their_proxy_IP:8080) but I'm not sure if something in that script is 
tripping up the Outlook connection, or...?

Any ideas on what to try or what might be happening?  Should Outlook 2003 be 
able to get the proxy settings from IE and make that connection thru the http 
proxy server?

2.Transitioning RPC-HTTP setup from back-end only to front-end / back-end setup

3.RPC over HTTP thru ISA

4.Exchange 2003 - Firewall - RPC over HTTP

What must be opened through a firewall in order for RPC over HTTP to
I thought it did everything through TCP/IP port 80.  Obviously this is

Anyone know?

(The reason I state it the way I have.. It works as long as both machines
are behind the firewall.  Once the client is outside the firewall, it fails
to work.  As the purpose of RPC over HTTP I thought was to avoid opening
more ports through the firewall and/or using VPN/PPTP - what am I missing?)

5.RPC-over-HTTP firewall problem SOLVED!

6. RPC-over-HTTP firewall problem

7. Rpc over http trought Win2003 RRAS Firewall Problems

8. RPC over HTTP on Exch 2003 SP2 w/ 2003 SP1 behind an ISA 2004 SP1 Firewall

Return to Exchange 2000


Who is online

Users browsing this forum: No registered users and 95 guest