Dear DougP
Thank you for the answer. I followed the article below from techNet, but I didn't get to make work.The remote access is make for an application in the IIS on a external LAN.
If you can help me???
Flavio Firmo
flaviohf@provide.psi.br
-----------------------------------------------
PSS ID Number: Q216415
Article last modified on 02-23-1999
winnt:2.0,6.5,7.0
winnt
======================================================================
-------------------------------------------------------------------------------
The information in this article applies to:
- Microsoft SQL Server versions 6.5, 7.0
- Microsoft Proxy Server version 2.0
-------------------------------------------------------------------------------
SUMMARY
=======
SQL Server can operate transparently with Proxy Server to prevent unauthorized
access to your internal network and eliminate the need to connect SQL Server
directly to the Internet.
When running SQL Server on a computer located behind Proxy Server, SQL Server is
protected by the packet filtering features of Proxy Server.
An administrator can configure Proxy Server to grant or deny inbound SQL Server
access by user, service, port, or IP domain.
This article describes how to configure Microsoft SQL Server so that it can be
accessed using the Server Proxy features of Microsoft Proxy Server.
MORE INFORMATION
================
This article will explain how to configure SQL Server for use with Proxy Server,
given the following scenario:
- SQL Server is located on an internal network, with an IP address of
209.58.170.10.
- The computer running Proxy Server has two network interface cards (NICs). One
NIC is connected to the internal network, with an IP address of
209.58.170.20. The second NIC is connected to the Internet, with an IP
address of 157.57.25.30.
- You want to access SQL Server from a client workstation located on the
Internet.
To configure SQL Server with Proxy Server given the conditions listed above,
perform the following steps:
1. Configure SQL Server with TCP/IP Sockets as one of the network protocols. If
you use a port number other than 1433 (the default), modify the
ServerBindTCPPorts line in Step 2 of this procedure to reflect that port
number.
2. Create the following Wspcfg.ini file on the SQL Server computer and place it
in the same folder as the Sqlservr.exe file (by default, this is the
C:\Mssql7\Binn directory for SQL Server 7.0 and the C:\Mmssql\Binn directory
for SQL Server 6.5):
[sqlservr]
ServerBindTCPPorts=1433
Persistent=1
KillOldSession=1
3. Install and configure Microsoft Proxy Server according to the documentation
provided with the product. Add the SQL Server computer's IP address
(209.58.170.10), along with the internal (intranet) IP address of the Proxy
Server (209.58.170.20), to the Local Address Table (LAT) on Proxy Server.
4. From the computer running SQL Server, connect to the MSPCLNT share on the
Proxy Server and install the Winsock Proxy Client.
5. Restart the SQL Server computer so that the changes to the Winsock driver can
take affect.
6. Now you must modify the client workstations for accessing the SQL Server
through the Proxy Server computer. To do this, perform the following steps:
1. Start the SQL Server Client Network Utility and click the General tab.
2. Click Add to create an entry for the SQL Server, using TCP/IP as the
Network Library. Provide a server alias and type the external (Internet)
IP address of the Proxy Server (157.57.25.30) in the Computer Name line.
Make sure the Port Number field contains the correct port number (by
default, this should be 1433).
NOTE: For SQL Server 6.5 clients, these entries are created on the Advanced
tab of the SQL Server Client Configuration Utility.
7. Verify the connection to SQL server from the client computer by starting
Query Analyzer (for SQL Server 7.0) or ISQL/w (for SQL Server 6.5) and
connecting to the server name you specified in part 2 of step 6 above.
Thank you for the answer. I followed the article below from techNet, but I didn't get to make work.The remote access is make for an application in the IIS on a external LAN.
If you can help me???
Flavio Firmo
flaviohf@provide.psi.br
-----------------------------------------------
PSS ID Number: Q216415
Article last modified on 02-23-1999
winnt:2.0,6.5,7.0
winnt
======================================================================
-------------------------------------------------------------------------------
The information in this article applies to:
- Microsoft SQL Server versions 6.5, 7.0
- Microsoft Proxy Server version 2.0
-------------------------------------------------------------------------------
SUMMARY
=======
SQL Server can operate transparently with Proxy Server to prevent unauthorized
access to your internal network and eliminate the need to connect SQL Server
directly to the Internet.
When running SQL Server on a computer located behind Proxy Server, SQL Server is
protected by the packet filtering features of Proxy Server.
An administrator can configure Proxy Server to grant or deny inbound SQL Server
access by user, service, port, or IP domain.
This article describes how to configure Microsoft SQL Server so that it can be
accessed using the Server Proxy features of Microsoft Proxy Server.
MORE INFORMATION
================
This article will explain how to configure SQL Server for use with Proxy Server,
given the following scenario:
- SQL Server is located on an internal network, with an IP address of
209.58.170.10.
- The computer running Proxy Server has two network interface cards (NICs). One
NIC is connected to the internal network, with an IP address of
209.58.170.20. The second NIC is connected to the Internet, with an IP
address of 157.57.25.30.
- You want to access SQL Server from a client workstation located on the
Internet.
To configure SQL Server with Proxy Server given the conditions listed above,
perform the following steps:
1. Configure SQL Server with TCP/IP Sockets as one of the network protocols. If
you use a port number other than 1433 (the default), modify the
ServerBindTCPPorts line in Step 2 of this procedure to reflect that port
number.
2. Create the following Wspcfg.ini file on the SQL Server computer and place it
in the same folder as the Sqlservr.exe file (by default, this is the
C:\Mssql7\Binn directory for SQL Server 7.0 and the C:\Mmssql\Binn directory
for SQL Server 6.5):
[sqlservr]
ServerBindTCPPorts=1433
Persistent=1
KillOldSession=1
3. Install and configure Microsoft Proxy Server according to the documentation
provided with the product. Add the SQL Server computer's IP address
(209.58.170.10), along with the internal (intranet) IP address of the Proxy
Server (209.58.170.20), to the Local Address Table (LAT) on Proxy Server.
4. From the computer running SQL Server, connect to the MSPCLNT share on the
Proxy Server and install the Winsock Proxy Client.
5. Restart the SQL Server computer so that the changes to the Winsock driver can
take affect.
6. Now you must modify the client workstations for accessing the SQL Server
through the Proxy Server computer. To do this, perform the following steps:
1. Start the SQL Server Client Network Utility and click the General tab.
2. Click Add to create an entry for the SQL Server, using TCP/IP as the
Network Library. Provide a server alias and type the external (Internet)
IP address of the Proxy Server (157.57.25.30) in the Computer Name line.
Make sure the Port Number field contains the correct port number (by
default, this should be 1433).
NOTE: For SQL Server 6.5 clients, these entries are created on the Advanced
tab of the SQL Server Client Configuration Utility.
7. Verify the connection to SQL server from the client computer by starting
Query Analyzer (for SQL Server 7.0) or ISQL/w (for SQL Server 6.5) and
connecting to the server name you specified in part 2 of step 6 above.
