Re: RPC over HTTPs

Bart:
It is obvious that you have done your research on this. When you
connect to the Exchange server using IE using the http://exchangeserver/rpc
URL, do you get a message indicating that the CA that issued the certificate
is not trusted? If so, THAT will break RPC over HTTPS for sure. Make sure
that the CA's certificate is installed on the client. Maybe I'm thinking of
something too simple, though.

Did you make the manual changes to the DC/GC that you are supposed to
make in the Registry? There used to be a KB article on configuring RPC over
HTTPS in a single server environment, but that information has been rolled
up in to the "RPC over HTTP Deployment Scenarios" gude. You can get to it
here:
http://support.microsoft.com/Default.aspx?kbid=833401

I just spent an entire day troubleshooting a very similar problem but it
turned out the workstation was having network problems. :-)

--
Jim McBee
Blog: http://mostlyexchange.blogspot.com
Free eBook: http://nexus.realtimepublishers.com/ttgsm.htm


"Bart" <Bart@xxxxxxxxxxxxxxxxxxxxxxxxx> wrote in message
news:D23E1540-9521-498C-8A57-36B3919AAB6E@xxxxxxxxxxxxxxxx
I followed the MS and some non-MS tips on how to setup RPC over HTTPs, but
so
far no luck.

The server runs Exchange 2003 with the latest patches. It is also a
Win2003
DC.

My client computer has Outlook 2003 with all latest patches. IE on that
machine can access the https:// address that is supposed to give access to
exchange.
Using /rpcdiag tells me that the 'directory' type is connecting through
https, but the 'mail' type fails.

When outside the firewall, I can see the 'mail' connection tries to
connect
with the NETBios name, rather than the FQDN (The 'directory' type
connection
uses the FQDN). I added the NETBios name to the hosts file and checked
that
it is pingable with its NETBios name).

Running the same Outlook machine from inside the firewall does connect
successfully, but an inspection of the /rpcdiag window shows that it is
cheating (using TCP/IP instead of HTTPS for the 'Mail' type connection,
and
HTTPS for the 'directory' type connection. )

Could there be an issue with the certificates? Because 'mail' is using the
NEtbios name, does that mean it will want a certificate with that as the
full
name?

Thanks.



.

Relevant Pages

  • Re: mail routing redundancy in Exchange 2007
    ... For Exchange Server 2007 - previous versions have link state, ... - checks whether the local internet connection is available or not ...
    (microsoft.public.exchange.connectivity)
  • Re: Unable to connect Outlook 2007 to Exchange 2003 Server
    ... The server is a Windows 2003 SBS Premium, ... it tries to autodetect the settings for Exchange. ... "The connection to Microsoft Exchange is unavailable. ...
    (microsoft.public.outlook)
  • Re: RPC over HTTP problem for some users only
    ... clarification from the exchange mvps just to make sure that i give you good ... > I did have my Outlook configured to use HTTP on a fast connection and I ... Do I do that on the RPC PRoxy server ... >>> Internet, every thing works fine. ...
    (microsoft.public.outlook.installation)
  • Re: RPC-HTTP problems
    ... Exchange access within our office and with OWA access outside our ... rpc-http connection to work outside our office. ... assure iis is allowing the rpcproxy.dll web extension. ... server is unavailable" ...
    (microsoft.public.windows.server.sbs)
  • Re: Unable to connect Outlook 2007 to Exchange 2003 Server
    ... The server is a Windows 2003 SBS Premium, ... it tries to autodetect the settings for Exchange. ... "The connection to Microsoft Exchange is unavailable. ...
    (microsoft.public.outlook)
Loading