I am developing a program in .Net and it works great in the development environment. It connects to a few databases (SQL Server) and uses SSPI authentication to do so. When I move this program local to the server that actually runs the SQL Server and run it on the same account I was testing with (i.e. I'm sure the permissions are good) it throws an error saying it can't validate the login due to the login coming from an untrusted domain.
In the past I have worked around this by using SQL Logins in the connection string instead, but I'm tired of using this dirty hack and I want to get to the bottom of why my account can't connect to a database when the program is executed on the same server.
I'd be happy to provide any other details necessary to solve this problem, but I have a feeling it might be something simple that I am unaware of.
The environment is Windows Server 2008, running a .NET 4.0 application and trying to connect to SQL Server 2012.