Community Discussions and Support
Single domain - Multiple NDS contexts

Hi!

iv:  You may have more than one Internet domain name mapped to a single
     NDS context, but you may not have multiple NDS contexts mapped to
     a single Internet domain name except by using the '/' operator.

I'm using the '/' operator:

[Domains]
/Teachers : mydomain.com
/Students : mydomain.com

In Mercury for NetWare: OK.
In Mercury32 with NDS: only detect users under /Teachers context :(((

Any idea?

Thx,
Barsony

Hi! iv:  You may have more than one Internet domain name mapped to a single      NDS context, but you may not have multiple NDS contexts mapped to      a single Internet domain name except by using the '/' operator. I'm using the '/' operator: [Domains] /Teachers : mydomain.com /Students : mydomain.com In Mercury for NetWare: OK. In Mercury32 with NDS: only detect users under /Teachers context :((( Any idea? Thx, Barsony

Hi! 

From Mercury.ini on Netware:
"you can have a single Internet domain name that maps to multiple NDS contexts"

[Domains]
/Teachers : mydomain.com
/Students : mydomain.com

In Mercury32 v4.52 with NDS it doesn't work: only search under /Teachers context.

What is the correct syntax?

Thx,
Barsony

<p>Hi! </p><p>From Mercury.ini on Netware: "you can have a single Internet domain name that maps to multiple NDS contexts" </p><p>[Domains] /Teachers : mydomain.com /Students : mydomain.com </p><p>In Mercury32 v4.52 with NDS it doesn't work: only search under /Teachers context.</p><p>What is the correct syntax? </p><p>Thx, Barsony </p>

[quote user="Barsony"]

Hi! 

From Mercury.ini on Netware:
"you can have a single Internet domain name that maps to multiple NDS contexts"

[Domains]
/Teachers : mydomain.com
/Students : mydomain.com

In Mercury32 v4.52 with NDS it doesn't work: only search under /Teachers context.

What is the correct syntax?

Thx,
Barsony

[/quote]

 

I do not do NDS but this is what it says in the readme.nds file about NDS domains.

 

b) The [Domains] Section.

In NDS mode, Mercury uses the [Domains] section to associate an NDS
organizational unit with an Internet domain. The syntax of the section is
basically the same as under Bindery mode, but with one or two extra
capabilities. Each entry in the [Domains] section must have an NDS
context on the left and an Internet domain name on the right. The NDS
context name must be expressed relative to the root of the NDS tree.
If you wish to apply an entry to an entire subtree rather than to a
single specific context, add a '/' character at the start of the NDS
context name.

Example:

The Organization "Acme Inc", has two separate divisions in the same NDS
tree, "Sales" and "Manufacturing". The "Manufacturing" division contains
three more organizational units, "Development", "Futures" and
"Production". The Sales division has only one organizational unit,
"Marketing". The NDS tree for Acme Inc looks like this:

        Acme Inc --+-- Sales ----------+-- Marketing
                   |
                   +-- Manufacturing --+-- Development
                                       |
                                       +-- Futures
                                       |
                                       +-- Production

The Internet domain name for Acme Inc is "acme.com". Because the Sales
and Manufacturing Divisions are administratively separate, they want to
have the domain names "sales.acme.com" and "mfg.acme.com" respectively.
Because of political divisions within the Sales group, the Marketing
division also wants to have its own domain name, "mktg.acme.com". The
Manufacturing Division, however, is happy to have "mfg.acme.com" apply to
all its sub-divisions. The [Domains] section that achieves this
organizational structure would be as follows:

[Domains]
Marketing.Sales.Acme Inc   :  mktg.acme.com
Sales.Acme Inc             :  sales.acme.com
/Manufacturing.Acme Inc    :  mfg.acme.com

Note the use of the '/' in the last entry to indicate that "mfg.acme.com"
should apply to all the organizational units beneath "Manufacturing" in
the NDS tree.

c) Restrictions

There are certain restrictions you must observe when running Mercury in
NDS mode:

i:   Your users' names must only contain standard ASCII characters. If you
     have usernames that contain special or extended ASCII characters,
     then you must create ASCII-only synonyms for those users.

ii:  If you use the '/' character to apply an Internet domain name to an
     NDS subtree then your users' names must be unique throughout that
     subtree. If you have two users with the same names in different
     organizational units of a subtree served by Mercury, then one of the
     users must be given a synonym that distinguishes him or her from the
     other user.

iii: Usernames may contain spaces; Mercury and Pegasus Mail will convert
     the space characters to underscores when writing the user's address
     into Internet mail. NDS regards spaces and underscores as exactly
     equivalent - if this condition ever changes in future versions of
     NetWare, then users whose names contain spaces must be given
     synonyms.

iv:  You may have more than one Internet domain name mapped to a single
     NDS context, but you may not have multiple NDS contexts mapped to
     a single Internet domain name except by using the '/' operator.

 

[quote user="Barsony"]<p>Hi! </p><p>From Mercury.ini on Netware: "you can have a single Internet domain name that maps to multiple NDS contexts" </p><p>[Domains] /Teachers : mydomain.com /Students : mydomain.com </p><p>In Mercury32 v4.52 with NDS it doesn't work: only search under /Teachers context.</p><p>What is the correct syntax? </p><p>Thx, Barsony </p><p>[/quote]</p><p> </p><p>I do not do NDS but this is what it says in the readme.nds file about NDS domains.</p><p> </p><p>b) The [Domains] Section. In NDS mode, Mercury uses the [Domains] section to associate an NDS organizational unit with an Internet domain. The syntax of the section is basically the same as under Bindery mode, but with one or two extra capabilities. Each entry in the [Domains] section must have an NDS context on the left and an Internet domain name on the right. The NDS context name must be expressed relative to the root of the NDS tree. If you wish to apply an entry to an entire subtree rather than to a single specific context, add a '/' character at the start of the NDS context name. Example: The Organization "Acme Inc", has two separate divisions in the same NDS tree, "Sales" and "Manufacturing". The "Manufacturing" division contains three more organizational units, "Development", "Futures" and "Production". The Sales division has only one organizational unit, "Marketing". The NDS tree for Acme Inc looks like this:         Acme Inc --+-- Sales ----------+-- Marketing                    |                    +-- Manufacturing --+-- Development                                        |                                        +-- Futures                                        |                                        +-- Production The Internet domain name for Acme Inc is "acme.com". Because the Sales and Manufacturing Divisions are administratively separate, they want to have the domain names "sales.acme.com" and "mfg.acme.com" respectively. Because of political divisions within the Sales group, the Marketing division also wants to have its own domain name, "mktg.acme.com". The Manufacturing Division, however, is happy to have "mfg.acme.com" apply to all its sub-divisions. The [Domains] section that achieves this organizational structure would be as follows: [Domains] Marketing.Sales.Acme Inc   :  mktg.acme.com Sales.Acme Inc             :  sales.acme.com /Manufacturing.Acme Inc    :  mfg.acme.com Note the use of the '/' in the last entry to indicate that "mfg.acme.com" should apply to all the organizational units beneath "Manufacturing" in the NDS tree. c) Restrictions There are certain restrictions you must observe when running Mercury in NDS mode: i:   Your users' names must only contain standard ASCII characters. If you      have usernames that contain special or extended ASCII characters,      then you must create ASCII-only synonyms for those users. ii:  If you use the '/' character to apply an Internet domain name to an      NDS subtree then your users' names must be unique throughout that      subtree. If you have two users with the same names in different      organizational units of a subtree served by Mercury, then one of the      users must be given a synonym that distinguishes him or her from the      other user. iii: Usernames may contain spaces; Mercury and Pegasus Mail will convert      the space characters to underscores when writing the user's address      into Internet mail. NDS regards spaces and underscores as exactly      equivalent - if this condition ever changes in future versions of      NetWare, then users whose names contain spaces must be given      synonyms. iv:  You may have more than one Internet domain name mapped to a single      NDS context, but you may not have multiple NDS contexts mapped to      a single Internet domain name except by using the '/' operator.  </p>
live preview
enter atleast 10 characters
WARNING: You mentioned %MENTIONS%, but they cannot see this message and will not be notified
Saving...
Saved
With selected deselect posts show selected posts
All posts under this topic will be deleted ?
Pending draft ... Click to resume editing
Discard draft