Announcement

Collapse
No announcement yet.

Can't connect to RPC via HTTPS in any way

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

  • Can't connect to RPC via HTTPS in any way

    I gotta say, I am at my wits end. I have thus far spent over 48 solid hours on figuring out why this isn't working and I'm about to start crying ..... Hopefully, someone on this great forum will be able to shed more light on this.

    I have a client running Exchange 2003 STD on Widows 2003 STD. Really plain vanilla with the exception that I have configured FBA and subsequently the "exchange-oma" fix to enable Active Sync.
    I have now also configured Outlook Anywhere but can't connect from "anywhere". I have verified each step of the config, ports, and VDir settings, the cert is through GoDaddy and works beautifully with OWA (not that it really matters though ).

    I have tried browsing to the RPC directory via "https://servername/rpc" as well as "https://FQDN/rpc" and both ultimately give me a 401.3 error. I have run the test at "testexchangeconnectivity.com" and get only one error;

    Attempting to ping RPC Endpoint 6004 (NSPI Proxy Interface) on server host.AD-domain.local
    Failed to ping Endpoint

    Additional Details
    RPC_S_SERVER_UNAVAILABLE error (0x6ba) was thrown by the RPC Runtime


    I can't think of where to go from here, any ideas?

    Thanks in advance,

    E

  • #2
    Re: Can't connect to RPC via HTTPS in any way

    Have you seen if this can help: http://messagexchange.blogspot.com/2...nd-points.html
    Caesar's cipher - 3

    ZKHQ BRX HYHQWXDOOB GHFLSKHU WKLV BRX ZLOO UHDOLVH LW ZDV D ZDVWH RI WLPH!

    SFX JNRS FC U6 MNGR

    Comment


    • #3
      Re: Can't connect to RPC via HTTPS in any way

      Thanks for responding L4ndy, I just finished going through the article and did the mods, looks like this was written for Exchange 2007, although I did try to adapt it for 2003. Still no joy, I began receiving http 401 errors and tried to troubleshoot that. I finally just restarted IIS and ExchangeSA and we are back to square one.

      Any other ideas?

      Regards,

      E

      EDIT - So I also found this article "here"
      and now I'm getting the following from "testexchangeconnectivity.com"

      Testing SSL mutual authentication with RPC Proxy server
      Successfully verified Mutual Authentication
      Additional Details
      Certificate common name host.FQDN.com matches msstd:host.FQDN.com

      Attempting to Ping RPC Proxy host.FQDN.com
      Cannot ping RPC Proxy
      Additional Details
      A Web Exception occurred because an HTTP 401 - Unauthorized response was received from IIS6



      Let me know your thoughts

      E
      Last edited by edvinh; 9th February 2010, 23:20.

      Comment


      • #4
        Re: Can't connect to RPC via HTTPS in any way

        The Exchange-OMA virtual directory has nothing to do with RPC over HTTPS. They are completely independent. Therefore unless you made an error with the configuration and applied something to the entire server, rather than just the virtual directory, it shouldn't have affected anything.

        I would suggest you start by removing RPC over HTTPS proxy from add/remove programs, then removing the two RPC virtual directories from IIS Manager. Run IISRESET to write the change to the metabase. Reinstall the RPC over HTTPS proxy and do the registry settings again, on both the Exchange server and the domain controller.

        Test again.

        There are only three things that go wrong with RPC over HTTPS on Exchange 2003.
        1. Certificate problems - not trusted, name mismatch etc.
        2. Authentication issues - the virtual directory is set for basic and the client for NTLM (Integrated) or vice versa.
        3. Registry settings are wrong.

        That is course presuming that the requirements are met of Exchange 2003 on Windows 2003 with a Windows 2003 DC/GC and Windows XP SP2 or higher and Outlook 2003 or higher.

        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: Can't connect to RPC via HTTPS in any way

          Originally posted by Sembee View Post
          The Exchange-OMA virtual directory has nothing to do with RPC over HTTPS. They are completely independent.
          Thanks Simon, thats what I thought, just wanted someone to reassure me

          Originally posted by Sembee View Post
          I would suggest you start by removing RPC over HTTPS proxy from add/remove programs, then removing the two RPC virtual directories from IIS Manager. Run IISRESET to write the change to the metabase. Reinstall the RPC over HTTPS proxy and do the registry settings again, on both the Exchange server and the domain controller.
          And thanks to your suggestion, I did exactly that;

          1. Uninstalled RPC-HTTP from Windows Components
          2. Backed up IIS and removed both RPC VDir's and reset IIS
          3. Restarted the Server and began the process over again.

          Thanks for suggesting the reinstall, it was really the only thing I hadn't tried. Should have known better

          Thanks again for all of your help.

          Edvin

          Comment

          Working...
          X