I am experiencing a
"Target principal name is incorrect" error after upgrading SQL Server 2016 to 2017. The SQL Server 2016 instance has been uninstalled. The certificate which is registered in SQL Server Configuration Manager Protocols and is used to enable wire encryption is named with the FQDN of the server. It is the exact same certificate that was working successfully with SQL Server 2016.
I have noticed since the upgrade that I cannot logon to SQL Server 2017 using the FQDN of the server. I can only logon using
[HOSTNAME]\[INSTANCE_NAME]. Why has this behaviour changed and how can it be restored? I am wondering whether restoring this behaviour will simultaneously resolve this connection error.