You’ll probably find that your service requires modifications to be made to the Windows Firewall system in order to provide consistent access to Integration Services. The Windows Firewall system controls access to specific computer resources primarily by limiting access to preconfigured ports. You cannot modify the port number used by Integration Services, as it only works using port 135.

In addition to using the user interface mentioned in this section, you can also script out this process from the command line by running the following (note that the line has wrapped but everything should be on a single command when you type it):

netsh firewall add portopening protocol=TCP port=135 name="RPC (TCP/135)" mode=ENABLE scope=SUBNET netsh firewall add allowedprogram program="%ProgramFiles%\Microsoft SQL
Server\100\DTS\Binn\MsDtsSrvr.exe" name="SSIS Service" scope=SUBNET

Here’s how to configure the Windows Firewall to permit Integration Services access:

1. Open the Windows Firewall from the Control Panel.

2. Select the Exceptions tab and click Add Program.

3. In the Add Program dialog, click Browse and select C:\Program Files\Microsoft SQL Server\100\DTS\Binn\MsDtsSrvr.exe. You should also, of course, use the Change Scope option in order to detail the computers that have access to the program by specifying a custom list of IP addresses, subnets, or both. The resulting exception is shown in the Windows Firewall dialog (see Figure 1-1).

4. Alternately, you can open the port instead of allowing the executable to have full reign of your network. To do this, click Add Port.



5. In the Add Port dialog, type a meaningful description like RPC(TCP/135) Integration Services, type 135 in the Port Number box, and select TCP as the protocol. You should also, of course, use the Change Scope option in order to indicate which computers have access to the port by specifying a custom list of IP addresses, subnets, or both.

That covers a substantial amount of the configuration required for the Integration Services service. Our next focus is event logging.