Support for eDirectory NCP servers listening on ports other than NCP 524
This document (7012589) is provided subject to the disclaimer at the end of this document.
Windows Server 2008 R2
Windows Server 2012
Because eDirectory supports hosting multiple instances on the same host machine, and allows configuring the NCP listening port for each instance in order not to collide over port 524 listening, it is possible to have NCP listening on a port other than 524.
In order to support multiple instances on multiple servers, it is incorrect to have an assumed NCP listening port; it must be learned from the server itself what port a particular instance of eDirectory is listening on.
eDirectory itself (in the data returned as part of eDirectory referrals) and SLP (as part of the svcaddr-ws attribute data) already includes the specific TCP/UDP port number a service / replica server is listening on.
known, port 524 is assumed. For eDirectory referrals and SLP name resolution, which do include port information, no port 524 assumption is made.
However, in the XTier NCP client (Novell Client for Windows 7, Novell Client for Linux, etc.), an assumption of port 524 is made even when more specific port information is available
If the name of the tree and/or server is supplied in the login dialog, when the name is resolved by SLP, all information about the tree and/or server is returned, including the IP address, port number and other network protocol information.
If the IP address is supplied in the login dialog, the Novell Client does not "learn" the port number, so it is necessary for the Client to specify which port number should be used to connect edirectory.
Earlier we always used port number 524; now other port numbers can be used for NCP communications.
With this improvement, the Novell Client learns correct eDirectory port information from eDirectory referrals. Once we have made the initial NCP connection to an eDirectory tree, referrals returned during object resolves will also provide accurate non-port 524 information the Novell Client will use when connecting to additional replicas within the tree.
This means the Client will learn correct NCP port information automatically through eDirectory referrals, and also for name resolution performed via SLP. The fix also supports manually typing in literal address and port information such as "10.0.0.1:1524" into the "Server:" or "Tree:" fields of the Novell Client login dialog.
This Support Knowledgebase provides a valuable tool for NetIQ/Novell/SUSE customers and parties interested in our products and solutions to acquire information, ideas and learn from one another. Materials are provided for informational, personal or non-commercial use within your organization and are presented "AS IS" WITHOUT WARRANTY OF ANY KIND.
- Document ID:7012589
- Creation Date:11-JUN-13
- Modified Date:11-JUN-13
- NovellClient for Open Enterprise Server (Client)
Did this document solve your problem? Provide Feedback