Cannot use Windows Authentification over VPN

Hi,
I'm trying to connect to my SQL Server 2000 over a VPN IPsec. The VPN
connects succesfully, I can browse with the Windows Explorer the shared
folders of my SQL Server.
When I ping the server the servername is resolved, and when I use ping
-a also resolve the dns.
My problem is the connection to the SQL Server with Windows
Authentification, the following error is throwed:
"Unable to connecto to server...
ODBC: Msg 0, Level 16, State 1
[Microsoft][ODBC SQL Server Dirver] Cannot generate SSPI context"
But when I use SQL Authentication works fine.
Can anyone help me please?
Thanks in advance,
David S
Hi guys...
Doing some test I think I know where is the problem.
As I describe in the past post, I'm using a Client VPN aplication to
communicate a mobile user to the main app in the hq. The things is that the
mobile user log in to his domain account when the VPN is not yet established,
so the DC doesn’t finds out when the user log in.
Once the VPN is up a running the user can access the different shared
folders. But when I try to connect to my app with SQL Server and Windows
Authentication, the app throws the following error: “Cannot generate SSPI
context”.
Is there any way to re-login once you have log onto your account or
just to establish a connection with the DC?
Thanks for your help,
David S
|||Working on exactly the same problem. Have you been able to resolve the
issue?
Maybe changing to named pipes? It did not work for me. Also, you can
use sql authentication and you should connect - unfortunately it is
not an option for me. Need to use windows authentication over ipsec.
|||Are you signing in to Windows through a VPN or starting a VPN connection
after you're signed in? You could try creating a User with the same
usercode and password as the user you use to sign in to the VPN, then sign
in to Windows with that user and then make your VPN connection and
connection to SQL that May work..
Mike Bulava, MCDBA
"dk77" <dk77@.aa-dot-com.no-spam.invalid> wrote in message
news:e5qdnXM6DIJiKgvfRVn_vg@.giganews.com...
> Working on exactly the same problem. Have you been able to resolve the
> issue?
> Maybe changing to named pipes? It did not work for me. Also, you can
> use sql authentication and you should connect - unfortunately it is
> not an option for me. Need to use windows authentication over ipsec.
>