I connect to the corporate network from my personal PC at home and can
connect via NT Authentication to SQL Server. When making the VPN
connection, make sure the "Include Windows logon domain" is selected on the
"Options" tab of the properties dialog for the connection.

Jim

[quoted text, click to view]

Thanks for the reply Jim. We are using a CISCO v4.0.3 client to connect.
There are no such options. From what I understand the cisco client
authenticates and allows someone past the firewall, but does not allow or
facilitate authentication onto the windows network. That is why the little
authentication pop up boxes asking for login and password occur when we try
to map drives or other resources.

Seems like a security issue with SQL Server not allowing someont to

Not really SQL Server. If there are no windows credentials
passed to SQL Server, then SQL Server can't do anything
about it. You have to have to have windows credentials to
pass as SQL Server has no way of guess what they might be.
You could try the following -
Create a local login on your PC with the same user name and
password you have in the domain you are using for VPN
access. Log onto your PC with that user and then establish
the VPN connection.
I haven't tried that with VPN so I don't know if it would
work - it works in dealing with workgroup and some DMZ
scenarios.

-Sue

On Fri, 20 Oct 2006 21:55:02 -0700, Leneise44
[quoted text, click to view]