Credential Manager Wildcard Credential with DNS Suffix in Adapter Setting

I have a credential stored in the credential manager for a wildcard domain (*.example.com). I've also added example.com to the IPV4 and IPV6 Advanced TCP/IP settings to automatically append that suffix. Trouble is, when I try to access a file share like \\something, rather than \\something.example.com, I'm still prompted for my credentials. It seems that even though challenge-response is still happening, but that Windows isn't checking my credential store for those creds. Any thoughts or ways to resolve this?

Solution 1:

This is an old problem with Windows, perhaps related to the way that the certificate is checked. There is no information coming from Microsoft, but it is thought that Windows checks that the "Common Name" of the certificate matches the Fully qualified domain name (FQDN).

If this assumption is correct, there's no solution that uses wildcards, except for fully qualifying the server-name.