Announcement

Collapse
No announcement yet.

RPC over HTTPS...

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

  • RPC over HTTPS...

    our organization doesnt have much need for RPC, but i want to implement RPC for a few users off-site...

    i think everything is configured correctly, but its the settings for outlook that i think im having trouble with.

    OWA is served from my FE. it also provides an activesync portal for the smart phone users, which all works without a problem.

    when i try to create an RPC outlook profile, it fails and cannot connect with the exchange server...

    my OWA is https://owa.mydomain.com/exchange

    but when i put this in, it prompts for creds, but they fail.

    the portion i dont understand is the name space with the SSL certs, and i think that is the problem...

    my SSL is issued to owa.duvalclerk.com, but the servers name is coc-wpa.duvalflclerk.com. duvalflclerk is the internal domain, and duvalclerk.com is the external.

    so how do i configure the msstd line in the outlook client? im thinking this is the problem... but im not sure.

    thanks guys,
    J_$

    ***EDIT***

    so i tried to set it up internally, and everything works fine inhouse without the msstd: line. just thought i might let ya know...
    Last edited by James Haynes; 30th April 2007, 20:05. Reason: additional information
    its easier to beg forgiveness than ask permission.
    Give karma where karma is due...

  • #2
    Re: RPC over HTTPS...

    i hate to bump things, but i still wanted to know if anyone has a more detailed explaination of the outlook configuration for RPC when the certs dont match...

    i can get it to work inhouse, but i cant get it to work outside the office. OWA, OMA, and activesync all work with no problem. i just dont understand what outlook wants to see.

    thanks again...

    J_$
    its easier to beg forgiveness than ask permission.
    Give karma where karma is due...

    Comment


    • #3
      Re: RPC over HTTPS...

      Have you followed the instructions here? http://www.petri.com/configure_outlo..._over_http.htm

      Have you configured the router to port forward 25, 80 & 443?

      Use a laptop that is configured to use Exchange internally (and that works) then take it external and follow the above instructions in the link.
      1 1 was a racehorse.
      2 2 was 1 2.
      1 1 1 1 race 1 day,
      2 2 1 1 2

      Comment


      • #4
        Re: RPC over HTTPS...

        thank you biggles77.

        thats a decent start. never thought to take one configed inside to outside... good call.

        i did look at the article, but i was curious about the section:
        Further note on SSL: When you purchase/issue your Digital Certificate for the SSL-protected website, you MUST make sure that the COMMON NAME on the certificate is 100% identical to the External FQDN you've just typed!
        they dont match, and im not using a trusted CA... its just generated by my DC/CA. im not too clear on this part.

        will report.

        thanks B!
        its easier to beg forgiveness than ask permission.
        Give karma where karma is due...

        Comment


        • #5
          Re: RPC over HTTPS...

          Originally posted by James Haynes
          my OWA is https://owa.mydomain.com/exchange
          but when i put this in, it prompts for creds, but they fail.
          Are you using the format domain\username when you try and logon or have you used the the trick that inserts the Domain Name when using FBA?
          1 1 was a racehorse.
          2 2 was 1 2.
          1 1 1 1 race 1 day,
          2 2 1 1 2

          Comment


          • #6
            Re: RPC over HTTPS...

            mang! it works...

            the first thing i did was import the cert to my trusted root CAs list to stop the nag.

            from outside i opened a browser and went to:
            https://owa.mydomain.com/rpc

            this gave me a 403.2, which is what i wanted to see... (cause your requesting a read on an execute-only folder, right?)

            then it was just a matter of configuring the outlook client correctly. while at the https://owa.mydomain.com/rpc page, i checked the cert name and made sure it matched the client. then the same entry was placed in the "mutually auth.." box with the "msstd" line and bang! it works.

            thanks again B. id have to work in data entry if it wasnt for you guys...

            j
            its easier to beg forgiveness than ask permission.
            Give karma where karma is due...

            Comment

            Working...
            X