Does your network consist of more than one NDS tree? If so, do you have users who need to access network resources on both NDS trees? You may have noticed that the NetWare login screen allows you to authenticate and log into only one NDS tree at a time. So, how can you save your users the time and trouble of having to log out of one NDS tree and into another one when they need to access network resources from a different tree? In this article, we’ll show you how you can use the Tree command to accomplish this task.

What’s the Tree command?
If you’re familiar with the utilities that come with NetWare, then the Tree command may sound new to you. If you look in the Public directory on your server, you won’t find TREE.EXE or any other utility like that. Instead, you use the Tree command as part of the login script. You can put it in the system or profile login script, but it will work best in the user login script.

For the command to execute properly, the client workstation must be running Novell’s Client 32, VLM 1.21, or later. That means that, if you run the NetWare client that comes with Windows 9x, the Tree command won’t work. It also won’t work on clients that don’t support multiple NDS tree logons, such as Novell’s client for OS/2.

To use the Tree command, type the following command in the user login script of the user who needs to access another tree:
TREE 2dtree\.userid.usersou.userso

You must supply the user’s fully distinguished login ID, which means that you must provide a leading period with the user’s ID, organizational unit, and organization. In this example, you’d replace 2dtree with the name of the second NDS tree that the user wants to access. In our example, userid is the user’s login ID, usersou stands for the user’s organizational unit, and userso represents the user’s organization.

If the user has the same user ID and password in both trees, he or she won’t be prompted to enter a password when the login script runs. If either the user ID or the password (or both) is different, then the user will be prompted to log into the other tree.

You can include the password in the tree command—but you shouldn’t. Doing so increases the chances that the passwords will be compromised. Second, including the passwords in the command increases the amount of work that you must do to maintain the scripts if the users change their passwords frequently.

After the Tree command connects the user to the new NDS tree, you can include login script commands that map network resources in the new tree to the user. Script commands, which are issued after the Tree command, execute (remain focused) on network resources in the new tree. To change the focus back to the original tree, include another Tree command with the original tree name in the command.

John Sheesley has been supporting networks since 1986, when he got his hands on NetWare 2.2. Since then, he’s worked with the Jefferson County Police Department in Louisville, KY and the Genlyte-Thomas Group. John’s been a technical writer for several leading publishers, including TechRepublic, The Cobb Group, and ZDJournals. If you’d like to contact John, sendhim an e-mail .

The authors and editors have taken care in preparation of the content contained herein, but make no expressed or implied warranty of any kind and assume no responsibility for errors or omissions. No liability is assumed for any damages. Always have a verified backup before making any changes.