December 18, 2008 at 10:55 am
I'm testing out an SSL VPN solution.
At present I can configure it to allow me to access port 1433 on the IP of our SQL server.
If I take a laptop that is a domain member and logon to it using my domain account, with the laptop off the network, it logs me on using a cached profile.
I then fire up my VPN software and try to setup a test connection to the SQL server simply to establish if I have connectivity.
It would appear that everything works perfectly if I use the IP address of the SQL server, but if I use either the short hostname (SERVER) or the FQDN of server.company.com it doesn't work and returns an SSPI error.
I've not spoken too much to the folks who manufacture the VPN as it's not been high priority as I'm only testing, but I'm unsure whether the issue lies with them, my test machine, or the SQL box?
All I know is that if I go via the ODBC area in Control Panel I can connect to the SQL box and use Windows Authentication i.e. my domain account only if I use the IP address when configuring the ODBC connection.
I'd welcome any pointers.
Viewing post 1 (of 1 total)
You must be logged in to reply to this topic. Login to reply