Announcement

Collapse
No announcement yet.

Problem with RPC over HTTP

Collapse
X
  • Filter
  • Time
  • Show
Clear All
new posts

  • Problem with RPC over HTTP

    I have an office with a number of users using Outlook 2007 with RPC over HTTP to connect to a remote Exchange 2003 server. Most of the clients connect without issue. But there are two machines that will not connect via Outlook/HTTP to the server without the VPN connection being active.
    I have installed the same certificate on these two PC's as all the others. In IE, they can connect to OWA without any certificate warnings. However, when trying RPC over HTTP rpcdiag.exe simply indicates that the computers are trying to connect and then simply disconnect. When the VPN is active the status of the connections in rpcdiag.exe indicates the client is connected via TCP/IP (which one would expect), not HTTP.
    I have noticed, and I don't know if this is pertinent, that the installed certificate seems slightly different than the certificate that is used for OWA. The installed certificate has an expiry date of 2009. However, when I investigate the certificate in IE that is generated for the OWA session the expiry date is earlier than that of the installed certificate. I've tried to install the OWA cert but it doesn't appear in the cert authority, I assume because the name is the same as the cert I had previously installed.
    One more oddity is that occassionally when Outlook RPC over HTTP is started a certificate warning appears. The name on the certificate warning is different on the two computers but follows the format: autodiscover.blahblah.com
    Any ideas why these two machines won't connect?
    Thanks.
    Last edited by Kevindv10; 16th April 2007, 21:07.

  • #2
    Re: Problem with RPC over HTTP

    Autodiscover is part of Outlook 2007 for use with Exchange 2007. It configures Outlook automatically.
    Are you using a wildcard certificate?
    Is the SSL certificate a home grown certificate or a purchased certificate?
    If the dates on the certificate are different then they are different certificates.

    Simon.
    --
    Simon Butler
    Exchange MVP

    Blog: http://blog.sembee.co.uk/
    More Exchange Content: http://exchange.sembee.info/
    Exchange Resources List: http://exbpa.com/
    In the UK? Hire me: http://www.sembee.co.uk/

    Sembee is a registered trademark, used here with permission.

    Comment


    • #3
      Re: Problem with RPC over HTTP

      I don't believe its a wildcard certificate, but it was generated inhouse, on the server. I'm contracted to work at a remote location (remote to the server, that is) and don't have access to the server myself. I neglected to mention that the server is running Exchange 2003.
      What's really curious is that a dozen other computers work fine, while only two are having apparent certificate issues. Could a certificate from a completely different site be creating a conflict?
      Last edited by Kevindv10; 18th April 2007, 01:05.

      Comment


      • #4
        Re: Problem with RPC over HTTP

        When it comes to certificates that are home grown, all sorts of odd things happen. I gave up trying to deploy anything with Exchange using home grown certificates many years ago. When you can get SSL certificates for US$20 it doesn't make sense for me to spend many hours trying to get something to work.

        My recommendation to you would be to swap the home grown certificate for a purchased one.

        Simon.
        --
        Simon Butler
        Exchange MVP

        Blog: http://blog.sembee.co.uk/
        More Exchange Content: http://exchange.sembee.info/
        Exchange Resources List: http://exbpa.com/
        In the UK? Hire me: http://www.sembee.co.uk/

        Sembee is a registered trademark, used here with permission.

        Comment


        • #5
          Re: Problem with RPC over HTTP

          We have a home grown cert, it works fine with outlook 2003 and 2007...

          It is true, that I spent about 2-3 hours more, but it was worth it...

          Comment

          Working...
          X