I've scoured Google searching for an answer that seems like it should be
easy but apparently isn't...when I open SSMS to connect to a SQL 2005
database and choose Windows authentication, it greys out the User Name
box...problem is, the server I need to connect to is in another domain...how
on earth are you supposed to specify a different Windows user name to
connect with other than the one currently logged into the machine?

-Ben



--
Posted via a free Usenet account from http://www.teranews.com

On Jul 6, 3:12 am, "Ben Hanson" <transparency...@hotmail.com> wrote:
> I've scoured Google searching for an answer that seems like it should be
> easy but apparently isn't...when I open SSMS to connect to a SQL 2005
> database and choose Windows authentication, it greys out the User Name
> box...problem is, the server I need to connect to is in another domain...how
> on earth are you supposed to specify a different Windows user name to
> connect with other than the one currently logged into the machine?
>
> -Ben
>
> --
> Posted via a free Usenet account fromhttp://www.teranews.com

Hi Ben,

If you need to connect to another machine within your own domain, or
in a domain with the appropriate trust relationship to your own
domain, then you can use the Run As feature when right clicking on the
shortcut that you're using to launch SSMS.

If, OTOH, it isn't possible for users from the target domain to log
onto machines on your local domain, then you need to find some other
way to do it - normal route to take in that case would be to get a
Terminal Services connection to a machine within the target domain and
then start SSMS normally (Or at least, that's what I've normally done
in the past).

The point behind this is - when SSMS offers to connect using Windows
Authentication, it's using Authentication that has already been
established. There's nothing built in to SSMS/SQL Server to perform
the authentication itself.

Damien