Login to SQL, using Windows 7, SQL Server Error 18452, "Login failed. The login is from an untrusted domain ..."
-
Sunday, August 22, 2010 8:42 AM
I have a File/Sharing Server which is Server 2008 SP2 and SQL Server 2008 is installed on it.
My system which is on the same workgroup, was running Windows 2003 Server, which I have saved Server 2008 login credential on it and used that credential to login to SQL Server on Server 2008 system in Windows Authentication mode using SQL management studio.
Recently I installed Windows 7 on that system, and I have also saved that Server 2008 credential in Windows 7 Credential Manager.
The problem is here when I want to login in Windows Authentication mode using SQL management studio like past, and I will get below Error:Cannot connect to [SERVER]
Login failed. The login is from an untrusted domain and cannot be used with Windows authentication. (.Net SqlClient Data Provider)
Error Number: 18452
Severity: 14
State: 1
Line Number: 65536I tried that registry solution (DisableLoopbackCheck=0x01 this thread), but no luck with that.
I have checked the outgoing packets when I click on connect, and I found out that SQL management studio tried to send my local windows credential instead of Server 2008 saved credential.I don't want to login in SQL Mode, and also I don't want to convert my server to Domain controller.
Is there any other solution with this issue?
Regards
All Replies
-
Monday, August 23, 2010 12:23 AM
Please try the workaround advised on Making SQL Server Management Server work on Windows Vista
by creating shortcut as follow;
C:\Windows\System32\runas.exe /netonly /user:domainx\myusername
"C:\Program Files\Microsoft SQL Server\100\Tools\Binn\VSShell\Common7\IDE\ssms.exe"
Sivaprasad S http://sivasql.blogspot.com Please click the Mark as Answer button if a post solves your problem!- Marked As Answer by Mahyar.FF Monday, August 23, 2010 8:27 AM
-
Monday, August 23, 2010 8:29 AM
by creating shortcut as follow;
C:\Windows\System32\runas.exe /netonly /user:domainx\myusername
"C:\Program Files\Microsoft SQL Server\100\Tools\Binn\VSShell\Common7\IDE\ssms.exe"
Thanks, it works perfectlyBut, is there any way to prevent prompting for password?
for example forcing it to read the password from Windows Credential Manager.Edit: /savecred does not work with /netonly at the same time.
Regards
-
Sunday, January 30, 2011 7:53 PM
For anyone else that runs accross this issue and doesn't want to uset he hack/fix the following worked for me in windows7:
1. Go to Windows Credential manager
2. Add a windows credential (if there isn't already one pointing to your server)
3. At Internet or network address type: <ServerName or address>:1433 (assuming you are using the default port)
4. UserName = User account created on your server for SqlAccess
5. password = obviously the password associated with the UserName
Done.
-
Wednesday, September 21, 2011 11:27 AM
Thank you very much Arsine!
I had this problem and adding the PORT Number after the FQDN - This is usuall 1433 but will be differnt for named instances
In XP you did not need to add the PORT for User Accounts - Manage Passwords
Paul

