SQL Server 2022 with FQDN login failed

Question

SQL Server 2022 with FQDN login failed

drnorbert

SSC-Addicted

Points: 431
More actions
September 4, 2024 at 3:07 pm

#4454012

I just replaced one of the servers, and all the configurations are done.
The new server can connect to the SERVER NAME but not to the FDQN name, however, the other server will connect to the FDQN from the new server.
Error in the new server when login with FDQN:
Login failed. The login is from an untrusted domain and cannot be used with Integrated authentication. (Framework Microsoft SqlClient Data Provider)
Norbert

Viewing 6 posts - 1 through 5 (of 5 total)

You must be logged in to reply to this topic. Login to reply

Mr. Brian Gale SSC-Insane Points: 24800 More actions · Answer 1

Sounds like an SPN issue. Did you configure the SPN's?

The above is all just my opinion on what you should do.
As with all advice you find on a random internet forum - you shouldn't blindly follow it. Always test on a test server to see if there is negative side effects before making changes to live!
I recommend you NEVER run "random code" you found online on any system you care about UNLESS you understand and can verify the code OR you don't care if the code trashes your system.

drnorbert SSC-Addicted Points: 431 More actions · Answer 2

Yes makes sense! Please advise me on how to figure out if this is the issue and how to resolve it.

Mr. Brian Gale SSC-Insane Points: 24800 More actions · Answer 3

I'm not sure about your response. Did you configure the SPN's or not? If you didn't, I would configure the SPN's. If you have configured the SPN's, then my next guess is that the security cert is not valid or one (or more) machine is not domain joined and as such can't be "trusted".

But SPN's are always my first thing to check when it is a problem with a new server setup as I can't count the number of times that I have forgotten to do that. My IT department doesn't give me (or the SQL Service account) permissions to create or remove SPN's, so I always need to bug them to create/remove SPN's when I spin up a new SQL instance.

The above is all just my opinion on what you should do.
As with all advice you find on a random internet forum - you shouldn't blindly follow it. Always test on a test server to see if there is negative side effects before making changes to live!
I recommend you NEVER run "random code" you found online on any system you care about UNLESS you understand and can verify the code OR you don't care if the code trashes your system.

drnorbert SSC-Addicted Points: 431 More actions · Answer 4

I solved by in Active Directory Users and Compuyters->Domain Contollers->ServerName->Properties->Atrribute Editor

in Atrribute "serviePrincipalName" add:

MSSQLSvc/FDQN

MSSQLSvc/FDQN:1433

Thanks for your advise.

Marimuthu-129612 Hall of Fame Points: 3332 More actions · Answer 5

use SQLCHECK utility ( https://github.com/microsoft/CSS_SQL_Networking_Tools/releases/download/1.0.1422.0/SQL_CHECK.zip )

ref :https://github.com/microsoft/CSS_SQL_Networking_Tools/wiki/SQLCHECK

Download SQL_CHECK.ZIP and extract SQLCHECK.EXE to a folder of your choice, e.g. C:\temp. output txt file will be in same folder. For best results, run this tool on the SQL Server and on the client machine. If using a web-based app, please run on the web server, as well.