Feedback
Did this article resolve your question/issue?

   

Article

"Login failed. The login is from an untrusted domain and cannot be used with Windows authentication." error

Information

 
Title"Login failed. The login is from an untrusted domain and cannot be used with Windows authentication." error
URL Name000040369
Article Number000162102
EnvironmentProduct: Connect/Connect64 for ODBC SQL Server Wire Protocol driver, Progress DataDirect for ODBC for SQL Server driver
Version: All supported versions
OS: All supported platforms
Database: SQL Server
Application: All ODBC applications
Question/Problem Description
The below error is received when connecting using Kerberos or NTLM authentication
Steps to Reproduce
Clarifying Information
Connection to SQL Server fails using windows Authentication
Cross Domain NTLMv2 Authentication fails with SQL Server
Error Message[DataDirect][ODBC SQL Server Wire Protocol driver][SQL Server]Login failed. The login is from an untrusted domain and cannot be used with Windows authentication.
Defect NumberDefect 60357
Enhancement Number
Cause
  • The domain controller administering the client machine where the driver resides and the SQL Server database machine are different.
  • Domain connection option information is missing
  • Windows NTLM Authentication protocol was upgraded from NTLM v1 to NTLM v2.
  • Extra spaces in the HostName connection option in odbc.ini file.
  • Special characters in the password has been found to result in this error; particularly with Unicode apps.
Resolution
  • Make sure the client is administered by the same domain controller that administers the database server.
  • For Linux/Unix, If specifying the domain name in the "Domain" connection option and the error is still occurring, try specifying the domain name in the loginID connection option with the following format: Domain/user
  • If using AuthenticationMethod=9, check to see if AuthenticationMethod=10 resolves the issue.
  • Make sure there are no extra spaces after the Hostname in the odbc.ini file.
  • Ensure that no special characters are used in the password.
  • Ensure its not an encoded password.

Contact Support for the hot fix and hidden connection option information if the above steps do not work.
Workaround
Notes
Last Modified Date8/19/2021 2:38 PM
Files
Disclaimer The origins of the information on this site may be internal or external to Progress Software Corporation (“Progress”). Progress Software Corporation makes all reasonable efforts to verify this information. However, the information provided is for your information only. Progress Software Corporation makes no explicit or implied claims to the validity of this information.

Any sample code provided on this site is not supported under any Progress support program or service. The sample code is provided on an "AS IS" basis. Progress makes no warranties, express or implied, and disclaims all implied warranties including, without limitation, the implied warranties of merchantability or of fitness for a particular purpose. The entire risk arising out of the use or performance of the sample code is borne by the user. In no event shall Progress, its employees, or anyone else involved in the creation, production, or delivery of the code be liable for any damages whatsoever (including, without limitation, damages for loss of business profits, business interruption, loss of business information, or other pecuniary loss) arising out of the use of or inability to use the sample code, even if Progress has been advised of the possibility of such damages.