ISA 2006:- Exchange 2007 RPC over HTTPS not working

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
==========================
From: Anywhere
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)
Web Listener:
- Name: OWA-RPC
- Authentication methods: Basic
- Port: 443
-Certificate: *.domain.com
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>)
Destination: (172.22.6.10:80)
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%
Protocol: https
User: domain\user
~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~

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.
LVL 1
Johnny_NguyenAsked:
Who is Participating?
 
Johnny_NguyenConnect With a Mentor Author Commented:
Got it fixed. After a lot of checking using RpcPing, I found out It was a DNS issue though very subtle.
I re-did the whole DNS setting and it worked now.
0
 
Johnny_NguyenAuthor Commented:
More information,
- I have installed RPC over http on Exchange Server. Enabled Outlook Anywhere from Exchange 2007 Console, set Authentication to be Basic.
- In IIS on Exchange server: I have set the security for RPC virtual directory to accept Basic Authentication, and uncheck the "Require Secure Channel (SSL)", exactly like the OWA directory.

- When I test browsing this http://mail.domain.com/rpc from internal network, without prompting me anything it led straight to
~~~~~~~~~~~~
"The website declined to show this webpage"
This error (HTTP 403 Forbidden) means that Internet Explorer was able to connect to the website, but it does not have permission to view the webpage.
For more information about HTTP errors, see Help.
~~~~~~~~~~~~
0
 
AkhaterCommented:
you should try by testing your rpc/http internally

you can do this by setting outlook to connect using http on both fast and slow network
0
Making Bulk Changes to Active Directory

Watch this video to see how easy it is to make mass changes to Active Directory from an external text file without using complicated scripts.

 
Johnny_NguyenAuthor Commented:
I've set outlook to use this rpc connection, when the PC is in internal network outlook prompt me for user/pwd then it works. In MS Exchange connection Status:
It starts with connecting then established.  But I notice the connection turns from HTTPS to TCP/IP
0
 
AkhaterCommented:
you mean that even internlly u cannot connect using rpc/http ? when it is connected it is usin TCP/IP ?

well then it seems more like an exchange issue

btw outlook anywhere can only work with https protocol if using basic authentication
0
 
Johnny_NguyenAuthor Commented:
As I mentioned, It works internally after prompting for a user/pwd. And when it does, all the https connection turn to TCP/IP, status turns to established.

Yeah I know Outlook Anywhere works with https using basic authentication, but thats what I use.

Any ideas, please ?
0
 
AkhaterCommented:
well tcp/ip doen't mean rpc/http it means "normal" operation
0
 
Johnny_NguyenAuthor Commented:
Okay, any help on this issue please
0
 
SteeCommented:
Is there any more info on the DNS issue as I have the same error..
0
Question has a verified solution.

Are you are experiencing a similar issue? Get a personalized answer when you ask a related question.

Have a better answer? Share it in a comment.

All Courses

From novice to tech pro — start learning today.