Forum Discussion
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 some of the users i am facing the issue where the desktop app will not connect to any Audio/Video meeting with the error "Sorry we couldn't connect you". Others it works fine.
The users can join all meeting fine via a browser though.
I have checked event logs and the only error i see when joining a meeting is the 4227 error TCIP .
I have tried reinstall ms teams , restart pc , check drivers nothing.
I havealso tried manual install from downlaoded msi and exe still same issue.
Can anyone pelase help ?
- Hello, I ham experiencing same problem on my work PC, can't connect to a call or can not call anybody. The issue is of Microsoft teams for PC, can call via browser, mobile app.. I did everything except formatting.
Will you care about this kind of issue ?? MS Teams Desktop APP - Sorry we couldn't connect you.how to solve this
We're experiencing the same error for any call from a call queue to some users. If they login to a fresh machine with Teams, then they don't have the problem. We have NOT tried the reg key fix that was suggested here yet. With so many people experiencing, seems like a bigger issues with the Teams desktop client itself.
Kleanthis I have been having this issue non-stop on Windows 7 for a month now. This software worked great for 2 weeks before I started getting this error. The error started showing up every once in a while, and now I cannot call or receive calls from anyone. My current work around is to send a screen share first, then add in audio and disconnect screen share.
FWIW I was able to resolve this for me by Sign Out and back in again. A password change may have affected it. Note that restarting the app was not enough.
FWIW I was able to resolve this for me by Sign Out and back in again. A password change may have affected it. Note that restarting the app was not enough.
This worked great for me, thanks for the advice.
I encountered this today with a user.
He had been on a Teams meeting earlier and had left his Bluetooth speakers on & connected to the laptop.
He got the "Sorry we couldn't connect you" Teams app message when he tried to join a later meeting.
He changed Teams to use system speaker, then he could connect.
He was then able to change Teams to use the Bluetooth speakers.
I suspect that signing out and back in to Teams would have done it too - to use system speakers instead of Bluetooth.
I have had success with the instructions in this article for increasing the TCP/IP port count and increasing timeout values.
https://deploymentresearch.com/fix-for-windows-10-exhausted-pool-of-tcpip-ports/It's also worth checking the network path between Teams clients in the Teams servers. Look for security software and transparent proxies that block or impede traffic.
We have been having this same issue with multiple users were I work. This is what correct the issue for us. Create a .reg file with this info, run Regedit as Admin and import. Perform a reboot and test.
Hope this helps!
Windows Registry Editor Version 5.00
[HKEY_LOCAL_MACHINE\SOFTWARE\Policies\Microsoft\Cryptography]
[HKEY_LOCAL_MACHINE\SOFTWARE\Policies\Microsoft\Cryptography\AutoEnrollment]
"AEPolicy"=dword:00008000[HKEY_LOCAL_MACHINE\SOFTWARE\Policies\Microsoft\Cryptography\Configuration]
[HKEY_LOCAL_MACHINE\SOFTWARE\Policies\Microsoft\Cryptography\Configuration\SSL]
[HKEY_LOCAL_MACHINE\SOFTWARE\Policies\Microsoft\Cryptography\Configuration\SSL\00010002]
"Functions"="TLS_RSA_WITH_AES_256_GCM_SHA384,TLS_RSA_WITH_AES_128_GCM_SHA256,TLS_RSA_WITH_AES_256_CBC_SHA256,TLS_RSA_WITH_AES_128_CBC_SHA256,TLS_RSA_WITH_AES_256_CBC_SHA,TLS_RSA_WITH_AES_128_CBC_SHA,TLS_RSA_WITH_3DES_EDE_CBC_SHA,TLS_ECDHE_RSA_WITH_AES_256_GCM_SHA384,TLS_ECDHE_RSA_WITH_AES_128_GCM_SHA256,TLS_ECDHE_RSA_WITH_AES_256_CBC_SHA384,TLS_ECDHE_RSA_WITH_AES_128_CBC_SHA256"- Did you try the reg edit? It has worked in every instance where we have had the issue.
Kleanthis We have the same error message since one month and still have not any solutions. Someone have success ??
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?
