ODBC Connection failed error 11001

[edward zhang]

We have SQL Server 7.0 SP3 on Window 2000. There is no problem to
establish ODBC connection with it internally (within the LN) using
TCP/IP. But when we connect the server through ODBC externally (Outside
the LN), the following messages appear:

Connection failed:
SQLState: '01000'
SQL Server Error: 11001
[Microsoft][ODBC SQL Server Driver][TCP/IP
Sockets]ConnectionOpen(gethostbyname()()).
Connection failed:
SQLState: '08001'
SQL Server Error: 11
[Microsoft][ODBC SQL Server Driver][TCP/IP Sockets]General network error

Any suggestion?

Thanks

Edward

*** Sent via Developersdex http://www.developersdex.com ***
Don't just participate in USENET...get rewarded for it!

[Tore Bostrup]

There are any number of possibilities for a connection to fail like this.

First of all, accessing a SQL Server from outside a local area network
usually means that the connection must pass through one or more routers and
at least one Proxy/Firewall. The Firewall and/or Proxy may not allow SQL
Server may to be accessed from an external location. It is usually not a
good idea to expose a SQL Server database directly to the internet.

Second, how are you addressing the server? If you are external to the LAN,
you have to specify an IP address or a registered domain name - and the
server must have a routable IP address. The server name you use internally
is meaningless outside your LAN.

Consider setting up a VPN connection to the LAN containing the SQL Server
(assuming you are an authorized user of that LAN), and connect through it.
That should solve most of the problems you may encounter.

HTH,
Tore.

"edward zhang" <anon...@devdex.com> wrote in message
news:%23gWJOaV...@tk2msftngp13.phx.gbl...

[edward zhang]

Tore,

Thank you very much for your information. Actually we are establishing
the ODBC connection to the server through VPN. We have done one server
successfully but failed with other one. I am wondering if the failure
was related to any settings on the SQL Server level?

[Tore Bostrup]

I can't tell what your scenarios are from this and your previous
description.

How many networks and how many systems are involved? (SQL Servers, Clients
that try to connect through VPN, and their respective networks).

Are you talking about three or four computers:

** Three:
2 Client PC's connecting to 1 SQL Server
OR
1 Client PC connecting to 2 SQL Servers

** Four:
2 Client PC's Connecting to 2 SQL Servers

Are you saying that you have two, three or four networks involved:

** Two networks:

Client PC 1 on Network 1 VPN to SQL Server 1 on Network 2
and
Client PC 2 on Network 1 VPN to SQL Server 1 on Network 2

OR
Client PC 1 on Network 1 VPN to SQL Server 1 on Network 2
and
Client PC 1 or 2 on Network 1 VPN to SQL Server 2 on Network 2

** Three networks:

Client PC 1 on Network 1 VPN to SQL Server 1 on Network 2
and
Client PC 2 on Network 3 VPN to SQL Server 2 on Network 2

OR

Client PC 1 on Network 1 VPN to SQL Server 1 on Network 2
and
Client PC 1 or 2 on Network 1 VPN to SQL Server 2 on Network 3

** Four networks:

Client PC 1 on Network 1 VPN to SQL Server 1 on Network 2
and
Client PC 2 on Network 3 VPN to SQL Server 2 on Network 4

Have you verified the VPN connections for each of your scenarios? Try
pinging the SQL server through the VPN (I *think* that should work, but I'm
not sure).

If the Client can see the SQL Server computer, it is a matter of configuring
the SQL Server client and server to have matching communication setup.

HTH,
Tore.

"edward zhang" <anon...@devdex.com> wrote in message

news:%23UqjUqe...@TK2MSFTNGP11.phx.gbl...

[edward zhang]

The testing scenario is very simple:

One Network, two SQL Servers, one client PC. The testing
results are:

Client PC 1 VPN to SQL Server 1 on Network 1 -- successful

Client PC 1 VPN to SQL Server 2 on Network 1 -- failed

We Have Tried pinging two SQL servers separately through the VPN, both
work.

[Tore Bostrup]

Either you are on two networks (client PC on one, SQL Servers on another) or
you wouldn't be needing a VPN connection.

Is your SQL Server 2 configured for TCP/IP sockets connections? (This is
different from running the TCP/IP network protocol on the server). Is it
configured to use the default port (1433) for SQL Server?

The problem indicates that the SQL Server either does not listen for TCP/IP
connections on the port you are trying to use, or that the connection
request does not reach it.

How are the servers configured (communication protocols, authentication, NT
Domain)?

There used to be a Connection Troubleshooter for SQL Server 7, I'm not sure
if there is one for SQL Server 2k, but you may wish to check the Microsoft
web site. Also, a bit of searching MSDN with keywords and phrases from your
error messages should give you some things to check out.

HTH,
Tore.

"edward zhang" <anon...@devdex.com> wrote in message

news:eyveTntJ...@TK2MSFTNGP11.phx.gbl...