
Signature
This posting is provided "AS IS" with no warranties, and confers no rights.
I forgot to include this in my orginal post (sorry), but I really want to
avoid using SQL Server logins - we got docked in our security reviews of the
server if there are any SQL Server logins.
> Hello,
>
[quoted text clipped - 36 lines]
> =====================================================
> This posting is provided "AS IS" with no warranties, and confers no rights.
Sophie Guo [MSFT] - 20 Oct 2005 11:12 GMT
Hello,
If the client is unable to join the domain with a domain user account, and
the machine which installs SQL server is not a DC, a workaround may be :
1. Create a local user account on the SQL server machine. Grant the user
account to access SQL server.
2. Create a same local user account on the client machine. The user account
has the same user name and password as the local user account on the SQL
server machine.
3. Log on the client machine with the local user account of SQL server
machine, then dial in the network with a VPN. After connecting to the
network, it can connect to SQL server.
I hope the inforamtion is helpful.
Sophie Guo
Microsoft Online Partner Support
Get Secure! - www.microsoft.com/security
=====================================================
When responding to posts, please "Reply to Group" via your newsreader so
that others may learn and benefit from your issue.
=====================================================

Signature
This posting is provided "AS IS" with no warranties, and confers no rights.