novel

General Discussion about LDAP Administrator

Moderator: Support

Postby bigpaulie » Thu Feb 28, 2002 1:22 pm

Hi,
The FAQ has some clues on how to connect to MS Active Directory.
How do, or what is the syntax, I use to connect to Novel Directory Services running on NT?
bigpaulie
 
Posts: 1
Joined: Thu Feb 28, 2002 12:00 am

Postby Support » Mon May 06, 2002 3:58 am

LDAP Administrator can't locate naming contexts automatically due to the fact that NovellТs implementation leaves the RootDSE's namingContext attributes empty. The workaround is to connect to a server with an empty BaseDN and then do a simple search (Ctrl-F). It shows you the DNs available at the server.
Support
 
Posts: 896
Joined: Sun Aug 12, 2001 12:00 am

Postby grantdlr » Mon Oct 23, 2006 5:40 am

Support wrote:LDAP Administrator can't locate naming contexts automatically due to the fact that NovellТs implementation leaves the RootDSE's namingContext attributes empty. The workaround is to connect to a server with an empty BaseDN and then do a simple search (Ctrl-F). It shows you the DNs available at the server.


This would be fine as a workaround, except when ever you exit the application, it does NOT save your changes in the profile but reverts back to "ROOTDSE" Is there any way we can change this behaviour?
grantdlr
 
Posts: 2
Joined: Mon Oct 23, 2006 5:35 am

Postby Support » Mon Oct 23, 2006 7:40 am

Please note that the original post is almost 5 years old. We've fixed this issue with Novell years ago.

when ever you exit the application, it does NOT save your changes in the profile but reverts back to "ROOTDSE" Is there any way we can change this behaviour?


Could you please provide more details? What is the version of LDAP Administrator/Browser that you use. Does this persistence issues affects only Base DN property or other profile properties do not persist as well?
Support
 
Posts: 896
Joined: Sun Aug 12, 2001 12:00 am

Postby steveg » Tue Nov 14, 2006 3:21 am

This problem occurs on LDAP Administrator 3.3.1 and eDirectory 8.7.3 and 8.8. Its only a problem with partitioned directories.

The base DN must be entered as T=TREENAME before the objects are displayed, but this has to be manually entered each time LDAP Administrator is started.
steveg
 
Posts: 3
Joined: Tue Jul 25, 2006 6:39 am

Postby grantdlr » Tue Nov 21, 2006 11:10 pm

We use LDAP Admin 3.3.1 and edirectory 873 and 8.8. It only affects the persistence of the base DN, reverting back to ROOTDSE.

Because Novell use a blank namingcontext, once we partition a part of the tree off, it adds a namingcontext attribute which is always returned by ROOTDSE instead of the top of the tree.
grantdlr
 
Posts: 2
Joined: Mon Oct 23, 2006 5:35 am


Return to General Discussion

Who is online

Users browsing this forum: No registered users and 0 guests

cron