Add ability to connect to remote domain in SSMS usng windows authentication - by mweber3

Status : 

  Won't Fix<br /><br />
		Due to several factors the product team decided to focus its efforts on other items.<br /><br />
		A more detailed explanation for the resolution of this particular item may have been provided in the comments section.

Sign in
to vote
ID 781629 Comments
Status Closed Workarounds
Type Suggestion Repros 0
Opened 3/18/2013 7:55:04 PM
Access Restriction Public


SSMS does not support the ability to connect to a SQL Server in another domain using windows authentication natively.  In order to accomplish this we have to use the runas /netonly option which is less than ideal because:
1.  Requires an extra step to start the program.
2.  Shows no indication in the tool that another account is being used.   All status messages show the local account incorrectly.
3.  Requires running multiple instances of SSMS when access 2 or more remote domains simultaneously.
Sign in to post a comment.
Posted by Sanjay [MSFT] on 3/21/2013 at 9:41 AM
Hi!, thanks for writing in to Microsoft.

This connect bug is a duplicate of an existing connect bug

We took a look at this request and triaged it against several others and unfortunately, it did not meet the bar to be fixed. While we are closing this issue as 'won't fix', we have taken note of this internally and we will try & incorporate this request when we revisit this functionality in a future release of SSMS.

A possible workaround is to launch SSMS with runas. If required, you can also use the "/netonly" switch for the runas command to log in using remote credentials on a domain that you’re not currently a member of, even if there's no trust set up.
Example: runas /netonly /user:domain\username <program.exe>

Sanjay Nagamangalam, SQL Server Manageability