Product specifications

Table Of Contents
Troubleshooting Firewalls and Avid Interplay
98
Troubleshooting Firewalls and Avid Interplay
Firewalls on client machines interfere with Avid Interplay’s TCP/IP communications.
Symptoms
The list of servers does not appear, for example, when you are connecting to a new database.
Connection establishment to the server fails.
Cause
These problems can be caused by personal firewalls installed on the client machine. A typical
example for such a firewall is ZoneAlarm
®
from ZoneLabs
or the Windows XP, Windows
Vista, or Windows 7 firewall.
These applications intercept all outgoing and incoming network traffic and decide whether to let
the traffic go through or block it. The effect is that applications like Avid Interplay fail to connect
to their servers.
Typically when the client looks for available Avid Interplay Engines in the network, no servers
can be retrieved. When the client is looking for servers, a UDP broadcast is sent out on port
8321.
Solution
Usually these personal firewalls can be configured to allow all network traffic for specific
applications. This should be done for Avid Interplay locally or for Internet access depending on
which servers Avid Interplay should connect to.
For information about ports used by Avid Interplay, see “Avid Interplay Port Usage” in the
Interplay Help and the Interplay Software Installation and Configuration Guide.
Integration of Journal Data into the Database
The Interplay Engine database consists of a core database store and a single permanent journal
file. The journal file holds the current binary data changes that are not yet written through to the
core database. The core database and the journal file are both contained in the _Database folder.
n
Prior to Interplay version 2.1, the Interplay Engine created multiple journal files, and it was
important for administrators to monitor the number of journal files created. This monitoring is
not needed for Interplay version 2.1 and higher.