sbrelop.blogg.se

There is another way, which I now use in preference to the runas /netonly method. use the runas /netonly trick with SSMS or Visual Studio.have a jump box inside the VPN that allows you to RDP and use tools connecting directly to the SQL Server machine.have the university add your domain as a trusted domain.have the university allow you to join your machine to the domain.This should work with any application, including Visual Studio. It will look like it is using your local Windows credentials, but it is not. This will prompt you for your password in the remote domain. This fools Windows into launching SSMS as the login you specify, rather than your own (this isn't something you can set in the Connection properties dialog of SSMS, it's how you need to launch SSMS from the command line or a shortcut): runas /netonly /user:domain\username "C:\path_to\ssms.exe" The only workaround I know of is for SSMS (and it works for other apps too, like Plan Explorer and SentryOne), and that's the runas /netonly trick described in this answer. Domain name is still part of the validation - your machine either has to be part of the domain, or the domain your machine is in must be trusted by the school's domain. You also can't just create the same username with the same password in your own domain, and expect that to magically work. This simply isn't how Windows authentication works, and largely defeats the purpose. You are attempting to pass Windows credentials in plain text from the connection string of an application.