Novell OPEN ENTERPRISE SERVER 2 SP2 - ADMINISTRATION, Implementation Manual, Page: 61 / 288

Caveats for Implementing OES 2 Services
6
61
n
ov
do
cx (e
n)
22
Ju
n
e 20
09
6
Caveats for Implementing OES 2
Services
This section presents a few pointers for avoiding common Open Enterprise Server 2 implementation
problems.
The list that follows is not comprehensive. Rather, it simply outlines some of the more common
problems reported by network administrators. To ensure successful service implementations, you
should always follow the instructions in the documentation for the services you are implementing.
Š
Section 6.1, “AFP,” on page 61
Š
Section 6.2, “Avoiding POSIX and eDirectory Duplications,” on page 62
Š
Section 6.3, “CIFS,” on page 64
Š
Section 6.4, “ConsoleOne Can Cause JClient Errors,” on page 64
Š
Section 6.5, “CUPS on OES 2,” on page 64
Š
Section 6.6, “eDirectory,” on page 64
Š
Section 6.7, “iFolder 3.8,” on page 66
Š
Section 6.8, “iPrint,” on page 66
Š
Section 6.9, “LDAP—Preventing “Bad XML” Errors,” on page 67
Š
Section 6.10, “Management,” on page 68
Š
Section 6.11, “NCP Doesn’t Equal NSS File Attribute Support,” on page 69
Š
Section 6.12, “Novell-tomcat Is for OES Use Only,” on page 70
Š
Section 6.13, “NSS (OES 2),” on page 70
Š
Section 6.14, “OpenLDAP on OES 2,” on page 71
Š
Section 6.15, “Samba,” on page 71
Š
Section 6.16, “Virtualization Issues,” on page 71
6.1 AFP
Š
Section 6.1.1, “Anti-Virus Solutions and AFP,” on page 61
6.1.1 Anti-Virus Solutions and AFP
The Apple Filing Protocol (AFP) support for NSS files on OES 2 SP2 is implemented via a
technology that bypasses the real-time scanning employed by most anti-virus solutions for OES.
NSS files shared through an AFP connection can be protected by on-demand scanning on the OES 2
server or by real-time and on-demand scanning on the Apple* client.