Go Premium for a chance to win a PS4. Enter to Win

x
  • Status: Solved
  • Priority: Medium
  • Security: Public
  • Views: 265
  • Last Modified:

user permissions in domain trusts

I have a domain trust in my environment and I want to add a user from domain-B to a shared folder on a server in domain-A.  As a test, I added domain-b\user to the shared folder of dc2.domain-A.local which is a DC server.  No problems there.  Active Directory appears to be working.  

However, if I go to a non-DC server than I cannot add the Trusted domain-B user to my domain-A server folders.  Users from domain-B won't even populate the add user window when I try find users.  

What am I missing?

Mike
0
Richard Comito
Asked:
Richard Comito
  • 2
  • 2
1 Solution
 
kevinhsiehCommented:
You you tried using groups? Put domain-B\user into domain-A\domain_local_group, and then assign permissions to domain-A\domain_local_group. The user may need to logout after you make the group membership change.
0
 
zalazarCommented:
When on the security tab and in Add... mode (Select Users, Computers, Service Accounts, or Groups).
Did you click on the button named "Locations...".
It's necessary to select Domain-B  there and press OK.
After that type the users name and click on "Check Names" and the lookup should be possible.

When working with AD groups in Domain-A where users of Domain-B should be member of, the group type should be "Domain local/Security".
0
 
Richard ComitoDirector of ITAuthor Commented:
Kevinhsieh and Zalazar - Yes, to both and it works, however, I need to be able to access users without using local groups.  I need to be able to put Domain-B\user instead.  A developer who makes a software we are using made a change to their system and they no longer can use Groups.

Again thanks! Both answers were correct.  However, my case needs the actual user from Domain-B since the developer made their change.

As a test, I opened the LDAP port on our firewall directly to their domain controller and it did authenticate and display users from Domain-B.  However, that is not how TRUSTS are supposed to work so I've been in contact with Microsoft and they agree that there is a problem so they are investigating but at their standard price.
0
 
zalazarCommented:
Thank you very much for the background information.
You are mentioning that it shouldn't be necessary for the member (non-DC) server to access their Domain Controller.
My experience with domain trusts is a little different and from what I know it's indeed necessary that the computer, which needs to lookup or verify the authentication of the trusted user, must be able to directly contact the trusted DC's.
But let's see what Microsoft will come up with.
0
 
Richard ComitoDirector of ITAuthor Commented:
Final Solution,
if I needed to add a single user from Domain-B\user to my Domain-A\Server ... I did have to open up authentication directly from the Domain-A\server to the Domain-B\DC.

Basically, there are two methods to adding users in a TRUSTED domain.

Method #1
Using Domain-A\groups and having Domain-B\users as members and then adding that Domain-A\group for permissions.  This was described by both Kevinhsieh and Zalazar.

Method #2
My case here which is adding Domain-B\User directly to Domain-A\server (no groups)
Zalazar called this one and "Yes" after days of testing with Microsoft this was the only solution (open authentication directly from Domain-A\server to Domain-B\DC).
0

Featured Post

Get your Conversational Ransomware Defense e‑book

This e-book gives you an insight into the ransomware threat and reviews the fundamentals of top-notch ransomware preparedness and recovery. To help you protect yourself and your organization. The initial infection may be inevitable, so the best protection is to be fully prepared.

  • 2
  • 2
Tackle projects and never again get stuck behind a technical roadblock.
Join Now