Koozali.org: home of the SME Server
Contribs.org Forums => Koozali SME Server 10.x => Topic started by: ReetP on July 17, 2020, 04:03:29 PM
-
As mentioned elsewhere, once SMB 1 is removed from Windows 10 you lose the ability to browse samba shares.
You can still map them via IP or server name if SME has the correct SMB version, but you can't browse for them.
Someone kindly wrote this: https://github.com/christgau/wsdd/
After a lot of work from Terry, and some clever bits from Jean Philippe, I have bodged together a contrib for testing on SME v10.
Terry will paste a howto shortly and a link to the rpm.
We are probably going to add this to the core in time.
This is going to be EXCLUSIVE to v10.
Yes, we have got it running SME v9 (it is much trickier) but I am NOT going to release it because we need people to test v10.
If we release it on v9 you won't bother testing v10, and probably won't upgrade for ages. So you have been warned!!
Details to follow soon.
-
John is to modest, there were a few hours went into this for sme10 it was a final tweak from JP that put the shine on it :-) . smeserver-wsdd-0.1-2.noarch.rpm
All that John said above and more..this becomes an essential tool when you upgrade to the new e-smith-samba-2.6.0-10.el7.sme.noarch.rpm and the windows pc does not have smb1 enabled
This is using the resource from upstream hence the need for the epel repo, I suggest you have a look and browse the home of the script and its writer - https://github.com/christgau/wsdd/
The current version of the script is ahead of the epel version, you can do a manual update if that is your want.
SME10
update e-smith-samba package
# yum update e-smith-samba --enablerepo=smeupdates-testing
Note - This is default smb config with updated e-smith-samba and does not need changing
# config show smb
smb=service
DeadTime=10080
KeepVersions=disabled
OpLocks=enabled
OsLevel=35
RecycleBin=disabled
RoamingProfiles=no
ServerName=sme10a5
ServerRole=WS
ShadowCount=10
ShadowDir=/home/e-smith/files/.shadow
UnixCharSet=UTF8
UseClientDriver=yes
Workgroup=sme-server
status=enabled
This then facilitates sme10 being accessable from a win10 PC with smb1 disabled
At this point adding network drives etc manually using an ip is still available
To restore the ability to see a Server under Network in explorer and browse for shares on that resource, wsdd is needed.
Install WSDD
Add EPEL repo
# yum install http://mirror.canada.pialasse.com/releases/9/smeaddons/x86_64/RPMS/smeserver-extrarepositories-epel-0.1-21.noarch.rpm
# signal-event yum-modify
# config set UnsavedChanges no
or
# signal-event post-upgrade; signal-event reboot
# wget https://www.reetspetit.com/smetest/7/noarch/smeserver-wsdd-0.2-1.noarch.rpm
# yum localinstall smeserver-wsdd-0.1-2.noarch.rpm --enablerepo=epel
or
# yum install https://www.reetspetit.com/smetest/7/noarch/smeserver-wsdd-0.2-1.noarch.rpm --enablerepo=epel
# config show wsdd
wsdd=service
TCPPorts=3702,5357
UDPPort=3702
access=private
status=disabled
# db configuration setprop wsdd status enabled
# config show wsdd
wsdd=service
TCPPorts=3702,5357
UDPPort=3702
access=private
status=enabled
# signal-event post-upgrade; signal-event reboot
To update script - replace /usr/bin/wsdd with wsdd.py rename to wsdd and set perms
I did have some issues with softether as I have that installed..
Download SME10A5 and go your hardest, the more that try the better the feedback
-
Just modded one of the URLs Terry.
Note to others.
- We may add some other options to the unit/service file in time
- This allows Broadcast packets on the Internal Interface via a custom masq template - masq should respect the wsdd TCP/UDP ports but doesn't as yet
- The updated samba defaults to ports 139 & 445 - no need to change anything
If someone uses Server & Gateway we'd like to hear from them
If you want to help development of this sort of thing then ask for a Rocker.Chat login and come and talk to us directly. We do not bite, and we are not Gods (well, some of them are... !).
I may even let you into the secrets of running it on v9 ;-)
You do not need to be a coding guru to help. Just interested and enthusiastic.
-
i just put a cherry on the sunday.
You did all the work John.
-
Installed on a server-gateway sme10a5 and browse to server fine from W10 ver. 2004 build 19041.388.
nice one!
-
Installed on a server-gateway sme10a5 and browse to server fine from W10 ver. 2004 build 19041.388.
Thanks mate, server/gateway, nothing crop up? did you copy in the updated wsdd.py file from the git source?
Thanks again for testing...
-
from a win10 powershell default settings on sme10a5, win10 smb1 disabled, interesting that windows negotiates a smb3 connection
PS C:\WINDOWS\system32> Get-SmbConnection
ServerName ShareName UserName Credential Dialect NumOpens
---------- --------- -------- ---------- ------- --------
SME10A5 Primary TERRYSHP\Terry xxxxxxxxxxxxxxxxxxx 3.1.1 2
-
Tried updated wsdd.py from github src, copied to /usr/bin, renamed and set permissions, reboot, python3 service on port 5357 is not running. Restore original wsdd and reboot and browsing the server works again. Will try again
-
Copied in updated wsdd.py and restarted, now working with updated wsdd.
-
Sweet - reading the open and closed issues on git the latest ver tightens up the code and operation - https://github.com/christgau/wsdd/issues and closed issues https://github.com/christgau/wsdd/issues?q=is%3Aissue+is%3Aclosed
-
Nice work Gary, and thank you.
As ever, if you want to help test come and chat to us at our Rocket.Chat instance.
Just PM me with a real name and email and I'll create a login and you can come and help test this sort of thing as we write it!
-
so need to import the source code from epel and update it with github
and import your smeserver package in core.
then have e-smith-samba requires it
-
for those who have had a look at WSDD see this - https://github.com/christgau/wsdd/issues/59
High CPU usage after server reboot · Issue #59 · christgau/wsdd
I recall someone mentioning a high cpu usage issue..