Welcome to ISAserver.org

RPC over HTTPs - Problems

Users viewing this topic: none

Logged in as: Guest

Printable Version

All Forums >> [ISA 2006 Publishing] >> Exchange Publishing >> RPC over HTTPs - Problems

Page: [1]

Message

<< Older Topic Newer Topic >>

RPC over HTTPs - Problems - 28.Aug.2008 5:47:23 AM

thomid

Posts: 6
Joined: 28.Aug.2008
Status: offline

I have a problem with RPC over HTTPs

I can successfully use RPC over HTTPs externally if I've first setup my clients with local connection to the Exchange server (ie VPN or LAN) and then connect through external connection. My challenge is that I cannot setup my clients to use RPC over HTTPs through external connection.

I've followed the article from Thomas Shinder http://www.isaserver.org/tutorials/ISA-Firewall-Publishing-OWA-RPC-HTTP-Single-IP-Address-Part1.html

Please help

Configuration:
ISA Server 2006 SP1 on Windows Server 2003 R2 SP2
Exchange 2003 SP2 on Windows Server 2003 R2 SP2

Post #: 1

Featured Links*

RE: RPC over HTTPs - Problems - 28.Aug.2008 5:51:19 AM

Jatin.Jagota

Posts: 8
Joined: 21.Aug.2008
Status: offline

Hi,

Are you installing client certificate on your client computer? i mean on external network computer? because without that it will not resolve your exchange server name.

Regards,
Jatin

(in reply to thomid)

Post #: 2

RE: RPC over HTTPs - Problems - 28.Aug.2008 6:40:21 AM

thomid

Posts: 6
Joined: 28.Aug.2008
Status: offline

Yes. I have a bought a 3rd party certificate that's trusted. OWA and ActiveSync works great, so it shouldn't be necessary to install the certificate right?

(in reply to Jatin.Jagota)

Post #: 3

RE: RPC over HTTPs - Problems - 28.Aug.2008 7:19:16 AM

Jatin.Jagota

Posts: 8
Joined: 21.Aug.2008
Status: offline

Yes it is necessary to install client certificate; as OWA and Async works on server based certificates but when you configure RPC over HTTPs then i need a client certificate to be installed; without that it will not resolve the exchange server name. So please issue a certificate from CA for client machine and install it. Then your problem will be resolved.

Make sure not to use Sub CA certificate on client machine; only client certificate will make the communication possible.

Regards,
Jatin

(in reply to thomid)

Post #: 4

RE: RPC over HTTPs - Problems - 28.Aug.2008 7:49:16 AM

thomid

Posts: 6
Joined: 28.Aug.2008
Status: offline

OK. I'm not sure wich certificate to install. My client certificate points to mx.domain.com. How can this certificate help the clients to resolve the hostname of the Exchange server (ie exchangeserver.domain.com)?

(in reply to Jatin.Jagota)

Post #: 5

RE: RPC over HTTPs - Problems - 28.Aug.2008 8:23:36 AM

Jatin.Jagota

Posts: 8
Joined: 21.Aug.2008
Status: offline

Well Install the CA certificate in your trusted root through MMC. Certificate will authenticate user only And for server name resolution make IP address entry of your webmail and exchange server in your client computer ""hosts"" file; this will resolve the server name.

(in reply to thomid)

Post #: 6

RE: RPC over HTTPs - Problems - 29.Aug.2008 7:51:49 AM

thomid

Posts: 6
Joined: 28.Aug.2008
Status: offline

OK. I had done everything right the first time. The solution to my problem was to publish Outlook (RPC) Standard port with the "Publish Mail Serves" Wizard.

Outlook RPC must be published to setup new Outlook profiles externally.

(in reply to Jatin.Jagota)

Post #: 7

RE: RPC over HTTPs - Problems - 16.Sep.2008 5:01:41 PM

hidoa

Posts: 10
Joined: 13.Sep.2008
Status: offline

thomid,
Can you explain in a little more detail how you did that, i'm having the same problem with Exchange '07 and ISA '06...
Thanks!

(in reply to thomid)

Post #: 8

RE: RPC over HTTPs - Problems - 17.Sep.2008 4:59:23 AM

thomid

Posts: 6
Joined: 28.Aug.2008
Status: offline

Outlook uses RPC/MAPI to connect to Exchange when creating a new account/profile. Creating a new profile externally will be denied in ISA if you havent published Outlook RPC standard port. To do so:

1. Publish Mail Server
2. Choose Client Access: RPC, IMAP, POP3, SMTP
3. Check Outlook (RPC) (Standard port)
4. Type the IP adress of your Exchange server.

Then you have to allow RPC (All interfaces) from the external computer to the internet.

Good luck

(in reply to hidoa)

Post #: 9