Anyone know where the smb.conf file is located? I would like to take a look at it's content.
MacBook Pro (Retina, 15-inch, Early 2013), OS X Mavericks (10.9.4)
If you mean nsmb.conf(5), it doesn't exist by default, but if you had one, it would be in /etc.
jhoogeboom wrote:
Anyone know where the smb.conf file is located? I would like to take a look at it's content.
smb.conf is the configuration file for Samba, and that was removed in OS X Server 10.7.
If you've installed Samba separately or are running OS X Server 10.6 or earlier...
From the command line, one or both of the following commands can be used to locate the specified file, or most any other file...
locate smb.conf
mdfind smb.conf
The locate command might not be activated on your system — if it's not, you'll get a diagnostic showing how to do that. The mdfind command uses Spotlight to query for its data, and that is usually is enabled.
The default location for the Samba smb.conf configuration file was in /etc on most systems, including on OS X Server 10.6 and earlier.
To avoid confusion, it's still possible to create a file at /etc/nsmb.conf to modify the configuration of the SMB server. The details are in the man page indicated in my first comment.
It seems I had the (I guess) erroneous belief that the OS X samba server was a direct port or implementation of the linux samba one including it's configuration file and syntax (like smb.conf). I have OS X server running it's file sharing over SMB in the local network but also remotely without problem, sadly remote ubuntu servers exposing their samba shares over the internet cannot be connected to from my OS X machine (bad practise I know, but recently smb supports encryption it seems). Ubuntu clients with smbclient can connect just fine, so I was trying perhaps to replicate OS X server's smb.conf settings in order to emulate a better support for connection.
jhoogeboom wrote:
It seems I had the (I guess) erroneous belief that the OS X samba server was a direct port or implementation of the linux samba one...
The Samba project changed the associated software license at their 3.2 release, which reportedly led Apple to create and migrate to their own CIFS/SMB implementation. Samba 4.0 had substantial changes to authentication.
You'll probably need to have a look at the Ubuntu Samba server logs for clues around the failure, if you've not already done so.
Whether the OS X CIFS/SMB client supports encryption, I don't know.
And a possibly-interesting discussion from else-forum...
Thanks MrHoffman, I've tried to up the log level of the samba server logs:
[2015/12/14 11:06:52.043900, 2] ../source3/smbd/server.c:437(remove_child_pid)
Could not find child 1193 -- ignoring
[2015/12/14 11:07:52.108755, 2] ../source3/smbd/server.c:437(remove_child_pid)
Could not find child 1195 -- ignoring
[2015/12/14 11:08:52.173667, 2] ../source3/smbd/server.c:437(remove_child_pid)
Could not find child 1201 -- ignoring
[2015/12/14 11:09:52.238582, 2] ../source3/smbd/server.c:437(remove_child_pid)
Could not find child 1205 -- ignoring
[2015/12/14 11:10:52.303318, 2] ../source3/smbd/server.c:437(remove_child_pid)
Could not find child 1206 -- ignoring
but I only get this bug that has something todo with CUPS printers that's apparently still around. No connection attempt is even mentioned in the logs.
Also tried the possibly-interesting discussion, seems their issue was having public shares, but even that did not work for me.
Thanks, I didn't know there was a client-side configuration side as well. Someone suggested here to have the server side conf include a encrypt passwords = yes, but also to set minauth=none on the client side. Still nothing though.
I found a little program called smbutil that showed me something new:
smbutil status 62.xxx.xxx.xxx
Operation timed out: unable to get status from 62.xxx.xxx.xxx using address 62.xxx.xxx.xxx
already tried upping the nbtimeout, but no luck yet.
I installed OpenVPN on my ubuntu server and connected my mac to the server through VPN, I can access the shares just fine this way using the local address. So the issue seems more firewall-ish / port related. Any clue what this could be? Any tips/starters on how do I investigate this? tried turning off the firewall on my mac (which I think only blocks inbound traffic anyway), but also timeout.
jhoogeboom wrote:
I installed OpenVPN on my ubuntu server and connected my mac to the server through VPN, I can access the shares just fine this way using the local address. So the issue seems more firewall-ish / port related. Any clue what this could be? Any tips/starters on how do I investigate this? tried turning off the firewall on my mac (which I think only blocks inbound traffic anyway), but also timeout.
Look at the firewall logs.
Debugging in recent years is all about finding and reading logs, and — where and when available and necessary — determining how to log yet more data to read.
I'd strongly encourage sticking with the VPN access here, in any case. I really don't like folks poking random packets at file servers. They will poke, too. This if for no other reason than random poking adds yet more data onto the file server logs. Data I end up sifting through, or that the log-sifting and anomoly-detection tools then have to be configured to ignore. If there's not some vulnerability discovered in the underlying services. The time to exploit tends to be pretty quick these days. Often faster than the problem can be identified and fixed, and faster than many of the folks can then get notified and deploy the patches, too.
VPN access seems like the way to go. I found out why it's not working too, apparently my ISP is blocking port 139 and 445.
jhoogeboom wrote:
VPN access seems like the way to go. I found out why it's not working too, apparently my ISP is blocking port 139 and 445.
Port blocks on ISP residential tiers of service for server-oriented protocols are fairly common.
osx server smb.conf location
