Teams Issues

wc2l

I'm confused (nothing new).
when I open Teams, it tells me I'm connected. If I call someone I get either not connected to the internet or not available.
If I do NetworkAssessmentTool.exe /qualitycheck
I get a lot of:
Please ensure your firewall allows connections to the following domains: *.ng.msg.teams.microsoft.com
They all failed.
Please ensure your firewall allows connections to the following domains: *.flightproxy.teams.microsoft.com
They all failed.

I can keep going, but all the same results.

I have NO idea what is blocking my access. No one can reach me and I can't get out to anyone. This was not an issue when I first converted from Skype to Teams. Teams first worked. I don't think I have changed anything in my setup.

I just wiped, cleaned and installed Teams from the MS Store. I have to wait to see if I can connect tomorrow. Anything blocking Teams from working? How do I toubleshoot this issue??

SteveITS

@wc2l Whst makes you think it’s pfSense related? (Serious question)

Is IPv6 working?

wc2l

@SteveITS
I have not used IPv6, Verizon FIOS had not implemented it when I started with them, Today, I see that it has started. I would not think MS Teams requires IPV6. I may have to look at learning how to set it up. Definitely don't have any of the rules setup for IPv6

So, since a couple of friends can use Teams over a standard home connection and I can't. My first guess it is that my network is the issue. I have installed/uninstall, tried multiple devices.

When I tried to run the Teams Network Assessment Tool, all I got was failure. I have been reading the forums and online. IPv6 is a hit and miss. I have a gateway, but not IPv6 on the WAN side. So I doubt that is it.

If you have other suggestions, I would love to troubleshoot.

SteveITS

@wc2l I asked about IPv6 because twice recently I’ve seen cases where it isn’t working properly and Outlook takes a long time to open and/or can’t connect, or clicking links in Outlook takes like a minute to open the page in a browser. As it (presumably) tries IPv6 and times out. I don’t usually use Teams though.

wc2l

@SteveITS
I had IPv6 disabled. I did attempt to turn it on (no idea what I'm doing) with it. I will shut it back off. I've just getting frustrated with the simple stuff just crashing. I'm starting to think going back to simple is better (not really)

Gertjan

@wc2l

I've installed and the run the "NetworkAssessmentTool.exe /qualitycheck" also.
It probably uses host names, resolves them to 'A' = IPv4 even if IPv6 is available.
Maybe the "team.microsoft.com" host names have no IPv6 counterpart.

On a pretty default pfSense there are no error.
Possible issues :
Broken DNS or package that filter DNS requests, or "Suricate" or "Snort'.

wc2l

@Gertjan
If I go to Diagnostics/DNS Lookup
teams.microsoft.com works just fine.
Host "msg.teams.microsoft.com" could not be resolved.
I had cloudflare and google for DNS servers. I took them out.
Have to wait for someone to test teams. (not like the old workdays)
I like retirement better ;-)

Gertjan

@wc2l said in Teams Issues:

teams.microsoft.com works just fine.
Host "msg.teams.microsoft.com" could not be resolved.

Same for me.

edit : while waiting, read also C:\Program Files (x86)\Microsoft Teams Network Assessment Tool\Usage.docx - this is a Microsoft tool with a manual / notice .... ( )