Consider the following scenario:
- You try to install a Web Services on Devices (WSD)-based device on a computer that is running Windows 7.
- You are using IPv6 link-local addresses on the computer.
- You are using SSL certificates to encrypt the communication.
- The value of the CN attribute of the certificate is the IP address of the server.
This problem occurs because Windows incorrectly adds the scope address to the IPv6 address when Windows checks the certificate's CN attribute for authenticity. Because the CN attribute does not (and should not) have a scope ID, this check fails. This causes the connection to be reset.
To work around the issue, use one of following methods:
- Use the host name instead of the literal IP address for the CN attribute on a SSL certificate.
- If you are working in a test environment and have only one device that is communicating with the Web Services on Devices (WSD)-based device, you can set the certificate's CN value to the IPv6 address together with the scope ID.