Environment
Novell Client for Windows Vista
Novell Client 2 for Windows Vista/2008
Novell Client 2 SP1 for Windows Vista
Novell Client 2 SP1 for Windows Server 2008
Novell Client 2 SP1 for Windows 7
Novell Client 2 SP1 for Windows Server 2008 R2
Novell Client 2 SP2 for Windows Vista
Novell Client 2 SP2 for Windows Server 2008
Novell Client 2 SP2 for Windows 7
Novell Client 2 SP2 for Windows Server 2008 R2
Microsoft Windows 2008
Microsoft Windows 7
Microsoft Windows Vista
Novell Client 2 for Windows Vista/2008
Novell Client 2 SP1 for Windows Vista
Novell Client 2 SP1 for Windows Server 2008
Novell Client 2 SP1 for Windows 7
Novell Client 2 SP1 for Windows Server 2008 R2
Novell Client 2 SP2 for Windows Vista
Novell Client 2 SP2 for Windows Server 2008
Novell Client 2 SP2 for Windows 7
Novell Client 2 SP2 for Windows Server 2008 R2
Microsoft Windows 2008
Microsoft Windows 7
Microsoft Windows Vista
Situation
The Novell Client 2 for Windows is configured with the IP address of a Directory Agent manually (using Red N > Novell Client Properties > Service Location tab > Directory Agent List), and then later, configuration is added to have DHCP deliver the IP address of the Directory Agent (by configuring a System or Local Login Profile).
How does the Novell Client use this data to locate the Directory Agent?
How does the Novell Client use this data to locate the Directory Agent?
Resolution
The locally configured address is used first, then the DHCP-delivered address is used next, then finally multicast is used if necessary. It is important to note that discovery will stop as soon as a DA is found that supports the scope the query is specifying.
Additional Information
The SLP DA information will potentially come from some or all of the available configuration sources, depending on how far in the discovery process the OpenSLP User Agent must go before finding a matching SLP DA for the scope(s) being requested. The local config is used first, but if a DA supporting the scope needed isn't found using the local config, the Client will next see if any DAs were specified via DHCP, and whether any of those support the scope requested. If unsuccessful using the DHCP-delivered DAs, multicast will be attempted.
OpenSLP does not maintain a list of "all the SLP DAs". Upon finding a DA that supports one of the scope(s) requested, it stops and will not connect to or maintain information about any DAs that it was not required to query.
The Client caches the SLP DA information for 5 minutes. If it becomes necessary to locate a DA after the cache expires, the discovery process starts over. But, it will again go no further into the discovery process than required to find one DA that supports a configured scope, and it will stop at that point and not attempt to check any more configurations, or probe for any more DAs.
OpenSLP does not maintain a list of "all the SLP DAs". Upon finding a DA that supports one of the scope(s) requested, it stops and will not connect to or maintain information about any DAs that it was not required to query.
The Client caches the SLP DA information for 5 minutes. If it becomes necessary to locate a DA after the cache expires, the discovery process starts over. But, it will again go no further into the discovery process than required to find one DA that supports a configured scope, and it will stop at that point and not attempt to check any more configurations, or probe for any more DAs.