Visit Open-E website
Results 1 to 6 of 6

Thread: NAS Functionality and Child/Trusted Domains

  1. #1
    Join Date
    Aug 2008
    Posts
    236

    Default NAS Functionality and Child/Trusted Domains

    Question for the NAS experts here. My customer has the following AD setup

    foo.com
    resources.foo.com
    apps.foo.com

    We've joined the DSS system to foo.com and all the groups/users can be seen. However, we can't see any of the users and groups in the child domains on the dss system. Is this functionality present?

  2. #2

    Default

    Try to enable the "Allow trusted domains".
    All the best,

    Todd Maxwell


    Follow the red "E"
    Facebook | Twitter | YouTube

  3. #3
    Join Date
    Aug 2008
    Posts
    236

    Default

    Already checked.. The behavior is as I described..

  4. #4
    Join Date
    Oct 2010
    Location
    GA
    Posts
    935

    Default

    2008 R2 PDC ?
    DNS on same box ?

  5. #5
    Join Date
    Aug 2008
    Posts
    236

    Default

    The PDC for the root domain is Windows 2008 and yes, we are using DNS from that same server.
    The other DCs for the child domains, does OpenE need to know about those servers?
    Essentially, what should one expect when checking the Trusted Domains box? Does that mean that I should be able to see all the users across all the domains from the Open-E server? Or does it mean something else?

  6. #6
    Join Date
    Oct 2010
    Location
    GA
    Posts
    935

    Default

    Allow trusted Domains:

    If it is set to no, then attempts to connect to a resource from a domain or workgroup other than the one which smbd is running in will fail, even if that domain is trusted by the remote server doing the authentication.
    This is useful if you only want your Samba server to serve resources to users in the domain it is a member of. As an example, suppose that there are two domains DOMA and DOMB. DOMB is trusted by DOMA, which contains the Samba server. Under normal circumstances, a user with an account in DOMB can then access the resources of a UNIX account with the same account name on the Samba server even if they do not have an account in DOMA. This can make implementing a security boundary difficult.

Posting Permissions

  • You may not post new threads
  • You may not post replies
  • You may not post attachments
  • You may not edit your posts
  •