Trusted Authentication will use the credentials that you are logged into the machine
with to try and connect, there’s not a way round this, if you want to use
trusted authentication for management studio, you need to be logged on to your
machine with an account that is allowed access to SQL, if not then you will
have to use SQL authentication.
Try this: Use RUNAS to set your Windows Auth domain for database connections
runas /user:domain\user "C:\Program Files\Microsoft SQL Server\90\Tools\Binn\VSShell\Common7\IDE\ssmsee.exe"
runas /user:domain\user "C:\WINDOWS\system32\mmc.exe /s \'C:\Program Files\Microsoft SQL Server\80\Tools\BINN\SQL Server Enterprise Manager.MSC\'"
runas /user:domain\user isqlw
Example:
runas /netonly /user:cricket\mdatta " C:\Program Files (x86)\Microsoft SQL Server\100\Tools\Binn\VSShell\Common7\IDE\ssms.exe"
runas /netonly /user:cricket\mdatta isqlw
Try this: Use RUNAS to set your Windows Auth domain for database connections
runas /user:domain\user "C:\Program Files\Microsoft SQL Server\90\Tools\Binn\VSShell\Common7\IDE\ssmsee.exe"
runas /user:domain\user "C:\WINDOWS\system32\mmc.exe /s \'C:\Program Files\Microsoft SQL Server\80\Tools\BINN\SQL Server Enterprise Manager.MSC\'"
runas /user:domain\user isqlw
Example:
runas /netonly /user:cricket\mdatta " C:\Program Files (x86)\Microsoft SQL Server\100\Tools\Binn\VSShell\Common7\IDE\ssms.exe"
runas /netonly /user:cricket\mdatta isqlw