I have better luck getting answers here than most all of the Tech. specific forums I visit, so here goes nuttin. VB.NET program connecting to SQL Server via SSPI (NT Security). Parameters: 1 All users must be on a "secure" subnet to be able to access the Server through the firewall. 2 SQL Server is using security account info. from domain SE 3 There can be NO (Zero, zip, zilch, nada) Trust relationships to other domains 4 Cannot use SQL Built in accounts The Scenario: 99% of all person using application X will be logged on to the SE domain. Their account info. will be passed by the application via SQL connection to the SQL server which will then validate if they are allowed to access the data. 1% may be logged on to other domains or even the local machine (these users DO have accounts on the SE domain). Issue: I can trap the error for bad credentials but I have no clue how to go back and allow that 1% to enter their SE credentials and pass them to the SQL server. Anyone with thoughts on how to do this feel free to chip in. I have already tried combining the 2 methods (didn't work) "Integrated Security=SSPI;Persist Security Info=False;Data Source=MyServer;Initial Catalog=MyData;User ID=SE\Fred;Password=Dorfman"