Microsoft KB Archive/299673

= How To Configure ISA Server 2000 and Enterprise Manager to Connect Through ISA to a SQL Server =

Article ID: 299673

Article Last Modified on 6/29/2004

-

APPLIES TO


 * Microsoft Internet Security and Acceleration Server 2000 Standard Edition

-



This article was previously published under Q299673



SUMMARY
This article describes how to configure both Microsoft Internet Security and Acceleration (ISA) Server 2000 and Enterprise Manager for administering a Microsoft SQL Server computer through an ISA server.

NOTE: This article describes how to set up outbound connections to a SQL server, but does not describe how to publish a SQL server.



MORE INFORMATION
To administer a SQL Server computer through an ISA server, you must configure both the ISA server and the client computer that has the SQL administration tools (Enterprise Manager).

Configuring the ISA server

 Create a protocol definition. To do this, follow these steps:  In ISA Management, in the left pane expand Policy Elements and click Protocol Definitions. In the right pane, click Create a Protocol Definition. Name the definition as desired. For Port Number type 1433 (this is the default SQL port), for Protocol select TCP, and for Direction select Outbound. When you are prompted to create secondary connections, select No.  Create a protocol rule based on the protocol definition. To do this, follow these steps:  In ISA Management, in the left pane expand Access Policy and click Protocol Rules. In the right pane, click Create a Protocol Rule.</li> Name the rule as desired.</li> In the Rule Action dialog box, under Response to client requests to use protocol, select Allow.</li> Select Apply this rule to and select Selected Protocols. Select the protocol that you created in the previous step.</li> Configure the schedule as desired.</li> Configure the client type as desired.</li></ol> </li></ol>

Configuring the client computer

Change the Default Network Library to TCP/IP in the SQL Server Client Network Utility. To start the Client Network Utility, click Programs on the Start menu and then open the Microsoft SQL Server 7.0 or the Microsoft SQL Server 2000 folder. You can also open the utility by typing Cliconfg.exe at a command prompt. The default protocol is Named Pipes.

If you are running SQL Server 7.0 and the corresponding Enterprise Manager, follow these steps to change the Default Network Library to TCP/IP in the Client Network Utility:
 * 1) Start the Client Network Utility. On the General tab, select TCP/IP as the protocol.NOTE: If you are running SQL Server 2000, click the Alias tab and select TCP/IP.


 * 1) If you need to configure an alias, click Add.
 * 2) Give the server a suitable alias.
 * 3) For protocol select TCP/IP, and enter the IP address in the Computer Name text box if you cannot resolve the server name.

NOTE: If you cannot resolve the server name through Domain Name System (DNS), Windows Internet Naming Service (WINS), the Hosts file, the Lmhosts file, or broadcast, you need to add an Alias configuration in the Client Network Utility. When you add an alias, you enter the IP address as the computer name. You can also change the port that you are using; if you do so, configure the ISA server and SQL server accordingly.

When you add a server in Enterprise Manager, you must specify a name that can be resolved to an IP address. If you enter an IP address instead of a name, Enterprise Manager attempts to resolve the IP address to a name. To resolve the IP address you can either configure the name resolution properly or by using an alias. You can see this behavior if you trace a connection attempt in the above described scenario.

Additional query words: Enterprise Manager, Port, SQL Server

Keywords: kbinfo KB299673

-

[mailto:TECHNET@MICROSOFT.COM Send feedback to Microsoft]

© Microsoft Corporation. All rights reserved.