Discussion Locked

Built trust / access denied

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

Hi,
I setup a trust between a windows nt4.0 domain and a windows 2000 server domain. On the windows nt4.0 server, I go into user Manager for domains and Select the other windows 2000 domain, I could see some but not all of the users from the other domain. When I try to go into the properties of one of the users I get access denied. I'm not sure how to resolve this. Any help would be appreciated. Thanks in advance

7 replies

by timwalsh

Merely setting up a trust relationship does not give any user (even the administrator)in one domain any rights for the other domain.

To gain access to anything that requires administrator rights in the other domain, the other domain's administrator must give your account administrator privileges.

by eporteni

If you are trying to access user accounts residing in the 2000 Active Directory through NT's user manager... I'm pretty sure you are going to lose some functionality for managing these accounts. AD and NT User Manager are different beasts all together. You would be able to go to the 2K domain through User Manager, but depending on Active Directory, I wouldn't try to do too much from your NT box. I know this probably doesn't help much, but it's just my thoughts. Have you thought about upgrading your NT PDC to 2K or 2K3?

by bjorn.tore

Hi.

Do not use usermanager for domain to access Active directory. It will work if you use the NT4 version, (its to old to know thats it' AD), but as soon as you move users to OU's away from the default location you have a problem.

Instead edit users with "Active directory users and computers" and if you have a lot of users, try out the "find" functionality.

As for the trust: Did you setup a 2 way trust ? on both the NT4 domain and the AD domain ?
Did the useraccount you where logged onto the computer have account operator rights in the AD domain when you got the "access denied?"

Use "dommon.exe" from the resourcekit to verify that the trust works.
If it does not, check out the nameresolution, thats most likely the problem.

Good luck, its never as easy as MS claims:)

This discussion is closed to new replies.