If you have clients that use CIFS networking protocol instead of a NetWare client, you must enable DFS Junction support for CIFS clients on all servers where you created DFS junctions. You must enable CIFS protocols for the destination servers, too. DFS Junction support for clients is available on NetWare 6.5 or later servers.
If new volumes are added within the DFS Management Context container after you enable DFS Junction support for CIFS clients, you might need to run VLDB Repair to update the VLDB database, depending on the utility that was used to create the new volume.
To enable DFS Junction support for CIFS clients on NetWare 6.5 or later servers:
On your NetWare 6.5 or later server, edit the sys:etc\cifsctxs.cfg file.
Add all CIFS/DFS users contexts to the file. CIFS uses a flat tree structure.
Enable DFS Junction support for CIFS for each server:
In iManager, click .
For instructions, see Section 3.1.4, Accessing Novell iManager.
Select a server to manage.
For instructions, see Section 3.1.7, Selecting a Server to Manage.
Select the check box, then click .
If you have not created a DFS Management Context, do it now.
For information, see Section 20.3, Creating a DFS Management Context.
In ConsoleOne, set the user Simple Password.
If Universal Password is enabled for the user container, it automatically synchronizes eDirectory and Simple Password.
IMPORTANT:Make sure the Windows logon user and password match the Simple Password’s username and password. DFS only passes the default Windows logon username and password.
In ConsoleOne, create junctions, if desired.
For information, see Section 20.18, Creating a DFS Junction Manually with ConsoleOne.