I'm trying to get RPC over HTTPS to work for our Exchange 2007.
Our network: DC, Exchnage 2007, ISA 2006 all joined to domain.
I've requested wildcard certificate *.domain.com so I can use with both owa.domain.com and rpc.domain.com. This certificate was installed in ISA server, and used for the Web listener below.
I've created a rule in ISA 2006
To: mail.domain.com (I've created a DNS to point this to our internal IP, which is 172.22.6.10, instead of our public IP)
Bridging: redirect requests to http port 80 (I've so sick of internal certificate and SSL connections so I just use redirect this over simple port 80)
- Name: OWA-RPC
- Authentication methods: Basic
- Port: 443
Public name: Rule applies to website mail.domain.com
Path: /rpc/*, /owa/*, /exchange/*, /public/*, /Exchweb/*
Authentication Delegation: Basic
The rule test was successful. In short, external people will have to access mail over address: https://mail.domain.com/owa
ISA authenticates users and redirects information to Exchange 2007 over port 80.
This works perfectly with OWA, but when it comes to RPC it failed with following error in loggin
Failed Connection Attempt <Firewall> 11/04/2009 12:54:31 AM
Log type: Web Proxy (Reverse)
Status: 64 The specified network name is no longer available.
Rule: Exchange OWA-RPC
Source: External (<External IP address>)
Request: RPC_IN_DATA http://mail.domain.com/rpc/rpcproxy.dll?Exchange.Localdomain:6001
Filter information: Req ID: 091c2910; Compression: client=No, server=No, compress rate=0% decompress rate=0%
MS Connection Status keep showing connecting, and then disconnected. I cannot work out what's wrong with RPC, I've done a considerable amount of time surfing on the internet without any success. Please help.