M
Mal James
I've read up quite a bit on this particular issue now, and nobody seems to
know a way to resolve this properly.
It seems that a user cannot connect to the sql database unless they are on
the same domain as the server. If i am logging in from home via VPN then i
join the work domain, but im logged into my laptop as a local domain.
Therefore when i run sqlcmd -S server\db it gives me the trusted server
connection user error.
However, if i create a new user on my laptop which is the exact username and
password as my active directory account at work, and assign it to my work
domain in user account control (vista), the sqlcmd -S server\db command
returns >1
So this is the problem, and I know how to get around it, but this is not
physically possible to do for all staff members on their home pcs. I need to
be able to allow non domain specific sql connections or somehting like that.
please help me!
know a way to resolve this properly.
It seems that a user cannot connect to the sql database unless they are on
the same domain as the server. If i am logging in from home via VPN then i
join the work domain, but im logged into my laptop as a local domain.
Therefore when i run sqlcmd -S server\db it gives me the trusted server
connection user error.
However, if i create a new user on my laptop which is the exact username and
password as my active directory account at work, and assign it to my work
domain in user account control (vista), the sqlcmd -S server\db command
returns >1
So this is the problem, and I know how to get around it, but this is not
physically possible to do for all staff members on their home pcs. I need to
be able to allow non domain specific sql connections or somehting like that.
please help me!