Summary:
Allow SQL 7.0/2000 connectivity through a Firewall.

Detailed Information:
1. Make SQL Server listen on a specific port on TCP (the default is 1433) or RPC (the default is a random port greater than 1023). You have to cycle the server after this change.

2. Configure your firewall server to allow traffic on the specific {ip_address}{port_number}.

3. Make the client (on the other side of firewall) use the appropriate connection string to talk to the {port_number} on the server. You can also use the Client Configuration Utility to add an "Advanced" entry with the appropriate Net-Library and connection string.


If you've done this and it still doesn't work then look at the firewall logs to see what packets it is dropping or do a network trace either side of the firewall to see what packets are not getting through. (You may want to disable/allow all through the firewall during testing to see what extra packets are allowed through).

Additional Info:
Which ports to open depends on the net-lib you are using :-

For tcp-ip sockets the default port for SQL Server is 1433.

For multi-protocol (rpc) the ports are normally variable, but you can fix them. See Q164667 in the Microsoft knowledgebase for details (http://support.microsoft.com)

For named-pipes over ip 137/138/139 are used. As these are the same ones used for file/print it is not recommended you allow these through the firewall.

Original Author: RSHAFER
Original Submitter: RSHAFER
Keywords: SQL firewall MMS ID#27442