Forum Discussion
MS Teams Desktop APP - Sorry we couldn't connect you.
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.
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.
Andrew Matthews Hi Andrew, if you are using a VPN the IP address is constantly changing each time you connect. How do you enter in the IP address for IPv4 with IP address changing?
TechEng The web services for Microsoft Teams use a defined range of IP Addresses. There is a public document with the ranges on docs.microsoft.com.
If you are talking about changing the TCP/IP port ranges. That should be a standard part of your build on Windows 10. The settings in the link that I provided do not hard set the client IP address, they change the dynamic port ranges to maximise the number of ports available.
