Unable to connect using Samba

[isagarran]

Configuration :

• MotherBoard socket 1155 MSI H67MA-E35 (Revision B3).
• FreeNAS FreeNAS-11.0-U3 (c5dcf4416)
  
• 6 disks Seagate Barracuda 2Tb
• Memory 8Gb
• OCZ PSU ZS550W-EU - ZS Series, 550W 80Plus Bronze
• Processor Intel® Celeron® Processor G530 (2M Cache, 2.40 GHz)
• I intent to configure RAIDZ2 as advised by senior FreeNAS
• CD/DVD device for installation
• SSD SATA device connected as USB device

Hello,

Could you help me please ?
I have this configuration. I'm able to connect from a Windows server but I'm unable to connect from an android/unix server.
I tried to check the log, activate the logs, but I didn't see any messages.

user

Code:

user  medianas
homedir  /mnt/ISAGARRAN_VOL/NASMediaWindows
console  csh
Nom complet  medianas
Compte microsoft  checked

volume

Code:

Vol  /mnt/ISAGARRAN_VOL
apply owner  checked
Proprietaire  root
apply owner  checked
proprietaire  wheel
type de permission unix

dataset

Code:

dataset  /mnt/ISAGARRAN_VOL/NASMediaWindows
apply owner  checked
proprietaire  medianas
apply owner  checked
proprietaire  medianas
type de permission Windows

Shared CIFS

Code:

Shared Windows  /mnt/ISAGARRAN_VOL/NASMediaWindows
use as home share  unchecked
Name  NASMediaWindows
Applique les permissions par defaut  checked
autoriser les accès invites  unchecked
Navigable par les clients du reseau  checked
hotes autorises  @IP Windows, @IP Android, @IP Unix
objects VFS  zfs_space, zfsacl, streams_xattr, alo_pthread

SMB configuration

Code:

Nom netbios  freenas
groupe de travail workgroup
description  freenas server
codepage dos  cp437
codepage unix  utf-8
maitre local  checked
serveur de temps  checked
decouverte zeroconf checked
protocole  smb3
toujours autoriser checked
obey parm restriction checked
bind ip address  freenas IP server

I would appreciate any help, advices,
Isagarran

 

[Chris Moore]

MotherBoard socket 1155 MSI H67MA-E35 (Revision B3).

That is a gaming / desktop board, not a server board, you can tell by the audio ports on it that are totally not usable for FreeNAS.
It also has a Realtek 8111E network interface that are not as reliable as the Intel interface that is recommended.

I don't know what availability runs where you are but in the US you could have had a proper server board for about $80 from eBay.
http://www.ebay.com/itm/Supermicro-...C202-Chipset-Socket-H2-LGA-1155-/231836795521

Did you try to configure the system from the GUI or did you do all this from the commandline?

 

[isagarran]

yes I do. All from Gui. In a Frenas 9.3, prevously, I didn't get any problems.
Of course, I'm not totaly familiar with this new version and I did 9.3 SMB configuration a long time ago.
Isagarran

 

[isagarran]

Hello,
I saw your recommendation about motherboard. Seems OK. I upgrade time to time my Freenas configuration. Last month, I upgraded the configuration implementing RAIDZ2, 6 disks with a SSD disk in order to boot on following advices in this forum.
I'll also follow your advice. It makes sense.
regards. Isagarran

 

[isagarran]

I continued my testing but I'm always unsuccessful. I used the command from my ubuntu client
sudo mkdir /media/jps/test

sudo mount.cifs "//192.168.1.49/NASMediaWindows" /media/jps/test -o user=WORKGROUP/medianas,file_mode=0777,dir_mode=0777
Password for WORKGROUP/medianas@//192.168.1.49/NASMediaWindows:
mount error(13): Permission denied
Refer to the mount.cifs(8) manual page (e.g. man mount.cifs)

Just before these commands I activated then deactivated the debug mode on SMB service (stop/start) (see log messages.txt )
I saw these messages in the log. I did my test around 10:55:59 and at the end, I saw a message (nt sure it is related or if it is a message we can ignore)

Code:

Oct  8 10:57:11 freenas smbd[8491]:  dfs_GetDFSReferral: struct dfs_GetDFSReferral
Oct  8 10:57:11 freenas smbd[8491]:  in: struct dfs_GetDFSReferral
Oct  8 10:57:11 freenas smbd[8491]:  req: struct dfs_GetDFSReferral_in
Oct  8 10:57:11 freenas smbd[8491]:  max_referral_level  : 0x0003 (3)
Oct  8 10:57:11 freenas smbd[8491]:  servername  : '\192.168.1.49\NASMediaWindows'
Oct  8 10:57:11 freenas smbd[8491]: [2017/10/08 10:57:11.955286,  3, pid=8491, effective(65534, 65534), real(0, 0), class=msdfs] ../source3/smbd/msdfs.c:1010(get_referred_path)
Oct  8 10:57:11 freenas smbd[8491]:  get_referred_path: |NASMediaWindows| in dfs path \192.168.1.49\NASMediaWindows is not a dfs root.
Oct  8 10:57:11 freenas smbd[8491]: [2017/10/08 10:57:11.955309,  3, pid=8491, effective(65534, 65534), real(0, 0)] ../source3/smbd/error.c:82(error_packet_set)
Oct  8 10:57:11 freenas smbd[8491]:  NT error packet at ../source3/smbd/trans2.c(9160) cmd=50 (SMBtrans2) NT_STATUS_NOT_FOUND[/CODE]

I join some screenshot configuration
regards
Isagarran

 

[isagarran]

Oups screenshots are there

 

[isagarran]

For analyzing and clarification purpose, I ran these commands

Code:

smbtree
WORKGROUP   
  \\HANAYORI  HanaYori server (Samba,Ubuntu)   
  \\FREENAS  FreeNAS Server   
  \\FREENAS\IPC$  IPC Service (FreeNAS Server)   
  \\FREENAS\NASMEDIAWINDOWS 

and

Code:

/mnt]# ls -alt /mnt  total  44   
drwxr-xr-x  19 root  wheel  26 Oct  8 09:49 ..   
drwxr-xr-x  3 root  wheel  128 Oct  8 09:49 .   
drwxr-xr-x  7 root  wheel  7 Sep 24 09:01 ISAGARRAN_VOL   
-rw-r--r--  1 root  wheel  5 Sep 10 11:11 md_size   

cd ISAGARRAN_VOL/   
/mnt/ISAGARRAN_VOL]# ls -al  total 102   
   
drwxr-xr-x  7 root  wheel  7 Sep 24 09:01 .   
drwxr-xr-x  3 root  wheel  128 Oct  8 09:49 ..   
drwxr-xr-x  2 root  wheel  2 Sep 10 14:58 jails   
drwxr-xr-x  19 medianas  medianas  19 Oct  7 16:36 NASMediaWindows   

/mnt/ISAGARRAN_VOL]# cd NASMediaWindows/   
/mnt/ISAGARRAN_VOL/NASMediaWindows]# ls -al  total  851   
drwxr-xr-x  19 medianas  medianas  19 Oct  7 16:36 .   
drwxr-xr-x  7 root  wheel  7 Sep 24 09:01 ..   
drwxr-xr-x  2 medianas  medianas  6 Sep 30 17:16 Nouveau 

Hope, it will help
Isagarran

 

[isagarran]

Hello
I'm little bit desesperate. Irun this command to check parameters.

Code:

testparm /usr/local/etc/smb4.conf medianas 192.168.1.52														   
Load smb config files from /usr/local/etc/smb4.conf																				 
rlimit_max: increasing rlimit_max (1024) to minimum Windows limit (16384)														   
Processing section "[NASMEDIAWINDOWS]"																							 
Loaded services file OK.																											
WARNING: You have some share names that are longer than 12 characters.															 
These may not be accessible to some older clients.																				 
(Eg. Windows9x, WindowsMe, and smbclient prior to Samba 3.0.)																	   
Server role: ROLE_STANDALONE																										
																																	
Allow connection from medianas (192.168.1.52) to NASMEDIAWINDOWS 

regards.
Isagarran

 

[isagarran]

Hello,
I tried "Authorized Guest access" and it works fine. But it isn't what I try to achieve. I'm wondering if I could have an uppercase/lowercase transformation problem. On Linux I'm seeing CIFS share as NASMEDIAWINDOWS. The one defined is NASMediaWindows. I can find it using a dynamic seach on the DMB Network, I can find FREENAS Network, navigate up to NASMEDIAWINDOWS share. There is user/password prompted. I specify the user (lowercase) and password (lowercase) and I got "Permission denied".
Is there a way to keep and to see the share, user and password with uppercase/lowercase mixed.
regards.
Isagarran

 

[isagarran]

Hello,
I'm quite sure that I've this problem. user/password and the way the path are seen.
On Linux : Usin guest access :
Access is OK with smb://FREENAS/NASMEDIAWINDOWS/Medias
Access is KO with smb://FREENAS/NASMediaWindows/Medias
The share defined is :

Code:

Shared Windows /mnt/ISAGARRAN_VOL/NASMediaWindows
use as home share unchecked
Name NASMediaWindows
...

User associated (medianas) to the share is in lowercase and password sent is also in lowercase (there are numbers inside also). I suspect strongly that SMB converts it to uppercase. At least for user.
I'm open to new ideas.
Isagarran

 

[isagarran]

any help ?