Latest News:
*New 11.2 series Release:
2019-06-20: XigmaNAS 11.2.0.4.6766 - released!

*New 12.0 series Release:
2019-06-20: XigmaNAS 12.0.0.4.6766 - released!

We really need "Your" help on XigmaNAS https://translations.launchpad.net/xigmanas translations. Please help today!

Producing and hosting XigmaNAS costs money. Please consider donating for our project so that we can continue to offer you the best.
We need your support! eg: PAYPAL

New WSD Discovery for Samba Shares

Post/Debate your Suggestions & Requests of XigmaNAS here. This ONLY pertains to XigmaNAS.
Forum rules
Set-Up GuideFAQsForum Rules
User avatar
raulfg3
Site Admin
Site Admin
Posts: 4928
Joined: 22 Jun 2012 22:13
Location: Madrid (ESPAÑA)
Contact:
Status: Offline

Re: New WSD Discovery for Samba Shares

#31

Post by raulfg3 » 09 Apr 2019 12:31

Shperrung wrote:
09 Apr 2019 10:56
Something wrong with WSDD or my installation. python3 says that there is no file/directory.
pkg install python3 was made before.
Permissions 0755 were done.
Xigmanas embedded.

Code: Select all

Last login: Tue Apr  9 09:47:05 2019 from 10.8.0.6
Welcome to XigmaNAS!
xigmanas: ~# pkg install python3
Updating FreeBSD repository catalogue...
FreeBSD repository is up to date.
All repositories are up to date.
Checking integrity... done (0 conflicting)
The most recent version of packages are already installed
xigmanas: ~# /mnt/RAID/scripts/wsdd-0.3/src/wsdd.py -i nicre0 -4 -w WORKGROUP/cd &
[1] 74757
xigmanas: ~# env: python3: No such file or directory
be carefull to install packages on embedded install, because are deleted on reboots.
12.0.0.4 (revision 6766)+OBI on SUPERMICRO X8SIL-F 8GB of ECC RAM, 12x3TB disk in 3 vdev in RaidZ1 = 32TB Raw size only 22TB usable

Wiki
Last changes

netware5
experienced User
experienced User
Posts: 107
Joined: 31 Jan 2017 21:39
Location: Sofia, BULGARIA
Status: Offline

Re: New WSD Discovery for Samba Shares

#32

Post by netware5 » 09 Apr 2019 13:10

raulfg3 wrote:
09 Apr 2019 12:31
be carefull to install packages on embedded install, because are deleted on reboots.
@raulfg3, I thing Shperrung is aware about this. My understanding is that he attempted to run the wsdd.py script immediately after installing Python3, without reboot. My feeling is that for unknown reasons Python3 failed to install.
XigmaNAS 11.2.0.4 - Omnius (rev.6743) embedded on HP Proliant Microserver Gen8, Xeon E3-1265L, 16 GB ECC, 2x4TB WD Red ZFS Mirror

Shperrung
experienced User
experienced User
Posts: 93
Joined: 04 Apr 2018 16:29
Status: Offline

Re: New WSD Discovery for Samba Shares

#33

Post by Shperrung » 09 Apr 2019 15:02

@raulfg3, I know about difference of embedded installation. It's not a problem if it doesn't work at all on my build.
I know what I shared via smb and I can mount it manually. Sometimes it may be useful to avoid someone's interest.
11.2.0.4 - Omnius (revision 6177)
ASRock J3710-ITX, LAN: Realtek RTL8111GR; 16Gb RAM; WD 1Tbx2, WD 2Tb; UPS Powercom WOW500U.

doktornotor
Advanced User
Advanced User
Posts: 182
Joined: 16 May 2017 00:22
Status: Offline

Re: New WSD Discovery for Samba Shares

#34

Post by doktornotor » 09 Apr 2019 21:09

Well, you just need

Code: Select all

rehash
after installing a package.

Shperrung
experienced User
experienced User
Posts: 93
Joined: 04 Apr 2018 16:29
Status: Offline

Re: New WSD Discovery for Samba Shares

#35

Post by Shperrung » 10 Apr 2019 09:34

After

Code: Select all

rehash
python3 or daemon continues send error messages into the log.
You do not have the required permissions to view the files attached to this post.
11.2.0.4 - Omnius (revision 6177)
ASRock J3710-ITX, LAN: Realtek RTL8111GR; 16Gb RAM; WD 1Tbx2, WD 2Tb; UPS Powercom WOW500U.

User avatar
Snufkin
Advanced User
Advanced User
Posts: 283
Joined: 01 Jul 2012 11:27
Location: Etc/GMT-3 (BSD style)
Status: Offline

Re: New WSD Discovery for Samba Shares

#36

Post by Snufkin » 10 Apr 2019 22:56

Checked how the new WS Discovery feature works with Windows 1809 client in Windows work group environment (no AD service). SMBv1 was completely disabled on XNAS server and on Windows client.

Below are my observations.

+ Positive
  1. WSD puts XNAS server icon in Network folder of Windows Explorer. Explorer provides relevant abbreviation "WSD" in table column "Detection method".
  2. Mouse double click on the server icon gives you access to the server share(s).
- Negative
  1. Double-clicking the mouse only works if:
    • NetBIOS over TCP is ENABLED,
    • user credentials are ALREADY stored on the Windows host.
  2. Credentials can only be entered by mapping the network drive and saving user/password data (mapped drive could be disconnected later). "Add network location" option does not work even if the full path to the share is specified.
  3. If NetBIOS is DISABLED you will not be able to:
    • access server shares even with the credentials that were saved before,
    • enter new credentials to access share on another server.
In general, WS Discovery feature seemed to me almost useless, because in any case you need to specify in advance the full path to the share and user credentials.
XNAS 11.2.0.4 embedded, ASUS P5B-E, Intel DC E6600, 4 GB DDR2, 2 x HGST HDN726040ALE614, 2 x WDC WD5000AAKS, Ippon Back Power Pro 400

doktornotor
Advanced User
Advanced User
Posts: 182
Joined: 16 May 2017 00:22
Status: Offline

Re: New WSD Discovery for Samba Shares

#37

Post by doktornotor » 10 Apr 2019 23:18

Well, there's no need to enter any credentials anywhere once you've done things the normal way, i.e.,

- put the NAS to the same workgroup as the Windows box(es)
- create accounts on the NAS matching those on the Windows box(es) - same username/password
- set proper permissions on the share

Now of course if you like to have your life painful, ignore the above... :P

netware5
experienced User
experienced User
Posts: 107
Joined: 31 Jan 2017 21:39
Location: Sofia, BULGARIA
Status: Offline

Re: New WSD Discovery for Samba Shares

#38

Post by netware5 » 11 Apr 2019 09:29

Snufkin wrote:
10 Apr 2019 22:56
Checked how the new WS Discovery feature works with Windows 1809 client in Windows work group environment (no AD service). SMBv1 was completely disabled on XNAS server and on Windows client.

Below are my observations.

+ Positive
  1. WSD puts XNAS server icon in Network folder of Windows Explorer. Explorer provides relevant abbreviation "WSD" in table column "Detection method".
  2. Mouse double click on the server icon gives you access to the server share(s).
- Negative
  1. Double-clicking the mouse only works if:
    • NetBIOS over TCP is ENABLED,
    • user credentials are ALREADY stored on the Windows host.
  2. Credentials can only be entered by mapping the network drive and saving user/password data (mapped drive could be disconnected later). "Add network location" option does not work even if the full path to the share is specified.
  3. If NetBIOS is DISABLED you will not be able to:
    • access server shares even with the credentials that were saved before,
    • enter new credentials to access share on another server.
In general, WS Discovery feature seemed to me almost useless, because in any case you need to specify in advance the full path to the share and user credentials.
My observations are opposite. I confirm that I am able to do everything above with NetBIOS disabled and WSD enabled.
XigmaNAS 11.2.0.4 - Omnius (rev.6743) embedded on HP Proliant Microserver Gen8, Xeon E3-1265L, 16 GB ECC, 2x4TB WD Red ZFS Mirror

User avatar
Snufkin
Advanced User
Advanced User
Posts: 283
Joined: 01 Jul 2012 11:27
Location: Etc/GMT-3 (BSD style)
Status: Offline

Re: New WSD Discovery for Samba Shares

#39

Post by Snufkin » 12 Apr 2019 23:12

doktornotor wrote:
10 Apr 2019 23:18
Well, there's no need to enter any credentials anywhere once you've done things the normal way
Fully agree with you, beeing well prepared one can avoid most of the problem in tricky use cases.
netware5 wrote:
11 Apr 2019 09:29
My observations are opposite. I confirm that I am able to do everything above with NetBIOS disabled and WSD enabled.
You may have Zeroconf/Bonjour service running on your server.
I think I was able to narrow down the causes of the problem I had to face.

To make Samba shares visible and accessible following features are available on the server and the client:
  • XNAS server
    1. Zeroconf/Bonjour service (mDNSResponderPosix daemon)
    2. WSD service (daemonized wsdd.py script)
  • MS Windows client
    1. WSD service (Function Discovery Provider Host and Function Discovery Resource Publication services)
    2. NetBIOS over TCP/IP (NBT) services
If either NetBIOS is enabled on the client or Zeroconf/Bonjour on the server, no errors occur.
Windows client name resolution works just fine when you connect SAMBA share, and command line ping confirms this.

But if I use WSD only on the server and the client, then I have an infamous Windows error 53 "Network path is not found". Pinging by server name gives unknown IP address reply.
At the same time, the correct IP address is clearly indicated in the MS Windows Explorer network folder.
This may sound strange, but somehow Windows client can show server IP address, but can't resolve it.

To understand what is happening on the Windows client one must use WSD debugging tools and I think it's too much to enable double-clicking the server icon in Windows Explorer, right?

And for the time being, my choice is in favor of NetBIOS option that comes by default in MS Windows.
XNAS 11.2.0.4 embedded, ASUS P5B-E, Intel DC E6600, 4 GB DDR2, 2 x HGST HDN726040ALE614, 2 x WDC WD5000AAKS, Ippon Back Power Pro 400

netware5
experienced User
experienced User
Posts: 107
Joined: 31 Jan 2017 21:39
Location: Sofia, BULGARIA
Status: Offline

Re: New WSD Discovery for Samba Shares

#40

Post by netware5 » 13 Apr 2019 12:39

Snufkin wrote:
12 Apr 2019 23:12

You may have Zeroconf/Bonjour service running on your server.
............
I don't run Zeroconf/Bonjour service on my server. And also my windows client confirms that WSD has been used to discover server shares.
XigmaNAS 11.2.0.4 - Omnius (rev.6743) embedded on HP Proliant Microserver Gen8, Xeon E3-1265L, 16 GB ECC, 2x4TB WD Red ZFS Mirror

doktornotor
Advanced User
Advanced User
Posts: 182
Joined: 16 May 2017 00:22
Status: Offline

Re: New WSD Discovery for Samba Shares

#41

Post by doktornotor » 13 Apr 2019 18:11

Snufkin wrote:
12 Apr 2019 23:12
And for the time being, my choice is in favor of NetBIOS option that comes by default in MS Windows.
Yes, that's something that does not work at all when SMBv1 is disabled/not installed.

sleyk2010
Starter
Starter
Posts: 21
Joined: 22 Nov 2018 03:30
Status: Offline

Re: New WSD Discovery for Samba Shares

#42

Post by sleyk2010 » 23 Apr 2019 22:54

+1 with @Netware, Can confirm this still works well for me with zero issues. Able to reboot at will anytime I like and Python3 re-installs like a champ from the post init scripts, and runs the wsdd script and functions correctly.

Try Dok's method for daemon or try the 4 post init script method. Both should work great.

I keep SMB1 disabled and disable Netbios over TCP/IP. I do run Zero bonjour services on my Xigma.

You do NOT need to use Netbios at anytime anymore. But to each their own :.)

bewoco
Starter
Starter
Posts: 24
Joined: 23 Apr 2015 14:26
Location: Germany
Status: Offline

Re: New WSD Discovery for Samba Shares

#43

Post by bewoco » 07 Jun 2019 20:15

+1 @netware
WSD discovery works perfect for me.
SMB1 disabled, Netbios disabled, Zeroconf bonjour running on XigmaNAS.
Windows 10 shows the XigmaNAS in its network environment as detected by WSD.

The WSDD.py script runs as a daemon as described above.

Small improvement:
Python3 downloaded to NAS once and stored on disk permanently. So no further download at each boot:
pkg fetch -d -o / .. path to cache …/ python3
from commandline. Check cache location.

Instead of
pkg install python3
as postinit command I use
pkg add -q /.. path to pkgcache .. /python3-3_3.txz
NAS4Free 11.2.0.4 (revision 6766) x64-embedded on HP ProLiant N54L with AMD Turion(tm) II Neo Dual-Core Processor 4096 MB ECC RAM;
NAS4Free 11.2.0.4 (revision 6625) x64-embedded on Acer H341 with Intel Atom D410 4MB RAM

User avatar
raulfg3
Site Admin
Site Admin
Posts: 4928
Joined: 22 Jun 2012 22:13
Location: Madrid (ESPAÑA)
Contact:
Status: Offline

Re: New WSD Discovery for Samba Shares

#44

Post by raulfg3 » 07 Jun 2019 22:02

I want to ask developers if planned to add WSD as base on next releases so no need to install by hand.
12.0.0.4 (revision 6766)+OBI on SUPERMICRO X8SIL-F 8GB of ECC RAM, 12x3TB disk in 3 vdev in RaidZ1 = 32TB Raw size only 22TB usable

Wiki
Last changes

User avatar
zoon01
Developer
Developer
Posts: 747
Joined: 20 Jun 2012 21:06
Location: Netherlands
Contact:
Status: Offline

Re: New WSD Discovery for Samba Shares

#45

Post by zoon01 » 07 Jun 2019 22:23

Sorry this wont make it on time to first 12 stable release, we will soon switch to python3.

Hope that answered your question for now.
System specs: XigmaNAS 11.2.0.4 -embedded on Samsung 860 EVO 256GB and Supermicro X10SL7-F w / Bios v3.2, IPMI v.03.77 / CPU E3-1241 v3 @ 3.50GHz - 32GB Crucial DDR3L 1600mhz ECC 1.35v , LSI 2308 on PH20.00.07.00 IT mode, Storage: 5x Western Digital Red (WD30EFRX) raidz

Development system is same system in virtualbox.

bewoco
Starter
Starter
Posts: 24
Joined: 23 Apr 2015 14:26
Location: Germany
Status: Offline

Re: New WSD Discovery for Samba Shares

#46

Post by bewoco » 20 Jun 2019 19:48

@zoon1:
Thanks, xigmanas' switch to python 3 eliminates the need for download and installation of python 3 in embedded systems at postinit.
So only the WSD script has to be started.

By the way: C implementation of a WSD daemon: https://github.com/Andy2244/wsdd2
NAS4Free 11.2.0.4 (revision 6766) x64-embedded on HP ProLiant N54L with AMD Turion(tm) II Neo Dual-Core Processor 4096 MB ECC RAM;
NAS4Free 11.2.0.4 (revision 6625) x64-embedded on Acer H341 with Intel Atom D410 4MB RAM

Post Reply

Return to “Suggestions & Requests”