Hello,
We are having some problem with the WAF configuration with our Outlook clients.
As soon as we enable the WAF for our Exchange Server, some users are being prompted for a username/password in Outlook.
Those users are connected into our LAN, so the activation of the WAF shouldn't pose any problems.
The problem happens with some users having mailboxes on the local Exchange server, and also - which is very strange - with ALL users that have a mailbox on Office 365.
So, for some reason, the WAF is interfering with Outlook 365 and also with Outlook and our Exchange Server.
We have captured the packets when launching Outlook with and without the WAF using WireShark, and we noted a difference in the DNS Requests. With the WAF activated our Outlook 365 users try to make a DNS resolution on a SRV record which doesn't exist (_kerberos._tcp.dc._msdcs.office365domain
.com).
Can you help us with this problem ? It is very important for us to use the WAF.
Thank you
Regards
This thread was automatically locked due to age.