Some diagnostic ideas -
1. Test from the workstation end
Do you have a workstation running a newer version of Windows, or even a non-critical workstation running WinXP?
If so, you could safely play with settings on that workstation to help figure out what changed on SME.
2. Test from the SME server end
Can you "stand up" a virtual SME server running an old version?
I had a problem after an upgrade a couple years ago which I tracked down by standing up an old version and comparing the template fragments under /etc/e-smith/templates and /etc/e-smith/tempaltes-custom between the two systems.
3. Research specific changes
If you can get a copy of the old e-smith-samba that your server was running, you can identify all the changed files as shown below, which may point you in a useful direction...
- My server is running e-smith-samba-2.6.0-28.el7.sme.noarch
- The smeos-10 repo contains e-smith-samba-2.6.0-26.el7.sme.noarch.rpm
I identified the changed files between these two versions like this:
# make a workspace...
mkdir tmp
cd tmp
# get the old rpm
wget http://mirror.pialasse.com/releases/10/smeos/x86_64/Packages/e-smith-samba-2.6.0-26.el7.sme.noarch.rpm
# extract the old rpm
mkdir e-smith-samba
cd e-smith-samba
rpm2cpio ../e-smith-samba-2.6.0-26.el7.sme.noarch.rpm |cpio -idmv
# use md5sum to list the changed files
# ("${x:1}" is $x from the 2nd char to the end...)
find . -type f |while read x; do old=$(md5sum "$x" |cut -d\ -f1); new=$(md5sum "${x:1}" |cut -d\ -f1); if [[ "$new" != "$old" ]]; then echo ${x:1}; fi; done
For 2.6.0-26 (above) this process identifies:
/etc/e-smith/events/actions/update-domain-group-maps
/home/e-smith/files/server-resources/regedit/win10samba.reg
For 2.6.0-23 on the SME 10.0 installer iso:
/etc/e-smith/events/actions/update-domain-group-maps
/etc/e-smith/events/actions/user-create-profiledir
/etc/e-smith/events/actions/user-delete-profiledir
/home/e-smith/files/server-resources/regedit/win10samba.reg
4. Compare your configuration settings to the new default settings
for svc in nmbd smb smbd masq; do
cd /etc/e-smith/db/configuration/defaults/$svc
printf "$(config show $svc |head -1)\t$(cat type)\n"
find . -type f ! -name type |while read s; do printf " ${s:2}\t$(config getprop $svc ${s:2})\t$(cat ${s})\n"; done
printf "\n"
done
Output on my system:
nmbd=service service
UDPPorts 137,138 137,138
access private private
status enabled enabled
smb=service service
DeadTime 10080 10080
KeepVersions enabled disabled
OpLocks enabled enabled
OsLevel 35 35
RecycleBin enabled disabled
RoamingProfiles no no
ServerRole PDC WS
ShadowCount 10 10
ShadowDir /home/e-smith/files/.shadow /home/e-smith/files/.shadow
UnixCharSet UTF8 UTF8
UseClientDriver yes yes
Workgroup mmsi sme-server
status enabled enabled
smbd=service service
TCPPorts 139,445 139,445
access private private
status enabled enabled
masq=service service
DenylogTarget drop drop
Logging most most
Stealth no no
Trace disabled disabled
pptp yes yes
status enabled enabled
5. Final Notes
While researching this I ran across some notes hinting that the syntax for ServerMinProtocol may have changed. You should review the settings you had previously for ServerMinProtocol and make sure they're actually making it into /etc/samba/smb.conf:
# grep protocol /etc/samba/smb.conf
client max protocol = SMB3
server max protocol = SMB3
client min protocol = SMB2
server min protocol = SMB2
9 Replies
2819 Views