Teams outbound traffic blocked only on WiFi - No blocks in logs
I have 2 devices that cannot seem to send messages via Microsoft Teams (Enterprise) only when on the WiFi. I have a Firewalla Gold Plus and there are no blocks shown in any of the traffic logs.
Both devices Android, 1 Pixel 8 Pro and 1 Samsung S22 Ultra (both running latest OS)
box version 1.978
app version 1.61.88
cloud instance v3
Nothing but default Active Protect enabled / applied
Any suggestions?
-
I've tried the emergency access, I have flushed DNS cache, Teams cache and all the usual things. I've contacted my ISP who cannot locate or determine any blocks or problems.
This problem also exists on Skype mobile and Hotmail mobile, all of which work when turning off WiFi.
While out of town this past week both my wife and I realized Teams (and Skype) was working while on WiFi so am confident it's something within our FWG router. I just submitted a support request from my Firewalla app on my mobile. Hoping someone can assist in identifying the cause -
I did have it enabled. Turned IPv6 off and everything works! That solved the issue, problem is gone.
Amazing. I've had 2 support sessions with my ISP, multiple tickets into Microsoft with the same BS responses, none of which helped. Firewalla support solved the problem is a few short hours. I am so freaking impressed with your support. THANK YOU.
Yay
-
I had the same issue with sending Teams messages from my phone and seeing the messages I successfully sent from my work laptop connected to a VPN. All other messages were received correctly. I resolved the issue by turning off Unbound DNS.
Is there a way to see logs from Unbound DNS? Perhaps I can add a custom rule to allow this to work and still be able to use Unbound.
-
Issue has crept up again for me. All DNS caching and related features are off. It is only an issue from my phone while connected to WiFi. It works fine on mobile data and other Wi-Fi networks. Also turned off ad blocking and active protect. Nothing in the firewall logs. Currently trying to access modem logs. Annoying issue.
Please sign in to leave a comment.
Comments
10 comments