Knowledgebase

Why am I having trouble installing to NetWare?

Return to Knowledgebase

Open File Manager's GUI uses existing NT browser architecture to find and connect to remote Windows machines where the System Component is to be installed.

However, when connecting to a NetWare system, Open File Manager relies on NT's use of a Novell client, or the NT client for NetWare networks. Most connection issues can be resolved by using a recent, fully patched client for NetWare.

Connections to NetWare machines can also be broken or inhibited by bad router configurations, WAN/LAN communications problems or insufficient user rights. (NetWare users must have full administrative rights to a system to install or manage Open File Manager.)

NetRoot Key

Inability to connect to a NetWare machine from Open File Manager's GUI can also result from erroneous Windows Registry entries in Open File Manager's NetRoot Key. This is usually caused by the machine name or other important routing information being changed for a machine that was previously targeted by Open File Manager. To update the Windows Registry in this case, simply delete the NetRoot key in its entirety and restart Open File Manager's GUI: The NetRoot key is located in:

HKEY_LOCAL_MACHINE\Software\St. Bernard Software\Open File Manager\<Version>

Note: the NetRoot key will be recreated and populated the next time OFM scans the network.

TTS Flag

In some rare cases, Open File Manager's GUI cannot connect to a NetWare machine because a previous version of the Open File Manager System Component is installed on the target system, and a Transactional Tracking System (TTS) error resulted in the TTS flag being set on one or more of Open File Manager's files. In this case, you need to manually delete all of Open File Manager's files and directories from the target system, including those directly under Sys:\System. Then, reboot the NetWare server and try the connection again. If a file cannot be deleted, open its properties, uncheck the TTS flag, and then delete the file.