A Share called homes and SMB

[HodgeHi]

Hello,

 

I was wondering if someone with access to an AD-OD environment could check out something for me. I have created a share in OS X Server which is called Homes. Now the AD Server cannot see this share even though i have given the admin user full control via ACLs. As soon as i unshare the folder and then change the name to something else like UserHomes and share it using this name, it works fine, no probs.

 

Is there something in SAMBA that requires the homes share name and thus clients can't see the share? I don't understand why Windows cannot see this share name?

 

TIA,

Mark.

[DMcCoy]

Hello,

 

I was wondering if someone with access to an AD-OD environment could check out something for me. I have created a share in OS X Server which is called Homes. Now the AD Server cannot see this share even though i have given the admin user full control via ACLs. As soon as i unshare the folder and then change the name to something else like UserHomes and share it using this name, it works fine, no probs.

 

Is there something in SAMBA that requires the homes share name and thus clients can't see the share? I don't understand why Windows cannot see this share name?

 

TIA,

Mark.

 

OS Xs Samba implementation is broken, it creates the Home share automatically, even if you disable the feature. I suspect this is what is using the name already.

[HodgeHi]

Have you witnessed this issue as well?

 

I assume that the volume Home that can be seen in Server admin's (another dire example of Programming) file sharing pane is the one that you refer to.

[DMcCoy]

I've only seen it due to the fact that I wanted to turn off the Username$ shares that are automatically generated but the settings in smb.conf are readded each time by os x.