Hi everybody,
i have a problem with [homes] share in samba version 4.0.3, this share
is not accessible, and also the security tab to set permission, through
windows client, is not active.
Other shares, like profiles, works.
I have also tried another path but the problem persists.
Test from server:
smbclient //localhost/homes -Uadministrator%password
Domain=[xxxxxxxxxxxx] OS=[Unix] Server=[Samba 4.0.3]
tree connect failed: NT_STATUS_BAD_NETWORK_NAME
Permissions on /home/private
drwxrws--- 2 root staff 4096 6 feb 12.01 private
smb.conf
[homes]
path = /home/private
read only = No
Thanks
i made a test changing [homes] to [home] i configured letter and path from user profile in active directory snap-in. works, each user gets a folder named when he logs into domain, subdirectory with username are created correctly Il 06/02/2013 12.34, Ufficiotecnico Acknow Srl ha scritto:> Hi everybody, > i have a problem with [homes] share in samba version 4.0.3, this share > is not accessible, and also the security tab to set permission, > through windows client, is not active. > Other shares, like profiles, works. > I have also tried another path but the problem persists. > > Test from server: > smbclient //localhost/homes -Uadministrator%password > > Domain=[xxxxxxxxxxxx] OS=[Unix] Server=[Samba 4.0.3] > tree connect failed: NT_STATUS_BAD_NETWORK_NAME > > > > Permissions on /home/private > drwxrws--- 2 root staff 4096 6 feb 12.01 private > > smb.conf > [homes] > path = /home/private > read only = No > > Thanks
[homes] is a special name:
from smb.conf manpage:
The [homes] section
If a section called [homes] is included in the configuration file,
services connecting clients to their home directories can be
created on
the fly by the server.
When the connection request is made, the existing sections are
scanned.
If a match is found, it is used. If no match is found, the requested
section name is treated as a username and looked up in the local
password file. If the name exists and the correct password has been
given, a share is created by cloning the [homes] section.
Some modifications are then made to the newly created share:
? The share name is changed from homes to the located username.
? If no path was given, the path is set to the user?s home
directory.
If you decide to use a path = line in your [homes] section, it may be
useful to use the %S macro. For example:
path = /data/pchome/%S
is useful if you have different home directories for your PCs
than for
UNIX access.
This is a fast and simple way to give a large number of clients
access
to their home directories with a minimum of fuss.
----
Hope this explains why...
Linda
Ufficiotecnico Acknow wrote:> i made a test changing [homes] to [home]
> i configured letter and path from user profile in active directory
> snap-in.
> works, each user gets a folder named when he logs into domain,
> subdirectory with username are created correctly
>
Yes, sure. Il 12/02/2013 03.19, Linda W ha scritto:> [homes] is a special name: > > from smb.conf manpage: > The [homes] section > If a section called [homes] is included in the configuration file, > services connecting clients to their home directories can be > created on > the fly by the server. > > When the connection request is made, the existing sections are > scanned. > If a match is found, it is used. If no match is found, the > requested > section name is treated as a username and looked up in the local > password file. If the name exists and the correct password has been > given, a share is created by cloning the [homes] section. > > Some modifications are then made to the newly created share: > ? The share name is changed from homes to the located username. > ? If no path was given, the path is set to the user?s home > directory. > > > If you decide to use a path = line in your [homes] section, it > may be > useful to use the %S macro. For example: > > path = /data/pchome/%S > > is useful if you have different home directories for your PCs > than for > UNIX access. > > This is a fast and simple way to give a large number of clients > access > to their home directories with a minimum of fuss. > ---- > Hope this explains why... > Linda > > > Ufficiotecnico Acknow wrote: >> i made a test changing [homes] to [home] >> i configured letter and path from user profile in active directory >> snap-in. >> works, each user gets a folder named when he logs into domain, >> subdirectory with username are created correctly >> > >