JohnItem
asked on
ODBC data source fails to connect to SQL Server 2000 via dial-up, but ok on broadband.
Hello, I have a situation in which a laptop user works from home, using a proprietary application.
This application connects to a SQL Server at the office using ODBC. Although I think irrelevant at this point, the user connects to office LAN via VPN.
Problem:
The ODBC data source setup on client's laptop connects successfully and therefore the application runs well, so long as he is at home (where he has a broadband connection to Internet).
If he leaves home and goes on the road (w/ same laptop), uses dial-up to connect to Internet, the application subsequently fails (I check and find that it is the ODBC data source that does not connect successfully).
Machine is running XP Home with the latest version of SQL Server data source.
Error is something along the lines of: SQL Server not found or invalid user name (I'm paraphrasing).
My attempts at solution:
ODBC is setup to authenticate using Windows NT authentication (not SQL Server user authentication).
Note that there are 6 other users on home, broadband connections with no problems at all who connect to the office LAN every day.
This implies - I believe - that it is indeed just a dial-up issue.
I've tried different dial-up ISPs; inquired with them to determined if it is a known problem.
I checked the time-out settings in SQL Server, for the possibility that connection is timing out and set it to its highest.
I hope this information helps. Thanks.
ASKER CERTIFIED SOLUTION
membership
This solution is only available to members.
To access this solution, you must be a member of Experts Exchange.
Hi again...
Have you checked the properties of your ODBC connection to make sure your are using TCP/IP instead of named pipes?
1. Highlight the connection, click CONFIGURE, then NEXT.
2. Click the CLIENT CONFIGURATION button. Make sure it is set to TCP/IP.
3. Also try changing both Server Name and Server Alias to the IP address, instead of the name.
I'm still thinking...
Have you checked the properties of your ODBC connection to make sure your are using TCP/IP instead of named pipes?
1. Highlight the connection, click CONFIGURE, then NEXT.
2. Click the CLIENT CONFIGURATION button. Make sure it is set to TCP/IP.
3. Also try changing both Server Name and Server Alias to the IP address, instead of the name.
I'm still thinking...
By the way, if changing the alias to IP address does not work, try REMOVING the alias in the Client Configuration section...
ASKER
My apologies for the delay... User is on holidays and I do not have access to PC until his return.
Guess it's not as urgent as they had me believe.
I will test modifications as soon as possible and get back to you. I will also increase the points to 190 (all I have so far).
Guess it's not as urgent as they had me believe.
I will test modifications as soon as possible and get back to you. I will also increase the points to 190 (all I have so far).
ASKER
Thank you gclay1.
Your first post did the trick. I used the Hosts file, which I would never have considered.
However, the reason it failed (see my second post) the first time is because the ODBC data source WAS set to TCP/IP.
In actuality it works when set to named pipes. Not sure why.
Client is happy as am I. I've increased points to 250.
Your first post did the trick. I used the Hosts file, which I would never have considered.
However, the reason it failed (see my second post) the first time is because the ODBC data source WAS set to TCP/IP.
In actuality it works when set to named pipes. Not sure why.
Client is happy as am I. I've increased points to 250.
ASKER
Exactly it is:
__________________________
Microsoft SQL Server ODBC Driver Version 03.81.9002
Running connectivity tests...
Attempting connection
[Microsoft][ODBC SQL Server Driver][Named Pipes]SQL Server does not exist or access denied.
TESTS FAILED!
__________________________
Thank you for the continued support.