similar to: NetBios at AD DC mode ?

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

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

> ... 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 Debian deb

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

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

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

On 23/10/2020 11:10, CpServiceSPb via samba wrote: >> 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

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

> 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 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 06/01/2023 14:09, Gilles via samba wrote: > Hello, > > I want to set up a stand-alone server > <https://wiki.samba.org/index.php/Setting_up_Samba_as_a_Standalone_Server> on a small LAN. > > I read that WINS should no longer be used: What's the current > alternative for clients to register? > > DNS with dynamic registration? Something else? > >

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

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

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

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. I've verified that all of my samba hosts are running nmbd! I've reached the end of my ability to debug this, so I could really use some help from the list to figure out why this isn't working. I've isolated the situation