SOLVED SMB Shares Can't be Accessed From a Mac Machine.

[Mamdoh]

Update [Oct 14, 2017]

As of FreeNAS-11-MASTER-201710140514, this issue seems to have been solved; confirmed on two different FreeNAS machines.

Mamdoh

--------------
Hi everyone,

I’m having a problem with SMB shares on MacOS Sierra. I can see the shares in “Finder”, but, when I click on them I get an error message like this:

There was a problem connecting to the server “192.168.2.12”.
The share does not exist on the server. Please check the share name, and then try again.

I’m using some SMB shares that require authentication and some that don’t. Shares can be accessed from a Windows machine successfully, but not from two different Mac machines with different OS versions.

The shares can be accessed on my base-install nightlies [FreeNAS-11-MASTER-201705050409 (8273773)]

I tried this on 3 systems (1 physical and 2 virtual) running:
FreeNAS-11-MASTER-201710060521 [Nightlies]
FreeNAS-11-MASTER-201710070509 [Nightlies]


First, I noticed that the GUI for the “SMB Service” is missing the “Server Minimum Protocol” and “Server Maximum Protocol” options.

Second, the [global] section in “/usr/local/etc/smb4.conf” looks like this:

Code:

[global]																															
	encrypt passwords = yes																										
	dns proxy = no																												
	strict locking = no																											
	oplocks = yes																												 
	deadtime = 15																												 
	max log size = 51200																											
	max open files = 171677																										
	logging = file																												
	load printers = no																											
	printing = bsd																												
	printcap name = /dev/null																									 
	disable spoolss = yes																										 
	getwd cache = yes																											 
	guest account = nobody																										
	map to guest = Bad User																										
	obey pam restrictions = yes																									
	ntlm auth = no																												
	directory name cache size = 0																								 
	kernel change notify = no																									 
	panic action = /usr/local/libexec/samba/samba-backtrace																		
	nsupdate command = /usr/local/bin/samba-nsupdate -g																			
	server string = FreeNAS Server (Test)																						 
	ea support = yes																												
	store dos attributes = yes																									
	lm announce = yes																											 
	hostname lookups = yes																										
	time server = yes																											 
	acl allow execute always = true																								
	dos filemode = yes																											
	multicast dns register = yes																									
	domain logons = no																											
	local master = yes																											
	idmap config *: backend = tdb																								 
	idmap config *: range = 90000001-100000000																					
	server role = standalone																										
	netbios name = FREENAS																										
	workgroup = MC_WORKGROUP																										
	security = user																												
	create mask = 0666																											
	directory mask = 0777																										 
	client ntlmv2 auth = yes																										
	dos charset = CP437																											
	unix charset = UTF-8																											
	log level = 10

I noticed “/usr/local/etc/smb4.conf” doesn’t have the following parameter:
pid directory = /var/run/samba

I tried adding the missing line +/- a combination of the following to the “SMB Service” Auxiliary parameters:
server min protocol =
server max protocol =

But without any luck. Any ideas or solutions?

Thanks,
Mamdoh


N.B.: I know the deal with nightlies and how they are in a constant state of potential “brokenness”. :) I’m only providing a feedback, which is probably not as valuable as feedbacks on beta versions. But, might confirm to other users who are facing the same issue that it’s a software-specific, rather than machine/system-specific issue. Also, if it results in finding a solution, then that’s just an added value to the thread. I’m planning to clean-install a stable base-release in the near future.

 

[anodos]

What happens if you do the following:
1) in finder click 'go' -> 'connect to server'
2) in menu type 'smb://<IP of freenas>/<share>'

 

[Mamdoh]

What happens if you do the following:
1) in finder click 'go' -> 'connect to server'
2) in menu type 'smb://<IP of freenas>/<share>'

Edit: Changed http:// to smb://.
---
If I try to connect to the FreeNAS server directly i.e.: smb://192.168.2.50, I get prompted with an authentication prompt, I tried both "Guest access" and "authenticated access -> correct authentication", I see a list of SMB shares on the server, after clicking on an individual share, I get promoted with an error message:

Code:

There was a problem connecting to the server “192.168.2.50”.
The share does not exist on the server. Please check the share name, and then try again.

If I try to connect to a share on the server directly i.e.: smb://192.168.2.50/Media, I get prompted with an authentication prompt, I also tried both "Guest access" and "authenticated access -> correct authentication", I get promoted with the same error message:

Code:

There was a problem connecting to the server “192.168.2.50”.
The share does not exist on the server. Please check the share name, and then try again.

 

[anodos]

If I try to connect to the FreeNAS server directly i.e.: http://192.168.2.50, I get prompted with an authentication prompt, I tried both "Guest access" and "authenticated access -> correct authentication", I see a list of SMB shares on the server, after clicking on an individual share, I get promoted with an error message:

Code:

There was a problem connecting to the server “192.168.2.50”.
The share does not exist on the server. Please check the share name, and then try again.

If I try to connect to a share on the server directly i.e.: http://192.168.2.50/Media, I get prompted with an authentication prompt, I also tried both "Guest access" and "authenticated access -> correct authentication", I get promoted with the same error message:

Code:

There was a problem connecting to the server “192.168.2.50”.
The share does not exist on the server. Please check the share name, and then try again.

Http or smb?

 

[Mamdoh]

Http or smb?

Oops! Sorry. smb:// not http:// I also tried cifs://. Same results.

I'm gonna edit my previous reply post to reflect that.

By the way, I also have an "afp" share on the same server which works fine.

Thanks.

 

[anodos]

In that case, perhaps switch to using stable instead of nightlies. ;)

 

[anodos]

I just confirmed that this isn't working. May be a side-effect of introducing Samba 4.7. Will have to test further.

Code:

[2017/10/08 13:37:58.059613, 10, pid=14052, effective(0, 0), real(0, 0)] ../source3/smbd/smb2_server.c:3006(smbd_smb2_request_done_ex)
  smbd_smb2_request_done_ex: idx[1] status[NT_STATUS_OK] body[4] dyn[no:0] at ../source3/smbd/smb2_sesssetup.c:1266
[2017/10/08 13:37:58.059676, 10, pid=14052, effective(0, 0), real(0, 0)] ../source3/smbd/smb2_server.c:918(smb2_set_operation_credit)
  smb2_set_operation_credit: requested 1, charge 1, granted 1, current possible/max 1/512, total granted/max/low/range 512/8192/26/512
[2017/10/08 13:37:58.059747,  5, pid=14052, effective(0, 0), real(0, 0)] ../libcli/smb/smb2_signing.c:93(smb2_signing_sign_pdu)
  signed SMB2 message
[2017/10/08 13:37:58.060190, 10, pid=14052, effective(0, 0), real(0, 0)] ../source3/smbd/smb2_server.c:1075(smbd_server_connection_terminate_ex)
  smbd_server_connection_terminate_ex: conn[ipv4:192.168.5.20:52232] reason[NT_STATUS_END_OF_FILE] at ../source3/smbd/smb2_server.c:3930

Advice still stands. Keep away from nightlies if you want stable system.

 

[jlentz3]

In that case, perhaps switch to using stable instead of nightlies. ;)

I’m on nightlies and using smb and I don’t have any issues connecting with Sierra.

I’d like to switch trains to stable but have not been able to make the switch successfully.


Sent from my iPhone using Tapatalk

 

[Ericloewe]

You have to rollback to the latest stable you installed.

 

[Mamdoh]

I’d like to switch trains to stable but have not been able to make the switch successfully.


Sent from my iPhone using Tapatalk

It all depends on your initial install. If you installed from an *.iso file that had the word "Master" within the name, then your base install is a nightly and you're stuck on that train to no layman's land. Solution: Clean install from a stable version.

If you, however, did/do install from a stable release *.iso, you can always switch to the nightlies train when the beta-bug bites you; knowing well you can always revert back to a stable version by changing trains. Good luck.

 

[Mamdoh]

I just confirmed that this isn't working. May be a side-effect of introducing Samba 4.7. Will have to test further.

Code:

[2017/10/08 13:37:58.059613, 10, pid=14052, effective(0, 0), real(0, 0)] ../source3/smbd/smb2_server.c:3006(smbd_smb2_request_done_ex)
  smbd_smb2_request_done_ex: idx[1] status[NT_STATUS_OK] body[4] dyn[no:0] at ../source3/smbd/smb2_sesssetup.c:1266
[2017/10/08 13:37:58.059676, 10, pid=14052, effective(0, 0), real(0, 0)] ../source3/smbd/smb2_server.c:918(smb2_set_operation_credit)
  smb2_set_operation_credit: requested 1, charge 1, granted 1, current possible/max 1/512, total granted/max/low/range 512/8192/26/512
[2017/10/08 13:37:58.059747,  5, pid=14052, effective(0, 0), real(0, 0)] ../libcli/smb/smb2_signing.c:93(smb2_signing_sign_pdu)
  signed SMB2 message
[2017/10/08 13:37:58.060190, 10, pid=14052, effective(0, 0), real(0, 0)] ../source3/smbd/smb2_server.c:1075(smbd_server_connection_terminate_ex)
  smbd_server_connection_terminate_ex: conn[ipv4:192.168.5.20:52232] reason[NT_STATUS_END_OF_FILE] at ../source3/smbd/smb2_server.c:3930

Advice still stands. Keep away from nightlies if you want stable system.

@anodos: Thank you for taking the time to investigate the problem. Please share any additional findings, if you have time. :)