Solution to strange "Trusted Connection" error.
I was having trouble connecting to a remote SQL Server instance using Windows Authentication. I was getting the apparently famous "Not a Trusted Connection" error, (apparently famous because of the number of results google turned up) but none of the standard solutions such as allowing mixed-mode authentication in SQL Server were the culprit.
My problem was further compounded by the fact that I could log in to this server using NT Authentication from any other machine in the domain. The issue was specific to my development computer--not my domain account or any other setup issue with SQL Server.
My network admin did some research on the problem and discovered a that Windows XP (my development OS) stores some login credentials in a local cache, and that that cache can sometimes be corrupted, or out of sync with the rest of the domain. A quick search of the event viewer revealed that I was getting Kerberos exceptions when attempting a connection to that server. The Event Viewer showed the following message:
"There were password errors using the Credential Manager. To remedy, launch the Stored User Names and Passwords control panel applet, and reenter the password for the credential ********."
A quick perusal of the control panel revealed no such tool (not sure why it wasn't there--but it wasn't).
I found this article to tell how to run the tool. I modified the password stored in XP, and then I was able to access the server from my development machine.
Kudos to my network admin who found this obscure networking issue!