"Sue Hoegemeier" wrote:

> You can also right click on the SSMS icon and do a Run As.
>
> -Sue
>
> On Tue, 27 Mar 2007 18:59:55 -0700, Bob
> <Bob@discussions.microsoft.com> wrote:
>
> >Sorry it took me a while to respond (had to be out of town).
> >
> >The piece that puzzles me is that I can connect using Query Analyzer without
> >any issues (using windows auth).
> >So, what changed in SSMS?
> >
> >(At this client site, sql auth on prod servers is not permitted)
> >
> >"Carl K." wrote:
> >
> >> Because you've selected Windows Authentication your local credentials must
> >> match your domain credentials.
> >>
> >> Create a user account on your local machine with the same credentials you
> >> use to log onto your workplace. When you log on to the local machine use
> >> 'MyAcct' (don't include your compname prefix). When you log on to the VPN use
> >> 'MyAcct' (don't include the domain prefix).
> >>
> >> As a alternative, create a separate SQL Login account and once you VPN into
> >> your workplace, use SQL Server Authentical and logon to te server using the
> >> SQL Logon account created for this purpose.
> >>
> >> "Bob" wrote:
> >>
> >> > Hi!
> >> > I have recently started using sql server management studio - I logon to
> >> > my desktop (Vista ultimate 32 bit) at home (using an account like
> >> > 'compname\myname') - I now VPN into my workplace (using my workplace account
> >> > 'domainname\MyAcct').
> >> > Now, when I try to connect to a server at my workplace using windows
> >> > authentication, it tries to connect as 'compname\myname'.
> >> > Is there a way to override this so that it can connect as 'domainname\myname'?
> >> > Any suggestions would be welcome!
> >> >
> >> >
>