ODBC connection to SQL server failing

Hi, I have an access 2003 database which connect to sql server via a
DSN that goes through a VPN. The database works fine and everyone can
coonect from their normal computers but for anyone working on their
Laptops (IBM Think Pad T42's) they cannnot connect to the datasource.
The DSN fails upon connection attempt with :

Connection Failed:
SQLState: '01000'
SQL Server Error: 1326
[Microsoft][ODBC SQL Server Driver][DBNETLIB]ConnectionOpen
(Connect()).
Connection Failed:
SQLState: '08001'
SQL Server Error: 17
[Microsoft][ODBC SQL Server Driver][DBNETLIB]SQL Server does not exist
or access is denied.

This has been driving me insane as i cannot understand why it works for
our desktop computers and not for our laptops. The version of MDAC is
the same on a computer that connects as it is on a laptop that doesn't.
TCP/IP is enabled on the server and is using the default 1433 port.
severs, desktops and laptops all patches and up to date with the latest
SP's. DSN has been dropped and re-created. Domain user has been put in
localAdmin group for laptop.

I hope i'm mising something really obvious...can someone please please
put me out of my misery and tell me they have come accross this before
and have a solution. Ive tried everything i can think of.

Cheers

DanDan (dan_barber2003@.hotmail.com) writes:
> Hi, I have an access 2003 database which connect to sql server via a
> DSN that goes through a VPN. The database works fine and everyone can
> coonect from their normal computers but for anyone working on their
> Laptops (IBM Think Pad T42's) they cannnot connect to the datasource.
> The DSN fails upon connection attempt with :
> Connection Failed:
> SQLState: '01000'
> SQL Server Error: 1326
> [Microsoft][ODBC SQL Server Driver][DBNETLIB]ConnectionOpen
> (Connect()).
> Connection Failed:
> SQLState: '08001'
> SQL Server Error: 17
> [Microsoft][ODBC SQL Server Driver][DBNETLIB]SQL Server does not exist
> or access is denied.

The problem is that the laptop somehow does not find the SQL Server.
This KB article discusses posible reasons:
http://support.microsoft.com/defaul...B;EN-US;q328306

--
Erland Sommarskog, SQL Server MVP, esquel@.sommarskog.se

Books Online for SQL Server SP3 at
http://www.microsoft.com/sql/techin.../2000/books.asp|||Thanks, Erland. I had found that article and gone through (as best i
could) all the options but still had no joy. I have finally solved it
though. On our desktops we have microsoft firewall client installed and
enabled but on the laptops we dont. For some reason it seems that we
cannot connect through our proxy server and a connection to sql server
has to be done through this firewall client?? Even though i have solved
the problem i am still not sure why this happened??

Thanks again

Dan|||Dan (dan_barber2003@.hotmail.com) writes:
> Thanks, Erland. I had found that article and gone through (as best i
> could) all the options but still had no joy. I have finally solved it
> though. On our desktops we have microsoft firewall client installed and
> enabled but on the laptops we dont. For some reason it seems that we
> cannot connect through our proxy server and a connection to sql server
> has to be done through this firewall client?? Even though i have solved
> the problem i am still not sure why this happened??

It sounds a little funny, I will have to admit. But being nowhere
close to a Windows networking expert, I don't have any explanations.

But if you have the SQL connection working, and also have the firewall
enabled on the laptops, that sounds like a double win to me.

--
Erland Sommarskog, SQL Server MVP, esquel@.sommarskog.se

Books Online for SQL Server SP3 at
http://www.microsoft.com/sql/techin.../2000/books.asp

ODBC Connect from MS Access to SQL Server 2000-Viable?

How viable is it to use MS Access as a front end (via ODBC) to a SQL Server
2000 database?

The users would access via the internet using a netgear vpn setup.

Thanks,

Paul SPaul Stanial wrote:
> How viable is it to use MS Access as a front end (via ODBC) to a SQL Server
> 2000 database?
> The users would access via the internet using a netgear vpn setup.
> Thanks,
> Paul S

I've seen this configuration more as an afterthought. What I mean is
that someone uses Access to design an application, complete with Forms
and Reports. Afterwards, they wish to put the data in SQL Server, but
they don't want to redo their Forms and Reports. From those projects
that I've moved the data to SQL Server, things have worked really well.

That being said, if this was a new application, I'd be deploying
something web-based (since you indicated that your users would access
via the internet). With many of the web-based tools out there, you can
quickly create applications as well.

HTH,
Brian

--
================================================== =================

Brian Peasland
dba@.remove_spam.peasland.com

Remove the "remove_spam." from the email address to email me.

"I can give it to you cheap, quick, and good. Now pick two out of
the three"

ODBC-- call failed when using VPN

Hello all.

Please excuse my lack of poper terminology when describing my issue to you, as I am very new to databases.

I have set up a SQL Server database which connects via MS Access. The application works fine, except when trying to connect through VPN.

Through System DSN, I changed the server name (FSERVER) to the server IP address, and test completed successfully. I am also able to ping the server when connected via VPN. However, when I try to start the application, I receive the following error after several seconds:

ODBC-- call failed.

That's it. No other information about the error. I read somewhere to make sure the MDAC versions are the same, which they are.

As I say, I am quite new to this, but would really appreciate any guidance to help me through.

Thanks in advance!
NilsWithout knowing quite a bit about your network, I can't give you a 100% sure-fire answer. My first guess would be that the DSN is set to use some protocol other than TCP/IP in the DSN Client Configuration and your VPN doesn't route that protocol. My next guess would be that your Network/VPN aren't configured to cooperate for name resolution.

Getting more error information than just "ODBC-- call failed." would help. That's not much for me to go on!

-PatP|||Thank you for the reply, Pat. Do you know of a way to receive a more verbose error than just "call failed"?

Thanks!
Nils|||That's a hard question to answer, it just begs for a smart-alec answer and that wouldn't help you at all.

The problem is most likely in the application/script itself. It apparently does a very poor job of reporting errors, and fails to give you critical information that would help you diagnose and fix this kind of problem.

I'd suggest that you start by solving a simpler problem, then use what yo learn from that process to help solve this problem. Use another application (with better diagnostic information) to open the ODBC DSN while using VPN. It should give you more information about the failure, which will help you (or us) to resolve the actual problem.

I'd start by using Excel, and use the Data | Import External Data | New Database Query menu item. This will allow you to open the DSN, which will probably throw some kind of error immediately. Just work through the process until you get an error message that tells you why the connection fails. I'd bet that the same problem is affecting your custom application, and once you fix the problem for one application, you'll fix it for them all.

-PatP