Weird Issue with Microsoft Teams

Hello,

I am having trouble diagnosing this particular issue with Microsoft Teams. The messaging function isn't working as messages aren't sent ("Failed to send" error message). After checking the web filtering logs, i found this out: 

 

2019:03:13-09:12:20 utm-bomare-2 httpproxy[6214]: id="0002" severity="info" sys="SecureWeb" sub="http" name="web request blocked" action="block"

method="CONNECT" srcip="192.168.1.168" dstip="40.74.62.125" user="" group="" ad_domain="" statuscode="500" cached="0"

profile="REF_HttProContaInterNetwo (VIP_Profile)" filteraction="REF_HttCffVipwhfilte (VIP_WHFilterAction)"

size="517" request="0x1b020c00" url="emea.ng.msg.teams.microsoft.com/" referer="" error="Connection timed out" authtime="0" dnstime="2"

cattime="128" avscantime="0" fullreqtime="127255911" device="0" auth="0" ua="" exceptions="application" category="122" reputation="neutral"

categoryname="Instant Messaging" application="micrsoft" app-id="1151"

 

Apparently, the request was blocked because of a connection time out error. I don't have AV scanning enabled on any of my filter actions. I tried skipping the proxy, same thing. I even disabled web filtering and application control, still same problem. Could it be a DNS issue? (we don't have an internal DNS server, we're using the UTM as gateway and DNS).

Any suggestions?

  • In reply to BAlfson:

    Thank you for the reply. 

     

    I will check it out and get back to you as soon as i can.

  • In reply to BAlfson:

    Ok so i just went through the DNS best practices article and the thing is, we don't have any internal DNS servers, everything is just forwarded to the UTM and our Office365 subscription is cloud-based. However, i did find out from point #8 that disabling Pharming Protection on the Fitlering Options > Misc tab does the trick! Could it be an ISP problem? 

  • In reply to Zak_B18 DZ:

    Is it okay if i leave Pharming Protection unchecked?