Home » Uncategories » Error 18452 the Login Is From an Untrusted Domain and Cannot Be Used With Windows Authentication Updated FREE

Error 18452 the Login Is From an Untrusted Domain and Cannot Be Used With Windows Authentication Updated FREE

Error 18452 the Login Is From an Untrusted Domain and Cannot Be Used With Windows Authentication

Recently a user has reported error 18452 while connecting to database server. Full description of this error is given below:

Error: 18452, Severity: 14, State: 1.
Login failed. The login is from an untrusted domain and cannot be used with Windows authentication.

You lot can see the screenshot of the mistake 18452 in below paradigm.

error 18452

Error 18452 – Root Cause

Reason backside error 18452 is because of wrong security authentication mode configuration. SQL Server is set to accept only windows logins to connect to database case.

As we know SQL Server uses ii hallmark modes to take database connections. One is Windows Authentication mode and another ane is SQL Server and Windows Authentication manner. We too phone call it Mixed Authentication style.

Sometimes, SQL Server authentication style is set to SQL Server and Windows Hallmark mode to accept SQL as well as windows connections but all the same you will face up this result. That might exist because y'all endeavour to connect to a server that has E'er on Availability Grouping configuration or database mirroring configuration.

Suppose yous have AOAG configuration and you are connecting to database using chief replica proper name non listener proper name using a login for which default database is ready as availability database. If failover got happen during your activity or you are connecting to secondary replica using a login for which default database is fix every bit availability database then also you will get this fault 18452 along with some SSPI context mistake that I have given below.

Fault: 17806, Severity: 20, Land: 14.
SSPI handshake failed with mistake lawmaking 0x8009030c, state 14 while establishing a connection with integrated security; the connectedness has been airtight. Reason: AcceptSecurityContext failed. The Windows error code indicates the crusade of failure. The logon effort failed

SSPI handshake errors comes because of Kerberos failure, which would nearly likely be related to non-existent SPN or bad SPN for SQL Server.

Solution

To fix this issue first we demand to check the hallmark way set for your SQL Server Instance. If your SQL Server instance is running with windows authentication way and so y'all must alter it to Mixed mode and so that windows and SQL both type of logins tin exist authenticated.

To check the configured hallmark mode for your SQL Server Instance, we need to launch SQL Server Instance belongings window. Correct click at the instance node and click at the properties option as shown in below screenshot.

Launch SQL Server Instance Property Window

One time yous will click at Properties option, you volition be getting beneath SQL Server example belongings window. Click at Security pick from left side pane. You can meet current Server Authentication configuration is set to Windows Authentication mode in below screenshot.

SQL Server Instance Property Window

Now nosotros will change information technology to SQL Server and Windows Authentication fashion . Select the radio push for SQL Server and Windows Authentication mode option and click ok button to continue. You tin can see that I have selected above style to employ the changes.

SQL Server Instance Property Window

Restart SQL Server services to apply the changes.

If your SQL Server Instance is already set up with SQL Server and Windows Authentication fashion then you should fix this effect in carve up fashion. Every bit I described above that one of the probable reason to get this fault 18452 is because you lot might use AOAG replica server proper noun to connect to the database with the login for which default database is set every bit the AOAG availability database.

If failover volition happen then yous would not be able to admission the database considering it will get secondary. Mistake 18452 will exist generated along with SSPI handshake errors because same database is set as default database for your login that has go inaccessible now considering of acting secondary database in AOAG. Failover will non happen for you considering you are using replica server name to make database connection.

Possible solution to set this issue is failback the AOAG to your before primary replica or you should apply AOAG Listener name to brand database connection. Also, to avoid this error during failover you should gear up default database for your login to master rather than availability database.

I hope you lot like this article. Please follow our Facebook page and Twitter handle to go latest updates.

Read More:

Fix Error 18456: Login failed for user "User_Name"
Fix Fault 4064: Cannot open user default database. Login failed
Mistake 53: Could non open a connection on SQL Server
AOAG Listener Error 19471: The handle is Invalid

Author
Recent Posts

Manvendra Deo Singh

I am working as a Technical Architect in one of the summit It consulting house. I have expertise on all versions of SQL Server since SQL Server 2000. I have lead multiple SQL Server projects similar consolidation, upgrades, migrations, HA & DR. I beloved to share my noesis. You can contact me on my social accounts for any consulting work.

Manvendra Deo Singh

Summary

Commodity Name

Gear up Error 18452: Login failed. The login is from an untrusted domain and cannot be used with Windows authentication.

Description

Recently nosotros got a login upshot where one of the SQL user was not able to connect to database instance and was getting error 18452. Full error description of this mistake is given below: Error: 18452, Severity: xiv, State: one. Login failed. The login is from an untrusted domain and cannot exist used with Windows authentication.