similar to: Samba4 computers not on W10 Network

Hai, There is some work done here, see: https://bugzilla.samba.org/show_bug.cgi?id=11473 Maybe an extra ping on it. Would be nice to have it in 4.11. since its directly related to/with SMB1. Greetz, Louis > -----Oorspronkelijk bericht----- > Van: samba [mailto:samba-bounces at lists.samba.org] Namens > Rowland penny via samba > Verzonden: woensdag 4 september 2019 15:48

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

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

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

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

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 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 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 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 asked abut that, here, but now seems a simpler things, so i retry... ] This seems NON a samba touble, but a different behaviour in M$ client OS. But, really, i've not clue how to find an answer... Suppose to have a Win7 and a Win10 machine, both NOT joined to a domain. Suppose to have a share, with guest access enabled, where only readonly access are needed. Suppose also

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

As subject say, we are trying to ''integrate'' some W10 machine on a NT domain, with samba as PDB/BDC, OpenLDAP backend. profile share is defined as: [profiles] comment = Network Profiles Share path = /srv/samba/profiles read only = No create mask = 0600 directory mask = 0700 store dos attributes = Yes browseable = No csc policy = disable root preexec =

Hello, i got some clients (WINDOWS7 and WINDOWS10) to connect to samba shares. OS is openSUSE 12.2; 13.1; 42.1 Samba-Version: 3.6.7; 4.1.22; 4.2.4 smb.conf is shown below. The samba setup is a workgroup setup, the W7-clients are set up to the workgroup 'workgroup'. No further changes are made to the W7-clients. samba setup: groupadd workgroup chgrp -R workgroup /srv/samba chmod -R 770

[see also my thread started here https://social.technet.microsoft.com/Forums/en-US/b653e756-f966-4f8f-9d13-f19a88d4cc5e/w10-pro-1903-and-samba-with-roaming-profiles-quotwe-cant-sign-in-to-your-accountquot?forum=win10itprogeneral] Hello, since the upgrade from W10 pro 1809 to 1903 roaming users can still logon, but they are 'greeted' with the message: "We can't sign in to your

Mandi! Rowland penny via samba In chel di` si favelave... > Are you also aware the the Guest user is turned off on Windows 10 by default? Aware yes, but i supposed was related to guest access TO the client, not guest access OF the client to server share... But, i'll give it a try. Thanks. -- dott. Marco Gaiarin GNUPG Key ID: 240A3D66 Associazione ``La Nostra

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

This topic may have been discussed many times, sorry to repeat here. I have been trying various combinations of adding test users via ADUC. The first three (3) added fine. Then the strange began. Many, many W10 client re-starts throughout these process to make client capture any changes from servers. In one case, create the user, give him/her a password. Login from W10 client. Logout of W10