While configuring Citrix XenMobile 10.3 at a customer site , “Login failed The login is from an untrusted domain and cannot be used with Windows authentication” error kept coming up whenever trying to setup Microsoft Database using Windows authentication. Customer using SQL AlwaysOn with single domain forest.
Did the following troubleshooting the issue:
SQL service account on AD is not locked.
SQL service account ODBC from a Windows machine using windows authentication is working fine and can connect to DB.
SQL service account has required db_owner permissions on SQL servers.
XM VM can resolve AlwaysOn listener hostname.
SQL servers can ping XM VM.
Local SQL account working fine on XM VM DB configuration.
Password surely being entered correctly in XM VM.
Domain Controller AD servers operational.
Event log on SQL servers not showing any events.
After contemplating the issue for a bit knowing that all troubleshooting steps revealed nothing, I noticed that customer is using a password generator with very long complex passwords. Knowing that XM is hardened Linux and no way to connect to it before finishing initial configuration on top of revealing the password to make sure it is typed correct, I directed the customer for testing purposes to set a bit less complex password for service account and voila it worked .
Without being able to see the entered password , it is impossible to determine if the limitation is actually a mistyped character in the XM VM (tried password about 15 times very slowly 🙂 ) because of keyboard or manual typo or if the hardened Linux XM VM is just not accepting certain characters that are rarely used.
Now trying to change the password after the XM VM is configured and SSH is enabled to make sure pasting is working from putty using the very complex long password generated but then again same error came up.
This is not official information, I have no idea if this is the character number or type limitation but what worked for me is a complex 12 character password with upper,lower,CAPS, and special characters. Eventually the issue was simply the password ..