Discussion Locked

Access to a NDS for NT domain

0 helpful
6 replies
Closed to new repliesThis discussion is closed. It stays readable, but it takes no new replies.

I have two NDS for NT powered domains. On the first domain I imported all NT users into NDS and all my Novell users were created corresponding NT accounts. On the second domain I imported only the NT users in NDS. Both domians trust each other (two way trust).
Problem is: an NDS authenticated user cannot access resources on the second domain and I don't know why. Specifically, I'm wanting to run a program that accesses a file server and a SQL database on domain 2. If I use the "NET USE" command to map a drive to the file server and SQL server in domain 2, then the program runs. I want to avoid this and simply be logged into NDS.
Can I have my cake and eat it too?

6 replies

by erikdr

NT requires credentials before the user gets access, there's no way around that.
So you are challenged with finding a way to explain the SQL Server in domain 2 who is the 'NT' user which asks access, without mapping the NDS account to an NT accountwhich implicitly happens when making the NET USE.
I have my strong doubts about that, though maybe you could find a less resource-consuming way of exposing the credentials than NET USE. Maybe make the use to a printer, not a file share?

Hope thiz helpz,

- The Netherlands

by asmith

In Domain 1, where I have corresponding NT accounts for all my NDS users, are my NDS users really getting NT credentials when they try to access an NT resource, or are they attempting to get the resource and allowed to because their username and password is the same in NT as in NDS? Again, if they have the same username and password in NDS and NT, are they really just logging in twice, or does NDS for NT provide some kind of special function that gives my NDS user NT credentials?

by Member 28996545

NDS for NT causes all calls to the NT security database to be intercepted and redirected into NDS. When you try to access a resource in domain2, NT will be wanting an account that has permissions to that resource. You need to ensure that a trusted account from domain1 is assigned permissions to the resource in domain2. Because security calls are redirected, you can use either Windows or NetWare tools to perform tasks. Also remember that NT creates security tokens at login time that are not dynamic. If userA is logged in, then added to a group that has permissions, it won't work until userA logs in again. (Whereas in NDS, changes are effective immediately, because permissions are evaluated dynamically at time of resource access, not login)

by Member 28996545

I shoudl have added: When your user logs in, they are authenticated against the information held in NDS, but an NT security token is still created (based on that information).

This discussion is closed to new replies.