ODBC SQL connection not working over PPTP VPN

We had a workstation connecting to a SQL server over a normal LAN.  Everything worked.  We had to move this workstation to a new office but wanted to still have access to this software.  We disjoined the workstation from the domain, moved it, and connected it to the VPN.  This is the error we get when opening the software. "Invalid user authorization specification: invalid user ID or password" We've reinstalled the software, and are 100% sure that the user ID and password is correct in the ODBC settings.  We had the software company login and they spent hours working on this but insist it's a networking issue, which I agree since it worked fine before the move. I've also disabled all firewalls on both ends including the firewall on the network adapters.  client pc is XP connecting to server 2003 standard.  Also, I am using the domain admin account for testing to connect.
Sean RhudyPresidentAsked:
Who is Participating?
 
Sean RhudyConnect With a Mentor PresidentAuthor Commented:
We tried everything above, couldn't get it to work.  We changed to a TS server.
0
 
Sean RhudyPresidentAuthor Commented:
P.S.  I can ping and browse the server with no issues.
0
 
arnoldCommented:
The situation is not the same since the system is no longer a member of the domain.


What is the authentication mode for the application using odbc are you using sql login or are you using or is the application using windows authentication mode. Now that that the system is not a member of the domain, the credentials used to login into the system do not match the required authorization to access the sql.
0
Improve Your Query Performance Tuning

In this FREE six-day email course, you'll learn from Janis Griffin, Database Performance Evangelist. She'll teach 12 steps that you can use to optimize your queries as much as possible and see measurable results in your work. Get started today!

 
Eugene ZCommented:
make sure odbs dsn  is set  with sql server valid sql server login\password  and if TCP\IP protocol  with port set too.

you need to make sure the new network setup of this PC has ability to see sql server port
default is 1433 - but you may have another (check on the sql server)
telnet from pc to this server port 1433
and you may need to open this port that will let this pc to see sql srrver
0
 
Eugene ZCommented:
<100% sure that the user ID and password is correct in the ODBC settings. >
does it mean when you open DSN properties - you cam get to the test form - and test connectivity was successful?


if is it -- it is probably this software setup problems-- > looks like you need to check this apps   connection string that may use another login
0
 
Sean RhudyPresidentAuthor Commented:
Yes, the test connectivity is successful.  ODBC is set to use SQL credentials, not windows authentication.
0
 
Eugene ZCommented:
check with the vendor  to check the apps connection string  - . you may have there something different than you have in DSN
0
 
Sean RhudyPresidentAuthor Commented:
I could rejoin the domain over the VPN, do you think that would be a smart troubleshooting step?
0
 
arnoldCommented:
Do you have sql login auditing enabled for failure? Look to see whether you have failed login attempts from the remote system looking at what username is being provided by the remote system and see whether it is an SQL or a remotename\username.

Rejoining the domain is not the only thing, you would also need to login into the system using AD credentials which in he current state would require the establishment of he VPN prior to making any login attempts.
0
 
Sean RhudyPresidentAuthor Commented:
Nothing else worked.
0
Question has a verified solution.

Are you are experiencing a similar issue? Get a personalized answer when you ask a related question.

Have a better answer? Share it in a comment.

All Courses

From novice to tech pro — start learning today.