Project

General

Profile

Bug #72099

Implement WS-Discovery to fix FreeNAS disappearance from Windows Network Browser after SMB/1.0 is deprecated.

Added by Grzegorz Krzystek over 1 year ago. Updated over 1 year ago.

Status:
Done
Priority:
No priority
Assignee:
Andrew Walker
Category:
Services
Seen in:
Severity:
New
Reason for Closing:
Reason for Blocked:
Needs QA:
No
Needs Doc:
No
Needs Merging:
No
Needs Automation:
No
Support Suite Ticket:
n/a
Hardware Configuration:
ChangeLog Required:
No

Description

Background:
Windows Explorer Network Browser is not showing FreeNAS in Neighbor if Windows 10 don't have SMB/1.0 enabled and we don't force SMB/1.0 Compatibility in SAMBA.
Because SMB/1.0 is buggy deprecated it's bad idea to enable it.
Problem: Nas is not visible to windows 10 computer in network browser. and for masive nontechnical users accessing via putting address \\MyNAS\ is unhandy.

Solution to this problem acorrding to https://support.microsoft.com/en-ca/help/4034314/smbv1-is-not-installed-by-default-in-windows is implementation of WS-Discovery protocol.

There is ready component (python script on MIT licence that covers that problem)
https://github.com/christgau/wsdd
i successfuylly tested it on my freenas 11.1-U7
IMHO it's hadny to have NAS just visible for windows 10 users as an icon in Explorer in Network Section.


Related issues

Has duplicate FreeNAS - Feature #75505: Add WSDD to the build + GUI, to replace SMB1 which is highly unsafe+withdrawn, but is also relied on for Windows Neighbourhood to discover FreeNAS CIFS sharesClosed
Copied to FreeNAS - Bug #74190: Add support for WS-DiscoveryClosed

History

#1 Updated by Dru Lavigne over 1 year ago

  • Assignee changed from Release Council to William Grzybowski

#2 Updated by William Grzybowski over 1 year ago

  • Assignee changed from William Grzybowski to Andrew Walker

#3 Updated by Bug Clerk over 1 year ago

  • Status changed from Unscreened to In Progress

#4 Updated by Andrew Walker over 1 year ago

I will implement this as follows:
There will be a new smb4.conf parameter "enable web service discovery". It defaults to "No". If set to "Yes", then we advertise using the python application. The application itself will be controlled via "samba_server". We'll basically treat it like it's a samba component.

root@FOOTEST:/usr/ports/net/samba49 # service samba_server status
smbd is running as pid 29617.
winbindd is running as pid 29623.
wsdd running is running as pid 29630.

Master PR: https://github.com/freenas/ports/pull/226

#5 Updated by Bug Clerk over 1 year ago

  • Status changed from In Progress to Ready for Testing

#6 Updated by Bug Clerk over 1 year ago

  • Target version changed from Backlog to 11.3

#7 Updated by Bug Clerk over 1 year ago

  • Copied to Bug #74190: Add support for WS-Discovery added

#8 Updated by Dru Lavigne over 1 year ago

  • Status changed from Ready for Testing to Done
  • Target version changed from 11.3 to Master - FreeNAS Nightlies
  • Needs QA changed from Yes to No
  • Needs Doc changed from Yes to No
  • Needs Merging changed from Yes to No

#10 Updated by William Grzybowski over 1 year ago

  • Has duplicate Feature #75505: Add WSDD to the build + GUI, to replace SMB1 which is highly unsafe+withdrawn, but is also relied on for Windows Neighbourhood to discover FreeNAS CIFS shares added

Also available in: Atom PDF