Home Forums OS X Server and Client Discussion File Serving Problem with group folders in Server 10.3.4

Viewing 3 posts - 1 through 3 (of 3 total)
  • Author
    Posts
  • #358563
    honestpuck
    Participant

    Hi all,

    I’m having problems with Group folders in a newly installed 10.3.4

    Setup:

    With groups I have everyone in Group_All. Admin and several users are in Group_Accounts, Admin and a subset of Group_Account is in Group_Debtors.

    The Group folder is a share point owned by Admin and with a group of Group_All, both of whom can read and write. In that folder is a folder Accounts which is owned by Admin and with a group of Group_Accounts, there is also a folder of Group_Debtors called Debtors.

    I try logging in to the server as user Peter, who is a member of Group_All, Group_Accounts and Group_Debtors cannot open either of the two folders. I also tried logging on as user John who is also a member of each group and he cannot open the folders. I’ve tried the login from both 9.2.2 and 10.3.4 clients and no go.

    I’m authenticating against an LDAP directory also on the server.

    Anyone have any thoughts as to the next step.

    Tony Williams

    #358566
    honestpuck
    Participant

    The folders are created under the default server "Groups" folder. I’ve tried it as just ordinary folderrs and getting the Group to point to them as the groups default folder.

    It turns out that the problem is the length of the groups short name. While ‘WorkGroup Manager’ will accept a group short name longer than 8 characters the system just silently fails if it is longer. Nice one, Apple. Of course exactly the same name worked fine under ASIP 6.3 and Apple’s Migration utility failed to either adjust the name or give us a warning. The XML import in WorkGroup Manager also failed to advise of the problem.

    Tony

    #360485
    jaharmi
    Participant

    I came across this problem, too, but I created my groups manually. WGM didn’t warn me at all.

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

Comments are closed