Configuring Laserfiche 8 Web Products to be Firewall Compatible.

April 19, 2010 | KB: 1012565
WebAccess 8, WebLink 8, Agenda Manager 8

Summary

A firewall can prevent a Laserfiche Web product from communicating with a Laserfiche Server. See below for instructions on configuring Web Access 8, WebLink 8, and/or Agenda Manager 8 to work with firewalls.

Ports

By default, Laserfiche 8 Server listens on TCP port 80 or 5050. Laserfiche defaults to port 80 except when installed on the 32-bit edition of Windows XP, where Laserfiche defaults to port 5050. The Laserfiche 8 Server broadcasts notifications on port 5051. If there is a firewall between your Laserfiche 8 Server and your web server, ensure ports 80 or 5050, and port 5051 are open on the firewall. You can use the Server Settings node of the Laserfiche 8 Administration Console to modify the default port settings. The Laserfiche 8.0.1 Server (and higher) installation automatically creates a Windows Firewall exception for the Laserfiche Server.

For Laserfiche Rio installations, ensure the listening and notification ports are also open in the firewall (5048 and 5055 by default, respectively).

Web Access 8

See Types of Firewall Configurations, which explains the different types of firewall configurations that can be implemented for Laserfiche Web Access 8.

WebLink 8

See Types of Firewall Configurations, which explains the different types of firewall configurations that can be implemented for Laserfiche WebLink 8.

Agenda Manager 8

In most cases, Agenda Manager 8 is hosted inside of a firewall and is not intended to be public-facing. As a result, detailed instructions on firewall configuration is not necessary. If there is a firewall between your Laserfiche 8 Server and your Agenda Manager 8 Server, ensure the Laserfiche Server's listening and notification ports are open.

Working with a DMZ

If your web product is installed within a DMZ, and you are using Windows Authentication, there are two possible solutions:

  1. Set up a second domain controller with a trust relationship to the primary one. The web server should be on the second domain.
  2. Open additional ports on the firewall to allow the web server to be part of the internal domain. For more information, see Microsoft KB 179442.