AdWall / FileWall / LinkWall

Support FAQ

Documentation Version 1.21

September 2003

Copyright © 2002-2003 - Connectotel

1.0 Introduction

2.0 AdWall

2.1 Which files does AdWall use?

2.2 AdWall tab is missing for the server object

2.3 Rule does not appear to be working

2.4 Connectotel AdWall option not available in “Third-party filter” list

2.5 BorderManager Setup or Rules tabs missing for the server object

2.6 ADWALL.NLM displays "Public symbol" errors when loading

2.7 Error message managing rules with non-English language client

3.0 FileWall

3.1 Which files does FileWall use?

3.2 FileWall tab is missing for the server object

3.3 Rule does not appear to be working

3.4 Connectotel FileWall option not available in “Third-party filter” list

3.5 BorderManager Setup or Rules tabs missing for the server object

3.6 FILEWALL.NLM displays "Public symbol" errors when loading

3.7 Error message managing rules with non-English language client

4.0 LinkWall

4.1 Which files does LinkWall use?

4.2 LinkWall tab is missing for the server object

4.3 Rule does not appear to be working

4.4 Connectotel LinkWall option not available in “Third-party filter” list

4.5 BorderManager Setup or Rules tabs missing for the server object

4.6 LINKWALL.NLM displays "Public symbol" errors when loading

4.7 Error message managing rules with non-English language client

5.0 General

5.1 “CyberPatrol's CPFILTER.NLM is not loaded. Please load CPFILTER.NLM.”

6.0 Public Domain site lists

6.1 How do I use public domain site lists?

6.2 How do I use DMOZ Open Directory Project lists

1.0 Introduction

This document contains Frequently Asked Questions (FAQs) encountered by Support for the Connectotel AdWall, FileWall and LinkWall products.

2.0 AdWall

2.1 Which files does AdWall use?

AdWall makes use of the following files. Please check that the files are correctly installed:

File / Location
ADWALL.NLM / SYS:ETC\ADWALL
ADWALL.NCF / SYS:SYSTEM
ADWALL.DLL / SYS:PUBLIC\WIN32\SNAPINS
ADWALL.LST / SYS:ETC\ADWALL
ADWALL.ACL / SYS:ETC\BORDER\ENGLISH
ADWALL.KEY / SYS:ETC\ADWALL
ADWALL.DOC / SYS:ETC\ADWALL
ADWALL.LOG (Optional) / SYS:ETC\ADWALL

2.2 AdWall tab is missing for the server object

Make sure that the file ADWALL.DLL is located in the directory SYS:PUBLIC\WIN32\SNAPINS on the server from which NWAdmin is being run.

2.3 Rule does not appear to be working

  • Ensure that the "Enforce Rules" box is ticked from the BorderManager setup tab within NWAdmin.
  • Ensure that the rule has been defined as “Deny” and not as “Allow”.
  • Ensure that the rule is high enough in the list of rules so that it is being applied before any other rule can apply to the request.
  • Check that the URL of the site is in the ADWALL.LST file.

2.4 Connectotel AdWall option not available in “Third-party filter” list

Ensure that the file SYS:ETC\BORDER\ENGLISH\ADWALL.ACL is present. Please see Appendix B of the AdWall documentation for information about this file.

2.5 BorderManager Setup or Rules tabs missing for the server object

Ensure that the BorderManager snap-ins have been correctly installed on the server from which NWAdmin is being run.

2.6 ADWALL.NLM displays "Public symbol" errors when loading

  • Ensure that PROXY.NLM is loaded
  • Ensure that ACLCHECK.NLM is loaded

2.7 Error message managing rules with non-English language client

German: “Die Steuerdatei für die Verwaltung von Informationen mit einem der externen Filterprodukte ist fehlerhaft.”

French: “Le fichier de contrôle utilisé pour la gestion des informations avec un des produits de filtre externe est endommagé.”

Spanish: “El archivo de control de gestión de la información de uno de los productos con filtro externo está corrupto.”

This problem is described briefly in the following Novell TID:

and appears to be a BorderManager issue with the handling of non-English language support for BorderManager snapins.

To resolve this issue:

1. Rename the file SYS:PUBLIC\WIN32\NLS\language\RESTRICT.LG to

RESTRICT.OLD

or

2. Change the value of the registry key:

[HKEY_LOCAL_MACHINE\SOFTWARE\Novell\SessionSettings]

from “language” to ENGLISH

3.0 FileWall

3.1 Which files does FileWall use?

FileWall makes use of the following files. Please check that the files are correctly installed:

File / Location
FILEWALL.NLM / SYS:ETC\FILEWALL
FILEWALL.NCF / SYS:SYSTEM
FILEWALL.DLL / SYS:PUBLIC\WIN32\SNAPINS
FILEWALL.LST / SYS:ETC\FILEWALL
FILEWALL.ACL / SYS:ETC\BORDER\ENGLISH
FILEWALL.KEY / SYS:ETC\FILEWALL
FILEWALL.DOC / SYS:ETC\FILEWALL
FILEWALL.LOG (Optional) / SYS:ETC\FILEWALL

3.2 FileWall tab is missing for the server object

Make sure that the file FILEWALL.DLL is located in the directory SYS:PUBLIC\WIN32\SNAPINS on the server from which NWAdmin is being run.

3.3 Rule does not appear to be working

  • Ensure that the "Enforce Rules" box is ticked from the BorderManager setup tab within NWAdmin.
  • Ensure that the rule has been defined as “Deny” and not as “Allow”.
  • Ensure that the rule is high enough in the list of rules so that it is being applied before any other rule can apply to the request.
  • Check that the URL of the site is in the FILEWALL.LST file.

3.4 Connectotel FileWall option not available in “Third-party filter” list

Ensure that the file SYS:ETC\BORDER\ENGLISH\FILEWALL.ACL is present. Please see Appendix Bof the FileWall documentation for information about this file.

3.5 BorderManager Setup or Rules tabs missing for the server object

Ensure that the BorderManager snap-ins have been correctly installed on the server from which NWAdmin is being run.

3.6 FILEWALL.NLM displays "Public symbol" errors when loading

  • Ensure that PROXY.NLM is loaded
  • Ensure that ACLCHECK.NLM is loaded

3.7 Error message managing rules with non-English language client

German: “Die Steuerdatei für die Verwaltung von Informationen mit einem der externen Filterprodukte ist fehlerhaft.”

French: “Le fichier de contrôle utilisé pour la gestion des informations avec un des produits de filtre externe est endommagé.”

Spanish: “El archivo de control de gestión de la información de uno de los productos con filtro externo está corrupto.”

This problem is described briefly in the following Novell TID:

and appears to be a BorderManager issue with the handling of non-English language support for BorderManager snapins.

To resolve this issue:

1. Rename the file SYS:PUBLIC\WIN32\NLS\language\RESTRICT.LG to

RESTRICT.OLD

or

2. Change the value of the registry key:

[HKEY_LOCAL_MACHINE\SOFTWARE\Novell\SessionSettings]

from “language” to ENGLISH

4.0 LinkWall

4.1 Which files does LinkWall use?

LinkWall makes use of the following files. Please check that the files are correctly installed:

File / Location
LINKWALL.NLM / SYS:ETC\LINKWALL
LINKWALL.NCF / SYS:SYSTEM
LINKWALL.DLL / SYS:PUBLIC\WIN32\SNAPINS
LINKWALL.LST / SYS:ETC\LINKWALL
LINKWALL.ACL / SYS:ETC\BORDER\ENGLISH
LINKWALL.KEY / SYS:ETC\LINKWALL
LINKWALL.DOC / SYS:ETC\LINKWALL
LINKWALL.LOG (Optional) / SYS:ETC\LINKWALL

4.2 LinkWall tab is missing for the server object

Make sure that the file LINKWALL.DLL is located in the directory SYS:PUBLIC\WIN32\SNAPINS on the server from which NWAdmin is being run.

4.3 Rule does not appear to be working

  • Ensure that the "Enforce Rules" box is ticked from the BorderManager setup tab within NWAdmin.
  • Ensure that the rule has been defined as “Deny” and not as “Allow”.
  • Ensure that the rule is high enough in the list of rules so that it is being applied before any other rule can apply to the request.
  • Check that the URL of the site is in the LINKWALL.LST file.

4.4 Connectotel LinkWall option not available in “Third-party filter” list

Ensure that the file SYS:ETC\BORDER\ENGLISH\LINKWALL.ACL is present. Please see Appendix B of the LinkWall documentation for information about this file.

4.5 BorderManager Setup or Rules tabs missing for the server object

Ensure that the BorderManager snap-ins have been correctly installed on the server from which NWAdmin is being run.

4.6 LINKWALL.NLM displays "Public symbol" errors when loading

  • Ensure that PROXY.NLM is loaded
  • Ensure that ACLCHECK.NLM is loaded

4.7 Error message managing rules with non-English language client

German: “Die Steuerdatei für die Verwaltung von Informationen mit einem der externen Filterprodukte ist fehlerhaft.”

French: “Le fichier de contrôle utilisé pour la gestion des informations avec un des produits de filtre externe est endommagé.”

Spanish: “El archivo de control de gestión de la información de uno de los productos con filtro externo está corrupto.”

This problem is described briefly in the following Novell TID:

and appears to be a BorderManager issue with the handling of non-English language support for BorderManager snapins.

To resolve this issue:

1. Rename the file SYS:PUBLIC\WIN32\NLS\language\RESTRICT.LG to

RESTRICT.OLD

or

2. Change the value of the registry key:

[HKEY_LOCAL_MACHINE\SOFTWARE\Novell\SessionSettings]

from “language” to ENGLISH

5.0 General

5.1 “CyberPatrol's CPFILTER.NLM is not loaded. Please load CPFILTER.NLM.”

This is a cosmetic error caused by earlier versions of ACLCHECK.NLM, which only knew about one third-party product for BorderManager.

The current ACLCHECK message is:

"Third Party URL filtering solution is not initialised"

(You can obtain a later version of ACLCHECK.NLM as part of the latest BorderManager 3.7 service pack from

This message, or the previous version of the message,as shown above, will appear whenever you try to access the Internet without AdWall, FileWall or LinkWall loaded. This happens because you have a rule referencing AdWall, FileWall or LinkWall, but

the NLM is not loaded.

To prevent this message, either load the relevant NLM or remove the corresponding rule from the BorderManager Access Rules list.

6.0 Public Domain site lists

6.1 How do I use public domain site lists?

See the Novell AppNote:

“Using Public-Domain Site Blocking Lists with Novell BorderManager”, Novell Research, February 2003

6.2 How do I use DMOZ Open Directory Project lists

See the Novell Cool Solutions article:

“Using DMOZ Open Directory Project lists with Novell BorderManager”, April 2003

AdWall/FileWall/LinkWall Support FAQ