Error code Connectivity_ICEWarn 0x80020 and Connectivity_ICEWarnEx 0x90

The MS Teams error codes "Connectivity_ICEWarn 0x80020" and "Connectivity_ICEWarnEx 0x9000" relate to ICE (Interactive Connectivity Establishment) issues, which affect real-time communications like calls and meetings. These codes originate from the underlying network protocols used to establish peer-to-peer connections in Teams (and other platforms using similar VoIP technology):

• Connectivity_ICEWarn 0x80020 typically points to DNS resolution problems. This means the Teams client cannot correctly resolve domain names required for setting up communication channels. Such a failure can prevent successful STUN/TURN connections, which are essential for media flow (audio/video/content sharing). The error often results from firewalls or proxies blocking certain traffic, network DNS misconfigurations, or lack of required network routes.
• Connectivity_ICEWarnEx 0x9000 is interpreted as a “malformed” condition in ICE connectivity checks. It may happen if network policies, firewall restrictions, or VPN configurations interfere with how connection candidates are formed and exchanged, or if traffic is intercepted or modified by security devices. This can block or disrupt the connectivity establishment for Teams calls and meetings.

Troubleshooting Tips:

• Ensure your firewall and proxy allow traffic for WebRTC, STUN, and TURN protocols (UDP ports 3478–3481, as well as dynamic media ports and TCP 443).
• Check if NAT traversal is properly configured (especially with company VPNs or networks using strict controls).
• Try Teams on a different network to rule out local restrictions.
• Update Teams and network drivers.

Interpreting Error Codes: Connectivity_ICEWarn 0x80020 & Connectivity_ICEWarnEx 0x90

These error codes are related to Interactive Connectivity Establishment (ICE), commonly used in Microsoft Teams, Skype, and VoIP applications. They typically indicate network connectivity issues affecting real-time communication.

Possible Causes & Fixes:

🔹 Firewall or Proxy Restrictions – Ensure WebRTC, STUN, and TURN traffic is not blocked.
🔹 NAT Configuration Issues – Use a VPN or configure port forwarding for better connectivity.
🔹 Corporate Network Policies – Contact your IT admin to allow the required ports and protocols.
🔹 Internet Connection Issues – Test with another network to identify local connectivity problems.

For more troubleshooting tips, visit:
🔹 https://reminigeek.com
🔹 https://networkvents.org
🔹 https://tmwhts.com

Hi LightInTheDark ,

0x80020 might be related to a DNS resolution failure from the client, e.g. the client is not able from its source network to get name resolution completely right.

And the 0x9000 might mean that it is malformed...

Check out this: 

• https://digitalbamboo.wordpress.com/2013/09/12/how-to-find-lync-ice-connectivity-failure-error-codes/
• https://www.msxfaq.de/skype_for_business/technik/icewarn.htm

• What client are you using? Windows(/Mac/Mobile/Browser/Linux)?
• How many are affected?
• Did you try it from another computer?
• Did you try it from another network, e.g. non-corporate network, test network/direct Internet link/LTE or else?
• Are all Office 365 IPs and URLs in the white listed on the FW and proxies?
• Is the client traffic via the Internet Breakout anyhow intercepted? E.g. fancy FW/proxy features which might break encryption, delay ... etc.