Microsoft KB Archive/274108

= SMS: How to Troubleshoot NDS Logon Point Creation Failures =

Article ID: 274108

Article Last Modified on 9/11/2007

-

APPLIES TO


 * Microsoft Systems Management Server 2.0 Standard Edition
 * Microsoft Systems Management Server 2.0 Service Pack 1
 * Microsoft Systems Management Server 2.0 Service Pack 2

-



This article was previously published under Q274108



SUMMARY
Systems Management Server (SMS) 2.0 has the ability to establish Novell NDS volume objects as logon points to an SMS site. It may occasionally be necessary to troubleshoot failures in the creation process of that logon point.

You can enable logging for the SMS_NDS_LOGON_SERVER_MANAGER, which will produce an nd_logon.log file in the sms\logs directory on your site server. Review of this log will provide you with valuable information concerning the cause of any failures.



MORE INFORMATION
There are two pieces of information that SMS requires to successfully connect to the Novell resource:
 * The security, as established in the Admin console, of a SITE SYSTEM connection account.
 * The proper path to the volume object where the SMSLOGON folder will be created.

Troubleshooting Security

 * 1) Log on to the Site server as the account that was set as the Site System connection account for NDS.

This will tell you whether the account can successfully authenticate to the NDS tree.
 * 1) Then try to connect to the volume where the SMSLOGON folder will be created. Manually create a directory and then delete it.

This process will tell you whether the connection account has the correct credentials to create the logon point.

Troubleshooting the Path
By referencing the nd_logon.log, verify that the path selected was typed correctly. The correct path should be as follows:

\\NDS_TREE_Name\.volume_object.OU.O

NOTE:
 * Depending on the Novell tree hierarchy, there may be more OUs (containers) in the path. The spelling of the tree name and all the objects in that path is of great importance.
 * The volume object needs to be the object as it appears in NWADMIN (Novell's administrative utility), not just the name of the volume, such as &quot;Apps&quot; or &quot;Vol1.&quot; The volume object consists of the file server upon which the volume is installed. For example, if a file server is called &quot;FS1&quot; and the volume is &quot;Vol1,&quot; the volume object would be &quot;FS1_vol1.&quot; This object should be found in the container in which the file server resides.

Additional query words: prodsms

Keywords: kbhowto kbinfo KB274108

-

[mailto:TECHNET@MICROSOFT.COM Send feedback to Microsoft]

© Microsoft Corporation. All rights reserved.