similar to: Browsing shares of a server

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

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

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

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

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

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 =

> 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

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

I've got a Samba DC installation that doesn't show a browse list to any clients on the network, which means point-and-click navigation of the network doesn't work. File sharing works just fine, as does joining computers to the domain, login authentication, etc. It's just the ability to browse lists of other machines on the network that doesn't work: clients see nothing.

El 27/9/19 a les 17:19, Christopher Cox via samba ha escrit: > 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?

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

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

I just noticed that smbclient from Samba 4.9.4 /built by myself) on FreeBSD 11.2 coredumps when called like this: smbclient -L <hostname> > % /liu/pkg/samba/4.9.4-liu/bin/smbclient -L filur00 > Enter username at AD.LIU.SE's password: > Abort (core dumped) … if it is linked against /usr/local/lib/libmd5.so (which is part of “libwww”). If I remove libmd5.so and recompile

On 20/06/16 19:53, Dale Schroeder wrote: > On 06/17/2016 4:31 PM, peter lawrie wrote: >> Hi all >> About 18 months ago I connected 14 new Windows 7 PCs to a Centos5.1 >> server >> with samba3x as domain members. There are no other servers on site. >> Today, I had to visit to connect up a PC in a new location. As I would >> normally do I checked for Centos

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

Le 25/10/2018 à 18:22, Giulio via samba a écrit : >> Is enabling SMBv1 on the Windows 10 side the only solution to get Linux share be visible for the Windows "Network" listing? > > Yes, it's the only way to see the samba computer in the computers' list. > > When using SMB>=2, network discovery will use a different protocol > (WSD/LLMNR) which samba