Windows Authentication in another domain via SSMS

Question

Windows Authentication in another domain via SSMS

mTBCent

SSChasing Mays

Points: 652
More actions
April 17, 2018 at 1:37 am

#410425

Hello,
I have a strange problem trying to enable log in with a domain SQL user, with Windows Authentication, from SSMS running locally but in another domain. On the destination domain the users are properly grouped and SQL Logins are created for all of them on the SQL Server instances. The SQL Logins are mapped to the domain users and access is allowed using Windows Authentication. It functions just ok when the user is logged remotely to the server and access the instance using Windows Authentication.
But we need to use these domain users for to access the remote SQL server from our local PCs, that are in another domain than the destination one. Between the two domains we can't add a trust relationship, so the only possible solution is to run SSMS as the destination domain user name via a special shortcut and login with Windows Authentication for the SSMS to think that we are logging with the correct domain user. It functions, but it is very, very slow. When the connection to the server is initiated it is so slow that it is not possible to work that way for any developer. Each operation is very slow and I can't find why.
Do you please have some suggestion on what is this happening and why SSMS is so slow when it is run with domain user (from another domain) and a connection is done to a server with Windows Authentication?
Thanks in advance,
Tomi

Viewing 3 posts - 1 through 2 (of 2 total)

You must be logged in to reply to this topic. Login to reply

andreas.kreuzberg SSCertifiable Points: 6191 More actions · Answer 1

Hi,
we start our ssms with a command line, to connect to different sql server in different domains.
But this is not slow, and it feels like you work local on the sql server

We start the ssms like this:

runas /netonly /user:YOUR_DOMAIN\YOUR_USER "C:\Program Files (x86)\Microsoft SQL Server\140\Tools\Binn\ManagementStudio\Ssms.exe"

Maybe this is different to the gui " run as different user"

Best regards,
Andreas

mTBCent SSChasing Mays Points: 652 More actions · Answer 2

andreas.kreuzberg - Tuesday, April 17, 2018 5:59 AM
Hi,
we start our ssms with a command line, to connect to different sql server in different domains.
But this is not slow, and it feels like you work local on the sql server
We start the ssms like this:
runas /netonly /user:YOUR_DOMAIN\YOUR_USER "C:\Program Files (x86)\Microsoft SQL Server\140\Tools\Binn\ManagementStudio\Ssms.exe"
Maybe this is different to the gui " run as different user"
Best regards,
Andreas

Hey Andreas,

thanks for sharing your experience. We do the exactly same, the command that you wrote upper is the very same command the we used to create a special shortcut for starting SSMS with the destination domain user. I have used this approach before and it functioned very good, as regular. Now the SSMS is acting very slow, and this is happening only when trying this approach, if I use SQL Server Authentication the studio runs very fast.

Best Regards,
Tomi