Forum Discussion

Copper Contributor

Mar 30, 2020

MS Teams Desktop APP - Sorry we couldn't connect you.

Hello all , I want to roll out MS teams to use company wide since we have included in our office365 bundle . I have created a small user test group before company wide push. My issue is that in s...

Iron Contributor

Apr 20, 2020

I have seen this over the last week. Particularly mid Teams meeting.

I see Event ID 4227 then a DNS client event error (1014) about unable to resolve a DNS entry for the Teams infrastructure.

This started happening about a week ago and has increased in severity.

Andrew Matthews

Iron Contributor

Jul 13, 2020

Andrew Matthews

I made a bit of progress on fixing this with a combination of the following.

1) Change the IPv4 / IPv6 preference to use IPv4 first

2) Increase the size of the TCPIP IPv4 socket pool to the maximum size

3) Update devices to Windows 10 2004.

The number of incidents that were being reported by the user base has dropped dramatically. We still get the odd incident on poor network connections (home broadband) but at one point we were getting hundreds of reports a week of this issue occurring.