Product specifications

Table Of Contents
Network Considerations
23
Network Considerations
This section contains topics related to setting up your Interplay network environment.
Computer Names
A hostname must comply with RFC 952 standards. For example, you cannot use an underscore
in a hostname. For more information, see “Naming Conventions in Active Directory for
Computers, Domains, Sites, and OUs” on the Microsoft
®
Support Knowledge Base. See also
“Workspace Names” on page 22.
Verify Entries on the DNS Server
Service Framework can become sluggish and unstable if there are incorrect entries in the DNS
server for any of the computers in the Interplay environment. Symptoms include excessive CPU
usage by the Service Framework Lookup service and Interplay Diagnostics. The tree view in the
Interplay Service Configuration or Health Monitor might also fail to populate if there are
incorrect DNS entries.
Make sure that you correct any errors in DNS entries for name to IP resolution.
Configure the DNS Server to Support Reverse Lookup
If DNS is not configured for Reverse Lookup, Service Framework can not resolve IP addresses
to host names. Symptoms include tree views failing to populate in the Interplay Service
Configuration, Interplay Diagnostics, and Health Monitor.
Make sure the DNS server is configured to support Reverse Lookups.
Non-DNS Environments
In an non-DNS environment, you must configure a host file on all systems, including Avid Low
Res Encode systems. This is necessary so the Service Framework can list the systems in its client
applications, such as the Interplay Service Configuration or Health Monitor.
Computers with Multiple Network Interfaces
Computers that have multiple network interfaces in use must be entered in DNS so that all IP
addresses have the exact same hostname.
If you have multiple network interfaces on a computer and one is not used, use the Device
Manager to disable the interface. If not, the computer might have problems communicating with
the rest of the Interplay workgroup.