[PSA] Blocked by the 0x89231806 error when using Party Chat on Windows 10? Start here
**Updated 4/1/16: Reformatted and added additional information.**
We've been working with customers to identify the most common PC configuration issues that can result in receiving the `Your network settings are blocking party chat. [0x89231806]` error when trying to use the Xbox App Party Chat feature on Windows 10. We've listed these common issues below, along with their mitigation steps. Also note that these same issues can also cause multiplayer issues in Windows 10 games such as Killer Instinct, #IDARB, and Gears of War (online co-op).
**********************************************************************
**Common Configuration Issues**
**********************************************************************
The most common issues we've identified so far include:
1. The Teredo networking adapter is in a borked state (borked being a highly technical term).
2. Teredo configuration parameters are incorrect.
3. The Windows Firewall has been turned off by internet security software.
4. Internet security software is blocking Teredo traffic.
5. IPv6 and/or Teredo is disabled by an application.
6. Required Windows services are not running, and/or are configured to not auto-start.
7. The PC's date/time settings are incorrect.
8. Home networking routers that block Teredo if the router detects an IPv6 connection.
**Note: Run all of the commands listed from an Admin Command Prompt (right click the Start button, and select 'Command Prompt (Admin)'.**
**********************************************************************
**Borked Teredo Adapter Mitigation Steps**
**********************************************************************
**Update: There is new logic in Windows Insider builds 14291 and higher that include some auto-healing logic for Teredo. If you are seeing that the Teredo adapter on your PC is in an error state, you can try a build from the Windows Insider Slow Ring to see if it will fix this issue automatically.**
You can check the state of Teredo with the following command (run from an Admin Command Prompt):
`netsh interface Teredo show state`
If the output from this command shows that the Teredo adapter is in a disabled state, you can try enabling it with the following command:
`netsh interface Teredo set state client`
If the output showed that the Teredo adapter is in an error state, you may need to force a re-install of the adapter:
1. Disable Teredo with the following command: `netsh interface Teredo set state disable`
2. Clean up any Teredo adapters still showing in Device Manager.
a. Open up Device Manager by right clicking the Start button and select Device Manager.
b. In Device Manager, select View, Show hidden devices.
c. Expand Network adapters.
d. Identify any network adapters that contain the word 'Teredo', such as Teredo Tunneling Pseudo-Interface. Right click these adapters, and select Uninstall.
e. Reboot your PC.
3. Re-enable Teredo with the following command: `netsh interface Teredo set state client`
**********************************************************************
**Incorrect Teredo Configuration Parameters Mitigation Steps**
**********************************************************************
This misconfiguration isn't very common, but we have encountered some issues where the servername value for Teredo was set to a blank or incorrect value. By default, the servername value should be set to `win10.ipv6.microsoft.com`. If you run the following command and see that the servername value is not set to `win10.ipv6.microsoft.com`, you can reset it with the next command.
1. Check the servername value by running: `netsh interface Teredo show state` and look for the value listed after `Server Name :`
2. You can reset the servername value to the default by running: `netsh interface Teredo set state servername=win10.ipv6.microsoft.com`
**********************************************************************
**Windows Firewall Issue Mitigation Steps**
**********************************************************************
It may seem a little counterintuitive, but the Windows Firewall needs to be up and running for Party Chat to work on Windows 10. In almost all cases we've encountered with this issue, the Windows Firewall has been turned off by internet security software and can require an update to the security software to address this issue.
You can check the state of the Windows Firewall with the following command (run from an Admin Command Prompt):
`netsh advfirewall show currentprofile`
In the output, you want the state to be 'ON'. If it's off, you can re-enable the firewall with the following command, but if it was shut off by security software it may be disabled again the next time your PC restarts.
`netsh advfirewall set currentprofile state on`