050-696 · Question #96
When installing the Novell Client on a Windows workstation, which login authenticator should you select if the Client will be used to log into an OES NetWare server?
The correct answer is A. NDS. Connecting to an OES NetWare server requires selecting NDS as the login authenticator because NetWare's directory-based authentication is built on Novell Directory Services.
Question
Options
- ANDS
- BBindery
- CeDirectory
- DCompatibility Mode
How the community answered
(50 responses)- A84% (42)
- B10% (5)
- C4% (2)
- D2% (1)
Why each option
Connecting to an OES NetWare server requires selecting NDS as the login authenticator because NetWare's directory-based authentication is built on Novell Directory Services.
NDS (Novell Directory Services) is the correct authenticator for OES NetWare servers because NetWare uses NDS as its core directory and authentication service, and the Novell Client presents NDS as the specific option for tree-based NetWare login.
Bindery is a legacy flat-file authentication database from NetWare 3.x and earlier, and is not appropriate for modern OES NetWare which uses directory-based authentication.
eDirectory is the product name for Novell's directory service, but within the Novell Client login authenticator selection dialog the NetWare option is specifically labeled NDS, not eDirectory.
Compatibility Mode is used for IPX/IP gateway interoperability scenarios, not as a primary directory login authenticator for OES NetWare.
Concept tested: Novell Client login authenticator selection for NetWare
Source: https://www.novell.com/documentation/novellient/
Topics
Community Discussion
No community discussion yet for this question.