Posts made by biggen

This appears to be for ARM only from what I’ve read.

So I think I "may" have fixed it. I upped the logging level in Samba and noticed that it was a NTLM auth problem.

So I added ntlm auth = yes which allows NTLMv1 clients to connect in the smb.conf file.

SAMBA 4.5 changed the default method of NTLM to NTLMv2 clients only. Older clients that don't use NTLMv2 can't connect without changing this setting.

What a PITA that was to diagnose.

(https://www.samba.org/samba/docs/current/man-html/smb.conf.5.html)

@Romo

Sure. Its pretty bare bones. Its basically a default smb.conf file with only a single share I added to the end.

[global]

## Browsing/Identification ###

# Change this to the workgroup/NT-domain name your Samba server will part of
   workgroup = WORKGROUP

# server string is the equivalent of the NT Description field
	server string = %h server (Samba, Ubuntu)

# Windows Internet Name Serving Support Section:
# WINS Support - Tells the NMBD component of Samba to enable its WINS Server
#   wins support = no

# WINS Server - Tells the NMBD components of Samba to be a WINS Client
# Note: Samba can be either a WINS Server, or a WINS Client, but NOT both
;   wins server = w.x.y.z

# This will prevent nmbd to search for NetBIOS names through DNS.
   dns proxy = no

#### Networking ####

# The specific set of interfaces / networks to bind to
# This can be either the interface name or an IP address/netmask;
# interface names are normally preferred
;   interfaces = 127.0.0.0/8 eth0

# Only bind to the named interfaces and/or networks; you must use the
# 'interfaces' option above to use this.
# It is recommended that you enable this feature if your Samba machine is
# not protected by a firewall or is a firewall itself.  However, this
# option cannot handle dynamic or non-broadcast interfaces correctly.
;   bind interfaces only = yes



#### Debugging/Accounting ####

# This tells Samba to use a separate log file for each machine
# that connects
   log file = /var/log/samba/log.%m

# Cap the size of the individual log files (in KiB).
   max log size = 1000

# If you want Samba to only log through syslog then set the following
# parameter to 'yes'.
#   syslog only = no

# We want Samba to log a minimum amount of information to syslog. Everything
# should go to /var/log/samba/log.{smbd,nmbd} instead. If you want to log
# through syslog you should set the following parameter to something higher.
   syslog = 0

# Do something sensible when Samba crashes: mail the admin a backtrace
   panic action = /usr/share/samba/panic-action %d


####### Authentication #######

# Server role. Defines in which mode Samba will operate. Possible
# values are "standalone server", "member server", "classic primary
# domain controller", "classic backup domain controller", "active
# directory domain controller". 
#
# Most people will want "standalone sever" or "member server".
# Running as "active directory domain controller" will require first
# running "samba-tool domain provision" to wipe databases and create a
# new domain.
   server role = standalone server

# If you are using encrypted passwords, Samba will need to know what
# password database type you are using.  
   passdb backend = tdbsam

   obey pam restrictions = yes

# This boolean parameter controls whether Samba attempts to sync the Unix
# password with the SMB password when the encrypted SMB password in the
# passdb is changed.
   unix password sync = yes

# For Unix password sync to work on a Debian GNU/Linux system, the following
# parameters must be set (thanks to Ian Kahan <<[email protected]> for
# sending the correct chat script for the passwd program in Debian Sarge).
   passwd program = /usr/bin/passwd %u
   passwd chat = *Enter\snew\s*\spassword:* %n\n *Retype\snew\s*\spassword:* %n\n *password\supdated\ssuccessfully* .

# This boolean controls whether PAM will be used for password changes
# when requested by an SMB client instead of the program listed in
# 'passwd program'. The default is 'no'.
   pam password change = yes

# This option controls how unsuccessful authentication attempts are mapped
# to anonymous connections
   map to guest = bad user

########## Domains ###########

#
# The following settings only takes effect if 'server role = primary
# classic domain controller', 'server role = backup domain controller'
# or 'domain logons' is set 
#

# It specifies the location of the user's
# profile directory from the client point of view) The following
# required a [profiles] share to be setup on the samba server (see
# below)
;   logon path = \\%N\profiles\%U
# Another common choice is storing the profile in the user's home directory
# (this is Samba's default)
#   logon path = \\%N\%U\profile

# The following setting only takes effect if 'domain logons' is set
# It specifies the location of a user's home directory (from the client
# point of view)
;   logon drive = H:
#   logon home = \\%N\%U

# The following setting only takes effect if 'domain logons' is set
# It specifies the script to run during logon. The script must be stored
# in the [netlogon] share
# NOTE: Must be store in 'DOS' file format convention
;   logon script = logon.cmd

# This allows Unix users to be created on the domain controller via the SAMR
# RPC pipe.  The example command creates a user account with a disabled Unix
# password; please adapt to your needs
; add user script = /usr/sbin/adduser --quiet --disabled-password --gecos "" %u

# This allows machine accounts to be created on the domain controller via the 
# SAMR RPC pipe.  
# The following assumes a "machines" group exists on the system
; add machine script  = /usr/sbin/useradd -g machines -c "%u machine account" -d /var/lib/samba -s /bin/false %u

# This allows Unix groups to be created on the domain controller via the SAMR
# RPC pipe.  
; add group script = /usr/sbin/addgroup --force-badname %g

############ Misc ############

# Using the following line enables you to customise your configuration
# on a per machine basis. The %m gets replaced with the netbios name
# of the machine that is connecting
;   include = /home/samba/etc/smb.conf.%m

# Some defaults for winbind (make sure you're not using the ranges
# for something else.)
;   idmap uid = 10000-20000
;   idmap gid = 10000-20000
;   template shell = /bin/bash

# Setup usershare options to enable non-root users to share folders
# with the net usershare command.

# Maximum number of usershare. 0 (default) means that usershare is disabled.
;   usershare max shares = 100

# Allow users who've been granted usershare privileges to create
# public shares, not just authenticated ones
   usershare allow guests = yes

#======================= Share Definitions =======================

# Un-comment the following (and tweak the other settings below to suit)
# to enable the default home directory shares. This will share each
# user's home directory as \\server\username
;[homes]
;   comment = Home Directories
;   browseable = no

# By default, the home directories are exported read-only. Change the
# next parameter to 'no' if you want to be able to write to them.
;   read only = yes

# File creation mask is set to 0700 for security reasons. If you want to
# create files with group=rw permissions, set next parameter to 0775.
;   create mask = 0700

# Directory creation mask is set to 0700 for security reasons. If you want to
# create dirs. with group=rw permissions, set next parameter to 0775.
;   directory mask = 0700

# By default, \\server\username shares can be connected to by anyone
# with access to the samba server.
# Un-comment the following parameter to make sure that only "username"
# can connect to \\server\username
# This might need tweaking when using external authentication schemes
;   valid users = %S

# Un-comment the following and create the netlogon directory for Domain Logons
# (you need to configure Samba to act as a domain controller too.)
;[netlogon]
;   comment = Network Logon Service
;   path = /home/samba/netlogon
;   guest ok = yes
;   read only = yes

# Un-comment the following and create the profiles directory to store
# users profiles (see the "logon path" option above)
# (you need to configure Samba to act as a domain controller too.)
# The path below should be writable by all users so that their
# profile directory may be created the first time they log on
;[profiles]
;   comment = Users profiles
;   path = /home/samba/profiles
;   guest ok = no
;   browseable = no
;   create mask = 0600
;   directory mask = 0700

[printers]
   comment = All Printers
   browseable = no
   path = /var/spool/samba
   printable = yes
   guest ok = no
   read only = yes
   create mask = 0700

# Windows clients look for this share name as a source of downloadable
# printer drivers
[print$]
   comment = Printer Drivers
   path = /var/lib/samba/printers
   browseable = yes
   read only = yes
   guest ok = no
# Uncomment to allow remote administration of Windows print drivers.
# You may need to replace 'lpadmin' with the name of the group your
# admin users are members of.
# Please note that you also need to set appropriate Unix permissions
# to the drivers directory for these users to have write rights in it
;   write list = root, @lpadmin


[rightcorner]
   path = /mnt/cam_drive/rightcorner
   browseable = no
   read only = no
   valid users = rightcorner

I tried min protocol = NT1 and max protocol = NT1 which I believe are SMB1. Neither allowed the cams to connect. I verified that the server was actually using NT1 by using a Windows client and connected to the samba share. I then used smbstatus to verify my windows box connected to the share via the NT1/SMB1 protocol.

I'm at a bit of a loss. There is something hampering the communication between these old cams and my samba server. They are on the same subnet so I can rule out any weird routing configuration.

@Reid-Cooper

Unfortunately no. Not at all.

max protocol = SMB1

Does not work. I think they changed it to “NT1” at some point.

But even with NT1, the cameras still won’t connect. I know the SAMBA server is working as I can use the same username/pass and connect via a Win10 box.

I’ve got a ticket open with Axis. It’s aggravating because they all used to work on an older Ubuntu 14 server a few years ago before they were temporarily shelved. Now that I’m bringing these old camera back to life, the SMB landscape has changed and stuff that worked once with ease has turned into a headache.

@JaredBusch

Well sure but they can’t actually turn off SMB on an IP camera...

Scott,

Unfortunately these cams are so old that Axis doesn’t update them anymore accept for security fixes. So I doubt these will ever get SMB2+.

I tried min protocol SMB1 before but got an error from testparm that says “unknown parameter” or something of the sort. So that’s when I also tried “NT1” as according to the SAMBA man page, NT1 seems to be the level right below SMB2. But that also doesn’t work either... Strange.

Anyone have any experience with older Axis cams running firmware that only allows you to mount shares via SMB1?

I can't seem to get any of my old Axis cameras to mount shares on my SAMBA server running Ubuntu 18.04. I found this little tidbit from Axis: https://www.axis.com/support/faq/FAQ116392

The cameras in question are indeed running firmware that is before 5.90. So according to that Axis FAQ, they should only support SMB1. But they do not connect to a default smb.conf file. Did SAMBA remove support for SMB1 by default?

I've tried adding to the smb.conf file

server min protocol = NT1
client min protocol = NT1

However, the cameras still won't connect. The errors I'm getting for on the camera logs themselves are:

<CRITICAL> Nov 10 16:55:04 axis-00408cdbbd05 kernel: [72008.090000] CIFS VFS: Send error in SessSetup = -13
<CRITICAL> Nov 10 16:55:04 axis-00408cdbbd05 kernel: [72008.210000] CIFS VFS: Send error in SessSetup = -13
<WARNING > Nov 10 16:55:04 axis-00408cdbbd05 disks[1133]: mount_disks.c : Disk 'NetworkShare0' NOT mounted (due to error) (4)

I'm wondering if its the SAMBA server itself that simply isn't honoring a SMB1 connection. Is there a trick to making sure that SMB1 is still being supported on Linux/SAMBA for legacy devices?

@stacksofplates Ah ok. I misread the script last night when I was looking it over. I thought since it was renaming it “snapshot” that it wasn’t copying the base image. I missed the $diskpath variable at the top of the script. Thanks for clearing that up!

This is a handy little script. I ended up installing the QEMU guest agent in my VM so I’ll add the “—quiesce” switch to the backup command line. Thanks for sharing this!

@stacksofplates I know this is an old thread but I have a question about this script. Why are you backing up the snapshot? Shouldn't the base image be backed up instead right before the block commit? Therefore, if you want to roll back, you just copy the original base image out of your specified backup directory back over the broken base image and away you go.

Unless I don't understand how external snapshots work, I don't see the purpose holding onto a snapshot AFTER you have committed it. The base image before the commit is the "backup" that's needed.

I appreciate the help guys. I'll start experimenting with XenServer and see what I can break on a perfectly working system...

Not being familiar with XenServer the last command "xe sr-create" is new to me.

Once XenServer is installed and I create my desired MD RAID devices via the CLI, can I not use a GUI to add them to XenServer as datastores?

Just so I'm clear on that link that Dustin provided (but looks like Scott wrote), I can install XenServer on a USB stick, put my VM's on a RAID 1 SSD datastore and my actual media for my NAS on a separate RAID 1 winchester?

Mdadm can manage both arrays like this?

I know that guide was for RAID 10 but I can adjust it pretty easily for twin RAID 1 arrays.

Thanks Scott that is very helpful. I've enjoyed playing around with MD on my Ubuntu Server. Learned a ton. I think moving it to a VM via XenServer sounds like another good learning expierence.

Wow I got a crash course in the finer naming art of Xen. Very cool. BTW, I should have kept my same username name from Spiceworks when I joined here. I recognize both Dustin and SAM from over there.

I'll check out that tut you linked to Dustin. Would I be correct in saying that while Mdadm works just fine it isn't really "supported" in this configuration with Xen? In other words, is this not something you would do on a production machine?

I currently run ESXi in my business for production. However, I'd like to try out Xen at home as I have heard so many good things about it.

I currently have a physical Ubuntu Plex/Nas server at home. Ubuntu is installed on a single SSD while my media for the NAS is installed on a 6TB mirror being managed and run by mdadm. This box has no hardware RAID and I'd like to keep it that way.

What's my path here to virtualize this host via Xen whilst using mdadm? I'd like to get an additional SSD so that I can run a mirror for the VM datastores and a mirror for my actual media. From what I have read, one seems to kind of have to hack Xen in order for it to play nice with Mdadm. Was Xen only designed to be run via Hardware Raid?

I'm also confused on what I would need to download. Is Xenserver the proper download or is it just "Xen"?