A.2 Known Issues With iChain 2.3 and NetWare 6.5

A.2.1 Install the Latest Support Pack for NetWare 6.5 Before Testing iChain in Your Environment

Because of potential compatibility issues, we recommend that you install NetWare 6.5 with the latest support pack before testing iChain in your environment.

A.2.2 Using the iFolder Client Through iChain

The latest Novell iFolder client and server components are required for use through iChain. The iFolder client only works through an accelerator using an LDAP profile with basic authentication enabled. iFolder can be accessed from a browser through iChain only by using NetStorage. The iFolder applet for browser access to iFolder is not supported through iChain.

Also, if you are using the iFolder client through iChain, you must use the Use host name sent by browser option. The Alternate host name option should not be used.

Do not use path-based multi-homing when configuring an accelerator for iFolder client access.

A.2.3 The iPrint Client for Novell Open Enterprise Server No Longer Supports iChain

For information about how to accelerate NetWare 6.5 iPrint with iChain 2.3, see TID 10092295.

A.2.4 Accessing iFolder Through an Accelerator Requiring Authentication

When you access iFolder through an accelerator requiring authentication, if the authentication fails for any reason, the iFolder client login dialog box cannot be closed with the Cancel or close buttons. Instead, it re-prompts for login.

A workaround for closing the login dialog box is to choose Exit from the right-click menu of the iFolder tool-tray icon.

A.2.5 Leaving the Challenge/Response Blank in RADIUS Causes Error

If you leave the Response field blank in the Challenge/Response, a 400 Bad Request error displays.

A.2.6 Issue With RADIUS Loading On a NetWare 6.5 Server

Because of an issue with the ConsoleOne snap-in installation or an issue in ConsoleOne on the NetWare server, if the eDirectory RADIUS objects (the DAS object, etc.), are created from ConsoleOne running on the server, RADIUS will not load. This issue is under investigation.

To work around this issue, install ConsoleOne and the NMAS/RADIUS snap-ins on a workstation and then create all RADIUS configuration objects from the workstation.