Administrative, Business, Mathematics, Technology and Society

Is There A Samba Doctor In The House?

10 Comments

As is often the case, Samba has me pulling hair, of which I have little to spare.

First of all, yes, I’ve read this.

As a user on the server itself:

[pat@Pat_Linux ~]$ smbclient //192.168.1.11/home/pat/Windows_Drive
Enter pat’s password:
Domain=[INTERGLOBAL] OS=[Unix] Server=[Samba 4.1.17]
tree connect failed: NT_STATUS_BAD_NETWORK_NAME
[pat@Pat_Linux ~]$

Here’s a tail of the log:

[2015/03/16 11:45:55.783210, 3] ../auth/ntlmssp/ntlmssp_util.c:34(debug_ntlmssp_flags)
Got NTLMSSP neg_flags=0x60088215
[2015/03/16 11:45:55.783449, 3] ../source3/auth/token_util.c:540(finalize_local_nt_token)
Failed to fetch domain sid for INTERGLOBAL
[2015/03/16 11:45:55.783501, 3] ../source3/auth/token_util.c:571(finalize_local_nt_token)
Failed to fetch domain sid for INTERGLOBAL
[2015/03/16 11:45:55.783804, 3] ../source3/smbd/password.c:144(register_homes_share)
Adding homes service for user ‘pat’ using home directory: ‘/home/pat’
[2015/03/16 11:45:55.783867, 3] ../source3/param/loadparm.c:1726(lp_add_home)
adding home’s share [pat] for user ‘pat’ at ‘/home/pat’

From “Global” portion of smb.conf:

workgroup = interglobal
server string = Samba Server Version %v

; netbios name = pat_linux

; interfaces = lo eth0 192.168.12.2/24 192.168.13.2/24
; hosts allow = 127. 192.168.12. 192.168.13.

; max protocol = SMB2

Standalone:

security = user
; passdb backend = tdbsam

Domain Controller section is the default. Pretty much everything is default. Here’s Shares

[homes]
comment = Home Directories
browseable = no
writable = yes
; valid users = %S
; valid users = MYDOMAIN\%S

[printers]
comment = All Printers
path = /var/spool/samba
browseable = no
; guest ok = no
; writable = No
printable = yes

# Un-comment the following and create the netlogon directory for Domain Logons:
; [netlogon]
; comment = Network Logon Service
; path = /var/lib/samba/netlogon
; guest ok = yes
; writable = no
; share modes = no

# Un-comment the following to provide a specific roving profile share.
# The default is to use the user’s home directory:
; [Profiles]
; path = /var/lib/samba/profiles
; browseable = no
; guest ok = yes

# A publicly accessible directory that is read only, except for users in the
# “staff” group (which have write permissions):
; [public]
; comment = Public Stuff
; path = /home/samba
; public = yes
; writable = yes
; printable = no
; write list = +staff

[Windows_Drive]
path = /home/pat/Windows_Drive
; available = yes
valid users = pat
read only = no
; browseable = yes

I’ve set up a samba password for user “pat.” Why is it trying to fetch a domain sid, and why is it failing (if that’s what’s causing the problem)?

[Late-evening update]

I had posted this question to the Fedora fora earlier today.

The response? Crickets.

This isn’t even a desktop issue; it’s a server issue. And no one over at Fedora can figure it out, or even try?

10 thoughts on “Is There A Samba Doctor In The House?”

    1. Yes.

      Which I’m sure complicates things even more, but I haven’t even gotten to that headache. I’m just trying to get it to work on host, from host.

      1. Rand, I can’t stress this enough: for the love of god, just try VirtualBox. 🙂 I don’t usually tell people to use some other program instead of the one they want to use, but I think this is a worthy exception. If you’ve spent more than an hour messing with QEMU, you are already behind where you would be with VirtualBox.

        For the cost of a few clicks on a very clean interface, you can share any folder on the host with the client, and control access permissions.

        There is no pain here. You could start a Windows install from scratch and have complete audio/video support, shared folders, and USB support in less than an hour.

        This is how it works:
        1) Install VirtualBox from https://www.virtualbox.org/wiki/Linux_Downloads
        2) Install the extension pack from https://www.virtualbox.org/wiki/Downloads

        Install Windows in the virtual machine. Once the install is done, click on Devices->Install guest additions CD image. Run the installer on the CD that mounts in your Windows guest. This installs custom video, mouse and shared folder drivers in Windows.

        Congratulations, at this point, you can do anything you need to do by editing the settings for your VM in the nice clean GUI provided.

        At least give it a try and decide which one works better for you. There is nothing stopping you from running both VMs side by side while you play.

          1. Just in case it matters, VirtualBox supports dynamic disk files, which only take up space used within the drive. That is, you can specify a 50 gig drive within a file, and the file will only take 10 gigs if that is what is used on the drive within it.

        2. I’ll check it out, but I want to get Samba running regardless. It’s not just for the virtual machine to talk to the physical drive. I do have a mixed network of Linux/Windows.

  4. Rand,
    I’ve set up Samba shares before, but long long ago.
    What I’d recommend as a test case is to follow the examples verbatim. Create a fake user and create a share around that user as shown exactly in the example provided in your link. Given your sample smb.conf file it looks like you are trying to set up a share directory that is different from the user’s home directory (in fact a subdirectory thereof).
    In past lives managing Linux/Windows shares I found it behooved me to first follow examples VERBATIM, even if they were not configured the way I want them, in order to make sure the verbatim steps work. Usually they do. Of course that gives me a share that doesn’t work the way I want. But once I have the working baseline, I work mods from there to *incrementally* get to where I want to be. Usually I’ll uncover the root cause to the original setup issue during those incremental changes and with a lot more understanding of what is happening by the time I get there. FYI I found that the same approach works for establishing Linux firewalls btw.
    So in brief, follow *exactly* the canned examples to make sure that baseline works, then extend out from there.
    If you get stuck getting a canned example to work or can’t figure out why a mod you want to make away from the baseline example isn’t working you can try emailing the original author of the cited “link” at the beginning of your post.

    Good Luck,
    Dave

Comments are closed.