18452: Login failed. The login is from an untrusted domain and cannot be used with Windows authentication
SQL ServerWhat does it mean?
A Windows authentication login attempt was rejected because it came from an untrusted domain (or Windows authentication was used where SQL authentication is required). The server does not trust this identity.
Why does it happen?
The client is connecting with a Windows identity from a domain/workgroup SQL Server does not trust; the machines are in different/untrusted domains; Kerberos/SPN configuration is wrong; or the connection string uses Integrated Security when SQL authentication is expected. A SQL login attempt while mixed mode is disabled shows a similar symptom.
How to fix it
If SQL authentication is required, switch the server to Mixed Mode and use a user name/password in the connection string (Integrated Security=false). If Windows authentication is required, verify the domain trust and the DNS/Kerberos SPN configuration. Make sure the client and server are in the same or a trusted domain. Narrow down the cause with the 'state' value in the error log.
More from this engine
- 1204The instance of the SQL Server Database Engine cannot obtain a LOCK resource
- 3906Failed to update database because the database is read-only
- 15023User already exists in the current database
- 605Attempt to fetch logical page belongs to a different allocation unit
- 4922ALTER TABLE ALTER COLUMN failed because one or more objects access this column
- 7202Could not find server 'name' in sys.servers
- 40501The service is currently busy. Retry the request after 10 seconds