search for: wsdd

On 9/27/19 12:48 PM, Rowland penny via samba wrote: > On 27/09/2019 18:33, Christopher Cox via samba wrote: >> >> I understand the "Function Discovery" side and wsdd (which is fine for >> local same network discovery somewhat similar to Network >> Neighborhood). I'm saying that even without that if I browse to just a >> computer in Windows Explorer, I get to see the shares that I have >> access to.? I'd like that sort of feat...

...enny via samba wrote: > On 27/09/2019 18:57, Christopher Cox via samba wrote: >> On 9/27/19 12:48 PM, Rowland penny via samba wrote: >>> On 27/09/2019 18:33, Christopher Cox via samba wrote: >>>> >>>> I understand the "Function Discovery" side and wsdd (which is fine >>>> for local same network discovery somewhat similar to Network >>>> Neighborhood). I'm saying that even without that if I browse to just >>>> a computer in Windows Explorer, I get to see the shares that I have >>>> access to....

> Active Directory was created to replace netbios If you see 2008r2, 2012 and even 2016 and 2019 acted as AD DC but I think you saw it, it is (NetBios) still at a place here, despite on AD DC mode. As far as I know there are many small/medium LANs where NetBios features such as neighborhood, folders, printers sharing using NetBios names resolving and others are still used. In my opinion It

...ble without explicitly specifying the >> share name that are available for a host?? And of course, is there >> anyway that "protocol" could be handled somehow in smbclient? >> >> >> > For Windows clients, see here: > > https://github.com/christgau/wsdd I understand the "Function Discovery" side and wsdd (which is fine for local same network discovery somewhat similar to Network Neighborhood). I'm saying that even without that if I browse to just a computer in Windows Explorer, I get to see the shares that I have access to. I...

...:25, Rowland Penny via samba wrote: > As far as 1 is concerned, not really sure, but as far as 2 is concerned, well > the answer is probably no, you really need SMBv1 for WINS and smbv1 is now > turned off by default everywhere. You will probably be better using Avahi for > Linux and wsdd for Windows. > Thank you Rowland! That's really the question -- I DON'T need smb1. So in that case do I just disable all the Wins and Browse List stuff? Do I even need nmb at that point? (or will it help with the Avahi and wsdd resolution?) Basically, I have a network with 4 Linux...

...ny via samba wrote: >> As far as 1 is concerned, not really sure, but as far as 2 is >> concerned, well the answer is probably no, you really need SMBv1 for >> WINS and smbv1 is now turned off by default everywhere. You will >> probably be better using Avahi for Linux and wsdd for Windows. >> > > Thank you Rowland! > > That's really the question -- I DON'T need smb1. So in that case do I > just disable all the Wins and Browse List stuff? Do I even need nmb at > that point? (or will it help with the Avahi and wsdd resolution?) Add '...

...r show >> automatically in Win 10's "Network" unless I manually enter the URL or >> share name. Is that correct? > > Windows now use the Function Discovery Provider Host and Function Discovery Resource Publication Services to find hosts on the network. You can add wsdd to the samba server to provide the Web Service Discovery service. See here: https://github.com/christgau/wsdd.git . Works very well. While wsdd works well, it too has to be enabled on the Windows 10 side AFAIK (or it just for serving?). Anyway, just weird that Microsoft created "an alter...

On 27/09/2019 18:57, Christopher Cox via samba wrote: > On 9/27/19 12:48 PM, Rowland penny via samba wrote: >> On 27/09/2019 18:33, Christopher Cox via samba wrote: >>> >>> I understand the "Function Discovery" side and wsdd (which is fine >>> for local same network discovery somewhat similar to Network >>> Neighborhood). I'm saying that even without that if I browse to just >>> a computer in Windows Explorer, I get to see the shares that I have >>> access to.? I'd like t...

...: >> On 27/09/2019 18:57, Christopher Cox via samba wrote: >>> On 9/27/19 12:48 PM, Rowland penny via samba wrote: >>>> On 27/09/2019 18:33, Christopher Cox via samba wrote: >>>>> >>>>> I understand the "Function Discovery" side and wsdd (which is fine >>>>> for local same network discovery somewhat similar to Network >>>>> Neighborhood). I'm saying that even without that if I browse to >>>>> just a computer in Windows Explorer, I get to see the shares that >>>>> I...

On Mon, 14 Oct 2019 13:47:34 +0100, Rowland penny via samba stated: >On 14/10/2019 13:27, Gerard Seibert via samba wrote: >> FreeBSD 12 >> Samba 4.8.12 >> >> Samba is not showing up on my Win 10 PRO machine. I can access the >> shares if I use the machines hostname or IP, though. How can I >> determine what version of ?smb? is being used? I have set ?client

...Windows Explorer. I do not use SMB1. Am I missing a trick or >> is it not possible without SMB1? > No you are not missing a trick, Network Browsing requires SMBv1. Windows > now uses Network Discovery instead, you should be able to use this > instead: https://github.com/christgau/wsdd >> >> I am using ClearOS7 with the Centos7 4.10.4 samba package. > > Samba is starting to remove everything to do with SMBv1, 4.13.0 (just > released) has deprecated a few of the parameters required for a PDC, so > can I suggest you upgrade to Samba AD as soon as possible...

I've just deployed an AD DC fileserver with Samba4 but the server itself is not available when browsing network computers from a Windows PC. Is it because of this [1][2] or did I misconfigure it? Thanks my config: # Global parameters [global] netbios name = FILESERVER realm = WDC.MYDOMAIN.IT server role = active directory domain controller server services =

...n't because of something you have done, or not done, it is because, from 4.11.0, smb.conf now has these by default: client min protocol = SMB2_02 server min protocol = SMB2_02 This means that your DC will not use SMBv1 and this is required (at both ends) for network browsing, try installing wsdd, this will make the DC visible to Network Discovery. See here for wsdd: https://github.com/christgau/wsdd Rowland

With the removal of SMB1 (by default) and everywhere (e.g. Windows), I noticed that when I open up a computer (\\computer-name) I can see the shares that I have access to... that is, from a Windows Explorer (in my case Win10).? Is there any way to get something like this working using smbclient without SMB1? All this is without (AFAIK) enabling the Function Discovery stuff.? How does Windows

My Samba4 computers (DC's & member server) are not shown within W10 File Explorer Network. Only the other workstations appear. I believe this is due to smb1 being depreciated. All the folder redirection still works, gpo, etc. Domain users can log in. What do I need to adjust so these machines appear in smb2? (I know this has been talked about before sorry.) -- Thank you. Bob Wooden

I am using Samba as a simple file server but I cannot browse its shares in Windows Explorer. I do not use SMB1. Am I missing a trick or is it not possible without SMB1? I am using ClearOS7 with the Centos7 4.10.4 samba package. My cut down configs (with most of the shares removed) are: [root at server ~]# testparm -s Load smb config files from /etc/samba/smb.conf NOTE: Service homes is

...a shares will never show > automatically in Win 10's "Network" unless I manually enter the URL or > share name. Is that correct? Windows now use the Function Discovery Provider Host and Function Discovery Resource Publication Services to find hosts on the network. You can add wsdd to the samba server to provide the Web Service Discovery service. See here: https://github.com/christgau/wsdd.git . Works very well. HTH, Roy

> Windows now uses Network Discovery instead of Network Browsing, if you > run this on all your Samba machines: > > https://github.com/christgau/wsdd > > Your Samba machines will appear in Explorer on Windows, your Linux > machines should use Avahi to get something similar. > > Rowland > Is this something that will be included in Samba in the future?

> ... and if you need network/share browsing Roland pointed me to a great > utility, wsdd (https://github.com/christgau/wsdd), which is also > packaged by various distros. Thanks for all. It' s almost exactly what I looked for, at least, to remain working "compurers/devices list" . I re-set all possible servers/clients to using the new technology. I built without Debia...

...rnative for clients to register? > > DNS with dynamic registration? Something else? > > Thank you. Wins requires SMBv1, which, as you probably know, isn't very secure, so it is now turned off by default, but it is still there. You can use Avahi/Bonjour for Linux/Mac clients and wsdd for Windows clients. Rowland