Announcement

Collapse
No announcement yet.

RPC over HTTPS (TCP/IP tries to connect first... causing delays)

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

  • RPC over HTTPS (TCP/IP tries to connect first... causing delays)

    Hello All,

    I have recently setup RPC over HTTPS for a mate and am a bit bewildered at the length of time it takes for it to kick over to HTTPS and receive the Login Authentication box on Outlook 2003 and Outlook 2007... Using the /rpcdiag switch I have discovered that it tries to connect with TCP/IP first which ofcourse fails miserably because its not on the internal network...

    I have found a 'quick fix' to be clicking "on fast networks, use HTTP first..." but if I do it like that, itll use HTTPS even if it is on the Internal Network which is not ideal.

    My theory is that of the domain name... it is domain-name.com and not the usual domain-name.local that traditional companies usually have.

    So in Outlook it is setup with the
    Exchange Server as "domain-name.com"
    and its RPC URL is "domain-name.com"

    and thus it "resolves" and tries to use TCP/IP first which causes the 1 ~ 2min delay before it decides to use HTTP/S

    Is there any way to fix this and get it working as it should without resolving to changing all the domains over to .local?

    Cheers in Advance!
    Last edited by augrunt; 18th September 2009, 02:01.

  • #2
    Re: RPC over HTTPS (TCP/IP tries to connect first... causing delays)

    tools > account settings > change account
    more settings > connection >

    exchange proxy settings >
    on fast networks connect using http first [tick]
    on slow networks connect using http first [tick]

    that should sort it for you.
    (oops - you alreayd did that)

    Ok here's my other suggestion, and we do this in production environment every day for the following scenario:
    Consultants require access to exchange when in the office, and access to exchange when on sites that do not have direct exchange connections to our servers.
    Solution: RPC/HTTPs.

    Problem: Clients will use RPc/HTTP when in the office.. not ideal as it's probably not as fast.
    Solution: create two profiles. "InOffice" "OutOffice"
    set one as RPc/HTTP configuration. Set the other as no RPC configuration.
    Train user on how to switch profiles as necessary.
    Last edited by tehcamel; 18th September 2009, 04:16.
    Please do show your appreciation to those who assist you by leaving Rep Point https://www.petri.com/forums/core/im.../icon_beer.gif

    Comment


    • #3
      Re: RPC over HTTPS (TCP/IP tries to connect first... causing delays)

      Using HTTP internally isn't a problem. There is almost no performance impact on either the server or the client. I configure all of RPC over HTTPS clients to work that way. Just ensure that split DNS is configured correctly.

      Otherwise the fail back to HTTPS is slow, and there is little that can be done to help. It doesn't help that Outlook is easily confused by home networks in to thinking that a WAN connection is actually a fast connection because all it sees is that the machine is connected to a LAN.

      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


      • #4
        Re: RPC over HTTPS (TCP/IP tries to connect first... causing delays)

        i want comlete book about this
        anybody help me

        Comment


        • #5
          Re: RPC over HTTPS (TCP/IP tries to connect first... causing delays)

          Originally posted by karthick4aus View Post
          i want comlete book about this
          anybody help me
          amazon.com

          Don't hijack threads.
          --
          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


          • #6
            Re: RPC over HTTPS (TCP/IP tries to connect first... causing delays)

            Originally posted by Sembee View Post
            Using HTTP internally isn't a problem. There is almost no performance impact on either the server or the client. I configure all of RPC over HTTPS clients to work that way. Just ensure that split DNS is configured correctly.

            Otherwise the fail back to HTTPS is slow, and there is little that can be done to help. It doesn't help that Outlook is easily confused by home networks in to thinking that a WAN connection is actually a fast connection because all it sees is that the machine is connected to a LAN.

            Simon.
            Thanks for Replying,

            I know it isn't a problem and everything -- thats why I said "I dont like it" because "its not ideal"... I believe the DNS is configured correctly if it manages to work on the Domain's Network and on another network (at another site) and the switching doesn't seem problematic.

            Do you think I should just let it go and go against my gut in thinking that this isn't going to be a problem thats going to bite me in the butt at some point?

            Comment


            • #7
              Re: RPC over HTTPS (TCP/IP tries to connect first... causing delays)

              Originally posted by augrunt View Post
              Thanks for Replying,

              I know it isn't a problem and everything -- thats why I said "I dont like it" because "its not ideal"... I believe the DNS is configured correctly if it manages to work on the Domain's Network and on another network (at another site) and the switching doesn't seem problematic.

              Do you think I should just let it go and go against my gut in thinking that this isn't going to be a problem thats going to bite me in the butt at some point?
              There is little that you can do about it, because Outlook is working as it should. The only thing that could cause you a concern is the slight delay. that isnt' a technical issue, but a user complaint issue.

              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

              Working...
              X