Knowledge Base Home

Call Support


Search the Knowledge Base

Skip to end of metadata
Go to start of metadata

Environment

Netmail Archive, all versions (GroupWise Environments)

Synopsis

By default, Windows servers hosting Netmail Archive do not speak 'NCP' (NetWare Core Protocol). Since they don't understand NCP, they are not able to mount Netware Volumes via NCP, nor are they able to subsequently process GroupWise Native Archives held on Netware Volumes.

One way to work around this issue is to configure CIFS support on the source Netware Volumes. However, a better solution is to install the Novell client on all Netmail Archive nodes that participate in GroupWise Native Archive Processing and leverage a netdrives.txt file. This article will explain how to do this.

Solution

  1. Run all Netmail Archive services using a Local System Account and use netdrives.txt. Windows services can be configured to run under a local system account in the service's Log On properties in the Windows Services Console:



    Using a windows domain user for the Netmail Services login will cause Netmail Services to alternately use Netdrives and or attempt to mount the volume as a windows resource. The result is that after reboots and workstation logins, sometimes the Netdrives info is not used and the Native Archive file access will fail with 'no archives found in the specified path' type of errors.



  2. Create and leverage a Netdrives.txt file in the CONFIG directory of each Archive Server in the environment:

    Create a Netdrive entry for each Netware volume and for any remote Windows servers involved in Native Archive processing (e.g., all NetWare Volumes that hold Native Archives).

    Be aware that Netdrives is only read on Framework start-up, so the Netmail Open service needs to be restarted on a server after any changes are made to the server's local netdrives file.

    Netdrives.txt must be created in the ...Program Files (x86)\Messaging Architects\Config directory. A Netdrives trace file will be created in the root of the Messaging Architects directory.


NW volume entry format

\\edir tree\fully qualified Netware volume object with dot notation\;user.ou.o;pwd

Windows volume entry format

\\winserverIP\vol\;domain\user;pwd

Sample Netdrives.txt:

\\MYTREE\.HSC2_USERS10.MYTREE\;.mplus.MyTree;mypwd
\\MYTREE\.HSC2_USERS1.MYTREE\;.mplus.MyTree;mypwd
\\MYTREE\.HSC2_USERS2.MYTREE\;.mplus.MyTree;mypwd
\\MYTREE\.HSC2_USERS3.MYTREE\;.mplus.MyTree;mypwd
\\MYTREE\.HSC2_USERS4.MYTREE\;.mplus.MyTree;mypwd
\\MYTREE\.HSC2_USERS6.MYTREE\;.mplus.MyTree;mypwd
\\MYTREE\.HSC2_USERS7.MYTREE\;.mplus.MyTree;mypwd
\\MYTREE\.HSC2_USERS8.MYTREE\;.mplus.MyTree;mypwd
\\MYTREE\.HSC2_USERS9.MYTREE\;.mplus.MyTree;mypwd
\\10.22.9.204\c$\db;ad\mplus;mypwd
\\MYTREE\HSFSVC01_VOL1.SVC.HSF.MYTREE\;.mplus.MyTree;mypwd

3.  The Directory Agent value should be filled in on the Novell Client Properties:

Without a way to resolve the Volume Name, the Novell Client won’t be able to access the volume. The SLP DA (Directory Agent) has all of the service information and will allow the Novell Client to get location information about the volume object.

Specifying the volume object name in DNS may work and may be an option if SLP is not being used in the environment. Specifying the IP address of the server holding the volumes rather than the volume object name in the netdrives.txt file may occasionally work as well.

Notes


Help us improve!
Is this article helpful?
Is it well written?
Is the content complete?