Page 1 of 1

SQL ODBC Conn fails

Posted: 8. Mar 2011, 17:41
by OwenW
I have a Windows 7 x64 guest on a Win7x64 host. I am trying to connect to a SQL Server on our network using an ODBC connection. I logged into the guest using my standard development login. I have verified that I can create ODBC connections to the SQL server using this profile on non-VM systems. The SQL Server error log recorded these errors:

- Error: 17806, Severity: 20, State: 14.
- SSPI handshake failed with error code 0x8009030c, state 14 while establishing a connection with integrated security; the connection has been closed. Reason: AcceptSecurityContext failed. The Windows error code indicates the cause of failure. [CLIENT: 10.10.6.187].
- Error: 18452, Severity: 14, State: 1.
- Login failed. The login is from an untrusted domain and cannot be used with Windows authentication. [CLIENT: 10.10.6.187]


I have verified that our DNS server correctly resolves both the IP and name of the guest VM by testing it from the command line on the SQL Server. I have read lots of suggestions on these errors, from disabling Windows firewall (it is) to using SQL authentication only (this works, but is not an option). For some reason, Windows authentication is failing when setting up an ODBC connection to SQL from a Win7 VM, and I am not an Active Directory or network specialist, so I need some help. I cannot understand why the fact that I am using a VM should have anything to do with it. The profile is joined to the domain correctly, as far as I can tell, and the process works just fine from NON-virtual systems. Any suggestions?

p.s.: I did check the Windows Event Viewer on the guest and did not see anything of interest there.

Re: SQL ODBC Conn fails

Posted: 8. Mar 2011, 17:43
by vbox4me2
Try Bridge network mode for the Guest.

Re: SQL ODBC Conn fails

Posted: 8. Mar 2011, 17:48
by OwenW
All my VM's use bridged adapters.

Thanks for the quick response, though!

Re: SQL ODBC Conn fails

Posted: 8. Mar 2011, 19:17
by OwenW
-->> Solved <<--

The issue turned out to be a corrupt profile. After setting up a new profile on the VM, the ODBC connection worked just fine.