Lorenzo Milesi
2020-May-09 09:34 UTC
[Samba] New install of 4.12.1: fileserver not visible when browsing network
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 = s3fs, rpc, nbt, wrepl, ldap, cldap, kdc, drepl, winbindd, ntp_signd, kcc, dnsupdate workgroup = WDC netbios aliases = server idmap_ldb:use rfc2307 = yes #?https://wiki.samba.org/index.php/Configuring_Winbindd_on_a_Samba_AD_DC # template shell = /bin/bash template homedir = /home/%U [sysvol] path = /usr/local/samba/var/locks/sysvol read only = No [netlogon] path = /usr/local/samba/var/locks/sysvol/wdc.mydomain.it/scripts read only = No [1] https://wiki.samba.org/index.php/Samba4/ActiveDirectory#Browsing_.28Domain_Master_Browser.29 [2] https://wiki.samba.org/index.php/FAQ#Why_Is_the_Network_Neighbourhood_empty_or_Does_Not_Show_All_Machines_in_the_Domain.3F -- Lorenzo Milesi - lorenzo.milesi at yetopen.it YetOpen S.r.l. - https://www.yetopen.it/ Via Salerno 18 - 23900 Lecco - ITALY - Tel +39 0341 220 205 - Fax +39 178 6070 222 Think green - Non stampare questa e-mail se non necessario / Don't print this email unless necessary -------- D.Lgs. 196/2003 e GDPR 679/2016 -------- Tutte le informazioni contenute in questo messaggio sono riservate ed a uso esclusivo del destinatario. Tutte le informazioni ivi contenute, compresi eventuali allegati, sono da ritenere confidenziali e riservate secondo i termini del vigente D.Lgs. 196/2003 in materia di privacy e del Regolamento europeo 679/2016 - GDPR - e quindi ne e' proibita l'utilizzazione ulteriore non autorizzata. Nel caso in cui questo messaggio Le fosse pervenuto per errore, La invitiamo ad eliminarlo senza copiarlo, stamparlo, a non inoltrarlo a terzi e ad avvertirci non appena possibile. Grazie. Confidentiality notice: this email message including any attachment is for the sole use of the intended recipient and may contain confidential and privileged information; pursuant to Legislative Decree 196/2003 and the European General Data Protection Regulation 679/2016 - GDPR - any unauthorized review, use, disclosure or distribution is prohibited. If you are not the intended recepient please delete this message without copying, printing or forwarding it to others, and alert us as soon as possible. Thank you.
Rowland penny
2020-May-09 10:44 UTC
[Samba] New install of 4.12.1: fileserver not visible when browsing network
On 09/05/2020 10:34, Lorenzo Milesi via samba wrote:> 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 = s3fs, rpc, nbt, wrepl, ldap, cldap, kdc, drepl, winbindd, ntp_signd, kcc, dnsupdate > workgroup = WDC > netbios aliases = server > idmap_ldb:use rfc2307 = yes > #?https://wiki.samba.org/index.php/Configuring_Winbindd_on_a_Samba_AD_DC > # template shell = /bin/bash > template homedir = /home/%U > > [sysvol] > path = /usr/local/samba/var/locks/sysvol > read only = No > > [netlogon] > path = /usr/local/samba/var/locks/sysvol/wdc.mydomain.it/scripts > read only = No > > > [1] https://wiki.samba.org/index.php/Samba4/ActiveDirectory#Browsing_.28Domain_Master_Browser.29 > [2] https://wiki.samba.org/index.php/FAQ#Why_Is_the_Network_Neighbourhood_empty_or_Does_Not_Show_All_Machines_in_the_Domain.3FNo, it isn'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
Andrew Bartlett
2020-May-09 19:51 UTC
[Samba] New install of 4.12.1: fileserver not visible when browsing network
Correct, Network browsing is not supported on the AD DC. On Sat, 2020-05-09 at 11:34 +0200, Lorenzo Milesi via samba wrote:> 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?> [1] https://wiki.samba.org/index.php/Samba4/ActiveDirectory#Browsing_.28Domain_Master_Browser.29 > [2] https://wiki.samba.org/index.php/FAQ#Why_Is_the_Network_Neighbourhood_empty_or_Does_Not_Show_All_Machines_in_the_Domain.3F-- Andrew Bartlett http://samba.org/~abartlet/ Authentication Developer, Samba Team http://samba.org Samba Developer, Catalyst IT http://catalyst.net.nz/services/samba
Alex MacCuish
2020-May-09 20:58 UTC
[Samba] New install of 4.12.1: fileserver not visible when browsing network
For Mac and Linux, use avahi. For windows, use https://github.com/christgau/wsdd. On 09/05/2020 20:51, Andrew Bartlett via samba wrote:> Correct, Network browsing is not supported on the AD DC. > > On Sat, 2020-05-09 at 11:34 +0200, Lorenzo Milesi via samba wrote: >> 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? >> [1] https://wiki.samba.org/index.php/Samba4/ActiveDirectory#Browsing_.28Domain_Master_Browser.29 >> [2] https://wiki.samba.org/index.php/FAQ#Why_Is_the_Network_Neighbourhood_empty_or_Does_Not_Show_All_Machines_in_the_Domain.3F
Lorenzo Milesi
2020-May-09 21:22 UTC
[Samba] New install of 4.12.1: fileserver not visible when browsing network
> 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.Thank you, it worked (of course) -- Lorenzo Milesi - lorenzo.milesi at yetopen.it YetOpen S.r.l. - https://www.yetopen.it/ Via Salerno 18 - 23900 Lecco - ITALY - Tel +39 0341 220 205 - Fax +39 178 6070 222 Think green - Non stampare questa e-mail se non necessario / Don't print this email unless necessary -------- D.Lgs. 196/2003 e GDPR 679/2016 -------- Tutte le informazioni contenute in questo messaggio sono riservate ed a uso esclusivo del destinatario. Tutte le informazioni ivi contenute, compresi eventuali allegati, sono da ritenere confidenziali e riservate secondo i termini del vigente D.Lgs. 196/2003 in materia di privacy e del Regolamento europeo 679/2016 - GDPR - e quindi ne e' proibita l'utilizzazione ulteriore non autorizzata. Nel caso in cui questo messaggio Le fosse pervenuto per errore, La invitiamo ad eliminarlo senza copiarlo, stamparlo, a non inoltrarlo a terzi e ad avvertirci non appena possibile. Grazie. Confidentiality notice: this email message including any attachment is for the sole use of the intended recipient and may contain confidential and privileged information; pursuant to Legislative Decree 196/2003 and the European General Data Protection Regulation 679/2016 - GDPR - any unauthorized review, use, disclosure or distribution is prohibited. If you are not the intended recepient please delete this message without copying, printing or forwarding it to others, and alert us as soon as possible. Thank you.
Maybe Matching Threads
- Error changing server IP address: ERROR: Connecting to DNS RPC server
- Intermittent permission denied when accessing share
- Unable to "rejoin" existing DC after upgrade (infamous WERR_FILE_NOT_FOUND)
- Intermittent permission denied when accessing share
- Intermittent permission denied when accessing share