locked
Exchange 2016 redirection of Client Access requests RRS feed

  • Question

  • Hi together,

    I would like to understand under which condition a Exchange 2016 server NOT proxy a client request to the proper mailbox server and perfrom a redirection?

    As I understand most usuall the CAS componente proxy the request to the users mailbox server. What in detail are the conditione for doing the rediect f the request? 

    TechNet tells:

    In some cases, the Client Access server might redirect the request to a more suitable Client Access server, either in a different location or running a more recent version of Exchange Server.

    Thanks a lot

    Max

    Friday, September 30, 2016 1:42 PM

Answers


  • Hi

    So for as the matter of NOT proxy the request to the right mailbox server, there are many reasons in which redirection and proxy NOT properly handled to the correct mailbox.

    Let understand first:-

    • After a user has authenticated to an internet facing CAS server, the CAS server attempts to locate the location and version of the users mailbox.

    • If the user is local, the mailbox is rendered.

    • If the user is NOT local, then use the AD Routing information supplied by the “Microsoft Exchange Active Directory Topology” service to locate a CAS server in the site hosting the user’s mailbox. If an external URL is configured on the CAS server in the second site, then silently redirect to the URL available or redirect the user to the link supplied. If the external URL is NOT specified, and an internal URL exists, & the authentication method on the virtual directory is set to windows integrated, then proxy the request.

    Not Proxy and Redirection due to these reasons.

    • Incorrect URLs point to the desired servers

    • Autodiscover URLs pointing to the wrong mailbox server

    • IIS Virtual Directories miss configurations

    • Legacy versions of Exchange URLs incorrect configurations

    • IIS Authentication Methods

    • Mis-configuration of DNS and Name Spaces internal and external in exchange

    Further you can troubleshooting the proxy and redirection issues by using https://testconnectivity.microsoft.com/ to further dig out the issues.

    Hope this will help.

    Kindly click "Mark as Answer" on the post that helps you, this can be beneficial to other community members reading this thread.

    Regards.

    H.shakir



    • Edited by H Shakir Friday, September 30, 2016 3:54 PM
    • Marked as answer by Max Kaiser Tuesday, October 4, 2016 7:47 AM
    Friday, September 30, 2016 3:53 PM

All replies

  • The TechNet info pretty much says it - if you are connected to a server with an older CU, it might redirect you to a server that's more up-to-date to connect to your mailbox; or if you are in one Active Directory site and your mailbox is in another, you might get redirected to a server in the other site.

    Will Martin ...
    -join ('77696c6c406d617274696e2d66616d696c6965732e6f7267' -split '(?<=\G.{2})' | ? { $_ } | % { [char][int]"0x$_" })

    • Proposed as answer by Lynn-Li Monday, October 3, 2016 9:01 AM
    Friday, September 30, 2016 2:22 PM

  • Hi

    So for as the matter of NOT proxy the request to the right mailbox server, there are many reasons in which redirection and proxy NOT properly handled to the correct mailbox.

    Let understand first:-

    • After a user has authenticated to an internet facing CAS server, the CAS server attempts to locate the location and version of the users mailbox.

    • If the user is local, the mailbox is rendered.

    • If the user is NOT local, then use the AD Routing information supplied by the “Microsoft Exchange Active Directory Topology” service to locate a CAS server in the site hosting the user’s mailbox. If an external URL is configured on the CAS server in the second site, then silently redirect to the URL available or redirect the user to the link supplied. If the external URL is NOT specified, and an internal URL exists, & the authentication method on the virtual directory is set to windows integrated, then proxy the request.

    Not Proxy and Redirection due to these reasons.

    • Incorrect URLs point to the desired servers

    • Autodiscover URLs pointing to the wrong mailbox server

    • IIS Virtual Directories miss configurations

    • Legacy versions of Exchange URLs incorrect configurations

    • IIS Authentication Methods

    • Mis-configuration of DNS and Name Spaces internal and external in exchange

    Further you can troubleshooting the proxy and redirection issues by using https://testconnectivity.microsoft.com/ to further dig out the issues.

    Hope this will help.

    Kindly click "Mark as Answer" on the post that helps you, this can be beneficial to other community members reading this thread.

    Regards.

    H.shakir



    • Edited by H Shakir Friday, September 30, 2016 3:54 PM
    • Marked as answer by Max Kaiser Tuesday, October 4, 2016 7:47 AM
    Friday, September 30, 2016 3:53 PM
  • Proxy – when Exchange 2016 server contact “other sources” (other Exchange servers) for retrieving data or information on behalf of his Exchange clients, we describe this process as Proxy.
    Redirect- When the Exchange 2016 server “inform” his client, that he cannot help them, and he needs to point them to “other Exchange servers,” we describe this procedure as Redirect

    By default, Exchange  2016 server will prefer to use the option of: “Proxy” instead of the “redirection” option because the Proxy process is transparent to the Exchange client.

    In reality, the proxy process could be considered as a complicated or complex process, but, from the “Exchange client” point of view, this process is transparent.
    The only thing that the Exchange clients need to know is that he needs to locate and contact the Exchange  2016 server.

    for deep dive you can check here : https://blogs.technet.microsoft.com/exchange/2015/10/30/client-connectivity-in-an-exchange-2016-coexistence-environment-with-mixed-exchange-versions/


    Dinesh Singh https://ucservice.blogspot.com

    Friday, September 30, 2016 4:19 PM
  • Hi together,

    I would like to understand under which condition a Exchange 2016 server NOT proxy a client request to the proper mailbox server and perfrom a redirection?

    As I understand most usuall the CAS componente proxy the request to the users mailbox server. What in detail are the conditione for doing the rediect f the request? 

    TechNet tells:

    In some cases, the Client Access server might redirect the request to a more suitable Client Access server, either in a different location or running a more recent version of Exchange Server.

    Thanks a lot

    Max

    If you are using UM, SIP traffic is always redirected, not proxied.


    Blog:    Twitter:   

    Friday, September 30, 2016 6:57 PM