SOLVED Windows home share connect fails, doubles path end

[ikke]

Hi,

I thought I sit down once again and try creating simple network share for a windows machine. The directory (zvol) is at:

/mnt/ikraid/topi/

and share details says it's name is "topi" and it's marked as homedir. Don't excactly know what difference that makes, but it's tapped anyway.

I even set the users freenas local password the same as in windows 10. Now everytime I try to connect windows to \\mynas\topi, it fails and prints out the following to the log, where you can see the path is wrongly having the dir name twice at the end:

Code:

[2017/10/29 18:07:28.311273,  1] ../source3/modules/vfs_shadow_copy2.c:2918(shadow_copy2_connect)
  shadow_copy2_connect: shadow_copy2_find_mount_point of the share root '/mnt/ikraid/topi/topi' failed: No such file or directory
[2017/10/29 18:07:28.311443,  1] ../source3/smbd/service.c:636(make_connection_snum)
  make_connection_snum: SMB_VFS_CONNECT for service 'topi' at '/mnt/ikraid/topi/topi' failed: No such file or directory
[2017/10/29 18:07:31.727465,  2] ../source3/smbd/service.c:1098(close_cnum)

Any idea how to fix this?

Versions is some months old here, I'm just updating it to latest to try if the bug is gone:

Code:

FreeBSD mynas.mynet 11.0-STABLE FreeBSD 11.0-STABLE #0 r313908+b3722b04944(freenas/11.0-stable): Sat Jul  1 02:44:49 UTC 2017	 root@gauntlet:/freenas-11-releng/freenas/_BE/objs/freenas-11-releng/freenas/_BE/os/sys/FreeNAS.amd64  amd64

 

[ikke]

how dumb was this, duh... so the use as home directory does not mean given user's home directory, but generic home directory base for all users, thus name doubling there at the end. This was easy to figure out by opening /usr/local/etc/smb4.conf where it's seen.

Well, I found a new way how to waste few hours by not reading the docs! :)