similar to: What is needed to allow Network Browsing of the file server in Windows

On 28/09/2020 12:36, Rowland penny via samba wrote: > > On 28/09/2020 12:01, Nick Howitt via samba wrote: >> 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? > No you are not missing a trick, Network Browsing requires SMBv1. Windows > now

On 9/27/19 10:39 AM, Rowland penny via samba wrote: > On 27/09/2019 16:19, Christopher Cox via samba wrote: >> 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

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

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

On 28/09/2020 14:52, Nick Howitt via samba wrote: > > > On 28/09/2020 12:36, Rowland penny via samba wrote: >> >> On 28/09/2020 12:01, Nick Howitt via samba wrote: >>> 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?

> 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

On 9/27/19 1:11 PM, Rowland penny 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

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 =

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

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

On 4/1/23 16: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

On 10/14/19 12:00 PM, Roy Eastwood via samba wrote: >> -----Original Message----- >> From: samba [mailto:samba-bounces at lists.samba.org] On Behalf Of Gerard Seibert via samba >> Sent: 14 October 2019 17:09 >> To: samba at lists.samba.org >> Cc: Gerard Seibert >> Subject: Re: [Samba] Detect version of smb being employed >> >> On Mon, 14 Oct 2019

> 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?

On 01/04/2023 23:10, David C. Rankin via samba wrote: > On 4/1/23 16: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

Current Version: samba 4.18.1 All, I have several **standalone** servers on a subnet, and for quite some time, I have received log messages in other standalone machines about multiple responses from the WINS server. There is only a single WINS server on the network (as it has been since samba 2.02 or earlier). The WINS server is 192.168.6.14. The log message that is received for example

I messed up on my reply yesterday. On 17/07/2020 21:05, Rowland penny via samba wrote: > > On 17/07/2020 19:57, Nick Howitt via samba wrote: >> Hi, >> I have a ClearOS 7.8 system which is running >> samba-4.10.4-11.el7_8.x86_64, and it upgraded to this just over a >> week ago (probably not relevant). A couple of days ago all the group >> shares failed. I

Hi, I would like to have nmbd only bind to the interfaces specified in the interfaces line of smb.conf, in the same way that smbd does. When researching this I did come across a mailing list thread saying there was no use case, but I think I have one. For many years ClearOS has been providing NT4 style domains and unix-style shares. M$ upset the applecart last year with their 1803 update

A reasonable alternative is to run Christgau's excellent Web Service Discovery host daemon (wsdd) on the samba server and make sure the Function Discovery Provider Host and Function Discovery Resource Publication services are running on the Windows 10 machines. Get wsdd from here: https://github.com/christgau/wsdd.git You can then stop and disable the nmbd on the samba machines as it's

On Mon, Jul 13, 2020 at 2:03 AM Rowland penny via samba < samba at lists.samba.org> wrote: > On 13/07/2020 04:29, Michael Jones via samba wrote: > > I'm trying to diagnose why my windows 10 clients can't do network > browsing. > > The network neighborhood doesn't show any of my machines running samba. > > > > Any advice? > > > Sorry, but it

On 27/09/2019 19:18, Christopher Cox via samba wrote: > On 9/27/19 1:11 PM, Rowland penny 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"