We have a customer who is trying to access our database server. The database server accounts require Windows authentication. The problem is the customer's domain is not and cannot be trusted with our domain. The customer wants to communicate to our network using a VPN. Windows authentication passes his network credentials to SQL Server and SQL Server says access denied and provides a NULL connection error message.
Is it possible to create a network account for the customer in our domain and have their VPN connection force a domain login into our network? The hope being that their domain credentials are replaced with our domain credentials.
I'm trying to avoid using SQL Server security, but I don't believe that is possible.
Makes sense. In our case they are trying to run an application and not query analyzer or EM, but it sounds like the same process would be followed.
One problem though may be related to an ODBC connection that is being used with this application. When we setup an ODBC connection a choice must be made between using SQL Server authentication or Windows authentication. If you choose Windows authentication SQL Server will use their domain information and not the credentials we want them to use. Any way around this?