ARR + URL Rewrite not working for new exchange Server with ADFSRSS

1 reply

Last post Jun 13, 2019 09:07 AM by Able

  • ARR + URL Rewrite not working for new exchange Server with ADFS

    Jun 12, 2019 10:42 AM|aasimenator|LINK

    Hi,

    I had created a post in the URL rewrite section over 2 hours ago, haven't received any response, i've been troubleshooting since and i think its more of a issue with ARR. 

    So currently when i go to https://mail.bayonetventures.com/owa i no longer get 502 error but what i do get is a 401 error and i am not sure what the issue is.

    So my current config is as following:

    1. 1. EXCH-01 Server Hosts Exchange 2019
    2. 2. ADFS-01 Server hosts ADFS 3.0
    3. 3. BayVL00-DMZ is IIS + WAP/ARR configuration on a different network/VLAN.

    BayVL00-DMZ has ARR configured on port 8443 which is where the port i guess in the log is coming from. So the URL in the log seems to be incorrect should it be 443 or no port at all?

    Log:

    <failedRequest url="https://mail.bayonetventures.com:8443/owa/sessiondata.ashx?appcacheclient=1&amp;acver=15.1.1261.39&amp;crr=1"
    siteId="1"
    appPoolId="DefaultAppPool"
    processId="2624"
    verb="POST"
    remoteUserName=""
    userName=""
    tokenUserName="NT AUTHORITY\IUSR"
    authenticationType="anonymous"
    activityId="{80000027-0000-C900-B63F-84710C7967BB}"
    failureReason="STATUS_CODE"
    statusCode="401"
    triggerStatusCode="401"
    timeTaken="0"
    xmlns:freb="http://schemas.microsoft.com/win/2006/06/iis/freb"
    >

  • Re: ARR + URL Rewrite not working for new exchange Server with ADFS

    Jun 13, 2019 09:07 AM|Able|LINK

    Hi aasimeator,

    According to your description,401 means authentication related error. It seems the ADFS server doesn't seem to get the a client certificate.So I  hope that you could post detail error message and post the  sub status code so it will help us to see the details of error.

    Best Regards

    Able

    Please remember to click "Mark as Answer" the responses that resolved your issue.
    If you have any compliments or complaints to MSDN Support, feel free to contact MSDNFSF@microsoft.com.