Connecting to remote SQL Server using DUN

Connecting to remote SQL Server using DUN

Post by Jim Elde » Tue, 14 Sep 1999 04:00:00



What are the basic steps necessary to connect to a remote SQL Server
using Dial-up Networking?

I am able to access the remote server via modem to
- successfully login
- map network drives
- ping the server

Other info:
- users who are connected locally to that server are able to connect to
the SQL Server.
- the Server Network Utility shows TCP/IP installed with port number
1433
- the client PC's Client Network Utility shows TCP/IP installed with
port number 1433 and
Server Alias and Computer Name showing the name of the remote server.

When I try to connect to the server using Query Analyzer, I get the
message "Unable to connect to server \\NTSERVER1  [Microsoft][ODBC SQL
Server Driver][TCP/IP Sockets]General network error.  Check your network
documentation."

If I type in the IP Address of the server in the Query Analyzer
connection dialog I get "Unable to connect to server 10.0.1.175
Server message 1326, Level 16, State 1  [Microsoft][ODBC SQL Server
Driver] client unable to establish connection.

The server is NT Server 4.0 SP5 W/ SQL 7.0 SP1 and the dialup client is
NT workstation 4.0 SP5.

Thanks!
Jim

 
 
 

Connecting to remote SQL Server using DUN

Post by Jim Elde » Tue, 14 Sep 1999 04:00:00


What are the basic steps necessary to connect to a remote SQL Server
using Dial-up Networking?

I am able to access the remote server via modem to
- successfully login
- map network drives
- ping the server

Other info:
- users who are connected locally to that server are able to connect to
the SQL Server.
- the Server Network Utility shows TCP/IP installed with port number
1433
- the client PC's Client Network Utility shows TCP/IP installed with
port number 1433 and
Server Alias and Computer Name showing the name of the remote server.

When I try to connect to the server using Query Analyzer, I get the
message "Unable to connect to server \\NTSERVER1  [Microsoft][ODBC SQL
Server Driver][TCP/IP Sockets]General network error.  Check your network
documentation."

If I type in the IP Address of the server in the Query Analyzer
connection dialog I get "Unable to connect to server 10.0.1.175
Server message 1326, Level 16, State 1  [Microsoft][ODBC SQL Server
Driver] client unable to establish connection."

The server is NT Server 4.0 SP5 W/ SQL 7.0 SP1 and the dialup client is
NT workstation 4.0 SP5.

Thanks!
Jim

 
 
 

Connecting to remote SQL Server using DUN

Post by Jim Elde » Tue, 14 Sep 1999 04:00:00


What are the basic steps necessary to connect to a remote SQL Server
using Dial-up Networking?

I am able to access the remote server via modem to
- successfully login
- map network drives
- ping the server

Other info:
- users who are connected locally to that server are able to connect to
the SQL Server.
- the Server Network Utility shows TCP/IP installed with port number
1433
- the client PC's Client Network Utility shows TCP/IP installed with
port number 1433 and
Server Alias and Computer Name show the name of the remote server.

When I try to connect to the server using Query Analyzer, I get the
message "Unable to connect to server \\NTSERVER1  [Microsoft][ODBC SQL
Server Driver][TCP/IP Sockets]General network error.  Check your network
documentation."

If I type in the IP Address of the server in the Query Analyzer
connection dialog I get "Unable to connect to server 10.0.1.175
Server message 1326, Level 16, State 1  [Microsoft][ODBC SQL Server
Driver] client unable to establish connection."

The server is NT Server 4.0 SP5 W/ SQL 7.0 SP1 and the dialup client is
NT workstation 4.0 SP5.  This is the first time I am trying to do this.

Thanks!
Jim

 
 
 

Connecting to remote SQL Server using DUN

Post by Jim Elde » Wed, 15 Sep 1999 04:00:00


Never mind -- it's working now.

(sorry about the dup. messages)


> What are the basic steps necessary to connect to a remote SQL Server
> using Dial-up Networking?

> I am able to access the remote server via modem to
> - successfully login
> - map network drives
> - ping the server

> Other info:
> - users who are connected locally to that server are able to connect to
> the SQL Server.
> - the Server Network Utility shows TCP/IP installed with port number
> 1433
> - the client PC's Client Network Utility shows TCP/IP installed with
> port number 1433 and
> Server Alias and Computer Name show the name of the remote server.

> When I try to connect to the server using Query Analyzer, I get the
> message "Unable to connect to server \\NTSERVER1  [Microsoft][ODBC SQL
> Server Driver][TCP/IP Sockets]General network error.  Check your network
> documentation."

> If I type in the IP Address of the server in the Query Analyzer
> connection dialog I get "Unable to connect to server 10.0.1.175
> Server message 1326, Level 16, State 1  [Microsoft][ODBC SQL Server
> Driver] client unable to establish connection."

> The server is NT Server 4.0 SP5 W/ SQL 7.0 SP1 and the dialup client is
> NT workstation 4.0 SP5.  This is the first time I am trying to do this.

> Thanks!
> Jim

 
 
 

Connecting to remote SQL Server using DUN

Post by Marti » Mon, 27 Sep 1999 04:00:00


Can somebody help me with this:

I know that is it possible to connect to a remote sql server using the
internet. In my case, it's MSSQL7. I'm used to work with the server
using a LAN, but I really don't know what to do when using the internet
and tcp/ip. I guess it is something with the ip address (of course!),
but what else?

I hope somebody can give me a clue or refer to a website dealing with
this. I have searched the news groups in vain.

Thanks in advance,

Martin Larsen

Sent via Deja.com http://www.deja.com/
Before you buy.

 
 
 

Connecting to remote SQL Server using DUN

Post by Alan Scot » Sat, 02 Oct 1999 04:00:00



says...

Quote:> Can somebody help me with this:

> I know that is it possible to connect to a remote sql server using the
> internet. In my case, it's MSSQL7. I'm used to work with the server
> using a LAN, but I really don't know what to do when using the internet
> and tcp/ip. I guess it is something with the ip address (of course!),
> but what else?

> I hope somebody can give me a clue or refer to a website dealing with
> this. I have searched the news groups in vain.

> Thanks in advance,

> Martin Larsen

> Sent via Deja.com http://www.deja.com/
> Before you buy.

I just did this for several of the applications I have written. It is

instructions. There are a couple things you need to have first. The
client machine I have found should have mdac installed on it. This can be
found at www.microsoft.com/odbc. This will update the client drivers for
SQL Server 7.

Hope to hear from you.
--

Thank you for any response.
Please direct all responses via email to

Alan Scott

 
 
 

1. connecting to a remote server using vb+sql server using ADO

hi,

i want to develop a database application using visual basic and ms-sql
server. i will be using front end application from different systems
on a network and the database resides on a Windows 200 Advanced Server
in the same network(in the same location).

i want to know which way i can connect to the server for accessing the
database.  i want to connect using ADO.

also i want to know the connection properties if the database resides
on a different location.

somebody can plz email me the connection properties at

regards,

sunil.

2. Change resource file

3. how do i determine which language was used during db installation?

4. Connection to remote SQL Server via DUN and Sygate

5. Small Office Table

6. Which database for WWW Query?

7. Problems connecting to SQL Server through ODBC and DUN

8. Tips for connecting to SQL Server thru DUN?

9. How to connect to remote SQL Server using ADO.NET