Appendix A: Firewall settings

Firewall settings are not relevant in single PC stand-alone demonstration installations.

In a client-server situation with more than one machine used for an Opera 3 SQL SE installation, you must consider inbound and outbound port settings for the following:

• Pegasus Opera Service

• Microsoft Distributed Transaction Coordinator (DTC)

• Microsoft SQL Server.

Part of the setup for the ports include what actions should be taken when a connection matches specified conditions (allow, allow if secure, block), and when the port rules apply (domain, private, public). You will need to consider your IT security for these aspects of the port rules.

Typically, outbound ports are open by default so should not need to be configured.

Pegasus Opera Service

These ports are used for communications between the client and the server.

To create port rules for the Pegasus Opera Service

1. At the Opera 3 SQL SE Server and each Opera 3 SQL SE Client PC,

2. From the Windows Start menu, type: 'wf.msc' to open the Windows Firewall with Advanced Security window.

3. Create the necessary inbound or outbound port rules.

Microsoft Distributed Transaction Coordinator (DTC)

Only needed if the Opera 3 SQL SE server and SQL Server databases are on different machines.

These ports are used for communication between the Opera SE server and the Microsoft SQL Server(s). They are also used between SQL Servers if the databases are on different SQL Server machines.

To create port rules for Microsoft Distributed Transaction Coordinator

1. At the Opera 3 SQL SE Server and Microsoft SQL Server machines,

2. From the Windows Start menu, type: 'wf.msc' to open the Windows Firewall with Advanced Security window.

3. Create the necessary inbound or outbound port rules.

Microsoft SQL Server

Only needed if the Opera 3 SQL SE Server and SQL Server databases are on different machines.

On the SQL Server machine allow TCP port 1433 in the incoming rules. If a non-standard port has been used, allow that port number instead. SQL Server connections also use UDP port 1434 to determine which actual port is used when non-default instances are connected to. In other words, the SQL Server driver connects to this port on the target server to find out the actual TCP port number to use when resolving an instance name.

To create port rules for Microsoft SQL Server

1. At the Opera 3 SQL SE Server and Microsoft SQL Server machines,

2. From the Windows Start menu, type: 'wf.msc' to open the Windows Firewall with Advanced Security window.

3. Create the necessary inbound or outbound port rules.

Non-default SQL Server instances will default to using a random TCP port number.