This discussion has been locked.
You can no longer post new replies to this discussion. If you have a question you can start a new discussion

Outlook 2019 - MAPI over HTTP, EWS oder ActiveSync - logon required

I would like to use Outlook 2019 for my Clients.

With Outlook 2016 all is fine and the Clients can connect through a XG and talk with my Exchange 2016.
As soon as i switch a Client to Outlook 2019 there is a Addition logon Windows asking the user for Addition credentials.

can anyone help me to find the correct rules for XG 17.5.3 ?

Seems to be the same as in UTM Beta ...
community.sophos.com/.../389080

Thanks in advance

 

Jürgen



This thread was automatically locked due to age.
Parents Reply
  • Hi,

    i spend the day with figureing out, why this still has problems.

    In my last Post regarding this problem, i said it worked.
    I know now, why: I had a Microsoft Direct Access Connection and so the problem didn´t come up.

    I had some problems the last days with Outlook 2019 and VPN/Direct Access.
    I am going to dump MS Direct Access and i am back with the Problem.

    External Outlook 2019 is still asking for logon credential on Windows 10  Enterprise Build 18363

    This is my situation.

    • SFOS 17.5.12 MR-12
    • Windows 10 Enterprise Build 18363
    • Exchange 2016 CU 16
    • SAN Certificate with mail, autodiscover, owa
    • A lot of testing

    I used this documentations

    What i see

    • Outlook / Autodiscover Test, on my external Client need logon credentals entered in the dialog box to function properly.
    • Outlook 2019 keeps asking for logon credentials
    • Microsoft O365 testconnectivity is ok with Mapi over HTTP
    • Microsoft O365 testconnectivity fails at rpc/rpcproxy with error 403. A manual call of the url and with addition logon credential seems fine in IE 11.

    The o365 has some reply from my exchange server 2016.

    • HTTP 403 vorbidden
    • You don´t have permission to access this rescource.

    What am i missing here in my setup?

    has anyone working this Outlook 2019 / Exchange 2016 on-premise?

    I have 2 firewall rules, one for Exchange autodiscover, one for Exchange Webservices 

    thanks

     

    Jürgen

Children