Guest User!

You are not Sophos Staff.

Thread Info
  • State Not Answered
  • Locked Locked
  • Replies 2 replies
  • Subscribers 5 subscribers
  • Views 1593 views
  • Users 0 members are here
Options
Suggested
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

Keine Verbindung von Outlook mehr an Exchange

Lars90

Hallo Zusammen,

nach dem ich das Userportal so konfigurieren wollte das jeder der in der Domäne ist sich einloggen kann (nach dieser Anleitung ) kann kein Outlook mehr eine Verbindung zum Exchange aufbauen. Das Anmeldefenster kommt, man gibt  Benutzername und Passwort ein die sicher richtig sind gegengeprüft via OWA, und es popt gleich wieder das Anmeldefenster auf. Das geht solange bis man abbricht und die Meldung kommt, dass der Informationsspeicher nicht zur Verfügung ist.

Hat jemand einen Ansatz?

Bin um jeden Rat/Tip dankbar.



This thread was automatically locked due to age.
  • 0

    Hallo Lars,

    Herzlich willkommen hier in der Community !

    (Sorry, my German-speaking brain isn't creating thoughts at the moment. [:(])

    I usually change the port used for the Userportal to 2443.  If that doesn't solve your problem, what do you learn from doing #1 in Rulz (last updated 2019-04-17)?

    MfG - Bob (Bitte auf Deutsch weiterhin.)

     
    Sophos UTM Community Moderator
    Sophos Certified Architect - UTM
    Sophos Certified Engineer - XG
    Gold Solution Partner since 2005
    MediaSoft, Inc. USA
  • 0

    My Exchange experience is dated, because I have only used Exchange through version 2010, but I suspect key things remain the same.

    1) OWA supports two URLs, one for internal connections and one for external connections.  For single-sign-on to work, the connection used by UTM needs to be set to Basic mode.   WAF cannot pass single sign-on information using the other authentication methods.

    2) Assuming that the WAF login uses Active Directory authentication, WAF obtains unqualified names.   You need to ensure that the WAF configuration adds the domain information as a prefix or suffix, or that Exchange is configured to apply the correct domain default.

    If you are using Exchange 2016, this article should help.  There have been similar articles for earlier versions of Exchange

    https://community.sophos.com/kb/en-us/131787

Unfiltered HTML