Home Forums OS X Server and Client Discussion File Serving “role” confusion for smb service

Viewing 3 posts - 1 through 3 (of 3 total)
  • Author
    Posts
  • #370882
    kray
    Participant

    I am having trouble getting smb services set up on Leopard Server. Currently the machine is set up as a stand alone server. However, all users who need smb connectivity are authenticated through LADP (not loacal). Can some one enlighten me as to the purpose of the other role options. Specifically I am wondering if I should be using “domain member”. I have no desire to do anything but serve files to my small group of windows users in a mixed lab of macs, pcs, and linux users.

    If this is the case, who chooses the workgroup (you can tell I am a windows neophyte), me or the University network that I am part of?

    Thanks

    #370895
    kray
    Participant

    By “working”, do you mean is smb working? If so, the answer is no. I changed the server “role” to primary domain controller (PDC) and managed to get smb service working for my personal login account and one other LADP authenticated user account on the system. However, other user accounts (LADP authenticated) can still not connect via smb service. There is no difference in the the way permissions are set up for the account that can connect and the accounts that can not.

    I am begining to think that there is something fundamentally broken with smb in Leopard Server.

    #370910
    kray
    Participant

    Thanks Mactroll. Here are more details:

    At this point I have two users authenticated to Local/Default (Administrator, and PostgreSQL Server)
    and four users authenticated to /LDAPv3/127.0.0.1 (my personal user, and three others)

    Services running are:

    APF
    DNS
    iCAL (not set up yet)
    iChat (not set up yet)
    Open Directory
    Print
    SMB
    Web

    You are right I do have the server set up as PDC

    My personal user is also set to use a portable home directory.

    The thing that I am most confounded by at this point is the fact that I have been able to mount a smb share for my personal user (from a windows computer of course), but I can get the other users (who are always on a windows computer) to be able to mount a smb share. I can even mount the other users shares if I authenticate as myself (but not as the owner of the share).

    Clearly there is something different in how my personal user is authenticated from how the other users are authenticated. I just can’t figure out what it is.

Viewing 3 posts - 1 through 3 (of 3 total)
  • You must be logged in to reply to this topic.

Comments are closed