# Windows player v2-R200 can't connect to SNI-hosted CMS

**URL:** https://community.xibo.org.uk/t/windows-player-v2-r200-cant-connect-to-sni-hosted-cms/20047
**Category:** Get Help
**Created:** [August 27, 2019, 10:14pm UTC](https://community.xibo.org.uk/t/windows-player-v2-r200-cant-connect-to-sni-hosted-cms/20047 "2019-08-27T22:14:05Z")
**Posts on this page:** 1
**Showing post:** 2

<div class="post-metadata">

### Author: ![alex](https://community.xibo.org.uk/user_avatar/community.xibo.org.uk/alex/32/5782_2.png) [@alex](https://community.xibo.org.uk/u/alex)
#### Post date: [August 28, 2019, 7:13am UTC](https://community.xibo.org.uk/t/windows-player-v2-r200-cant-connect-to-sni-hosted-cms/20047/2 "2019-08-28T07:13:41Z")

</div>

Thanks for your post

The Windows Player definitely connects to an SNI-enabled host, so that isn’t the issue.

I think it’s far more likely to be AWS denying TLS 1.0 connections. Windows by default doesn’t offer TLS 1.2 even though it’s quite capable of doing it.

Try enabling that, and I think you’ll find that will solve it:

> [@Enable TLS 1.2 / Strong Crypto in Windows .net Player](https://community.xibo.org.uk/t/enable-tls-1-2-strong-crypto-in-windows-net-player/7091):
>
> By default, the Windows .net Player uses the standard crypto libraries provided by the Microsoft .net Framework. If you need to use a CMS that provides only TLS 1.2 connections, then you will need to ensure you set the following registry settings: 32 bit machines Key: HKLM\SOFTWARE\Microsoft\.NetFramework\v4.0.30319\SchUseStrongCrypto Type: DWORD Value: 1 64 bit machines Key: HKLM\SOFTWARE\Wow6432Node\Microsoft\.NetFramework\v4.0.30319\SchUseStrongCrypto Type: DWORD Value: 1 Original post th…

---

_[View the full topic](https://community.xibo.org.uk/t/windows-player-v2-r200-cant-connect-to-sni-hosted-cms/20047)._