RealPlayer Content Appears to be Blocked
Problem: RealPlayer content fails to play. This is typically a firewall configuration issue and not
an Web Appliance problem. RealPlayer uses port 554, which is typically blocked in default firewall
configurations.
Note: The remote site can force the use of a non-HTTP port, which will result in users not being
able to view the content if the firewall is blocking the port being used.
Solution: To enable access to RealPlayer content, open port 554 on your firewall.
C.2 Active Directory Troubleshooting
The common error messages that you may encounter when configuring Active Directory access
are described in this section, as are the corrective actions that you can take to respond to them.
The following errors may be displayed at the bottom of the page when you click Verify Settings
on the Configuration > System > Active Directory page.
C.2.1 Appliance and AD Domain have the same name
The appliance and your Active Directory domain have been given the same name. These names
cannot be the same. Change the hostname of the appliance on the Network: Hostname page,
and then re-test the Active Directory settings by clicking Verify Settings on the System: Active
Directory page.
C.2.2 Clock skew is too large
The time difference between the appliance and your Active Directory Kerberos server is greater
than three minutes. Update the time on your Kerberos server, or adjust the NTP Server setting
(set at the bottom of the Configuration > System > Time Zone page) to synchronize the appliance
to the same NTP source as your Kerberos server.
Note: Microsoft Windows Server 2000 can be configured as an NTP source, see KB articles
http://support.microsoft.com/kb/216734
and
http://support.microsoft.com/kb/223184
. Microsoft
Windows Server 2003 is configured as an NTP source by default.
C.2.3 Could not auto-detect settings
Your network’s Active Directory settings could not be auto-detected by the appliance. Clear the
Auto-detect advanced settings check box, and manually configure all the required fields on the
System: Active Directory page.
C.2.4 Could not connect to Domain Controller
The appliance could not connect to the specified Active Directory domain controller, typically
because the hostname cannot be resolved, or an error was made when it was entered. Check
the Active Directory Domain Controller, update the required fields on the System: Active
Directory page, and click Verify Settings again.
Sophos Web Appliance | Appliance Behavior and Troubleshooting | 205
