> Active Directory was created to replace netbiosIf 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 would be better to offer to admins/users alternative - who wants they uses v2 and not uses NetBios, who wants they return to v1 and uses NetBios that they could make a decision on their own And this will be fully identical functioning as Windows DCs behaviour. As for compatibility also. Cp Service SPb...
Just my 2cts: you should definitely turn off NetBios name resolution where possible and rely on DNS and SMB3 (disable older versions). Otherwise you are calling out for security and privacy issues. And I really appreciate that Samba wants to get rid of that legacy - thanks for that! Best Regards, Joachim -----Urspr?ngliche Nachricht----- Von: samba <samba-bounces at lists.samba.org> Im Auftrag von CpServiceSPb via samba Gesendet: Friday, 23 October 2020 12:10 An: samba at lists.samba.org Betreff: Re: [Samba] NetBios at AD DC mode ?> Active Directory was created to replace netbiosIf 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 would be better to offer to admins/users alternative - who wants they uses v2 and not uses NetBios, who wants they return to v1 and uses NetBios that they could make a decision on their own And this will be fully identical functioning as Windows DCs behaviour. As for compatibility also. Cp Service SPb... -- To unsubscribe from this list go to the following URL and read the instructions: https://lists.samba.org/mailman/options/samba
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 sharing using NetBios names > resolving and others are still used. > > In my opinion It would be better to offer to admins/users alternative - who > wants they uses v2 and not uses NetBios, who wants they return to v1 and > uses NetBios that they could make a decision on their own > And this will be fully identical functioning as Windows DCs behaviour. > As for compatibility also. > > Cp Service SPb...The latest versions of Windows have SMBv1 turned off by default, but can be turned on again, but this is not recommended. To use netbios, you need SMBv1, Samba is working towards removing SMBv1 and, like Windows, has turned it off by default, but it can be turned on again, this is not recommended. Eventually, SMBv1 will be removed from Samba, whether this is before or after Windows removes it, is up to Windows, but it will be removed by both. If you are still using netbios, can I suggest you make plans to stop using it, before you are forced to. Rowland
On 23/10/2020 11:32, Rowland penny via samba wrote:> > 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 sharing using NetBios names >> resolving and others are still used. >> >> In my opinion It would be better to offer to admins/users alternative >> - who >> wants they uses v2 and not uses NetBios, who wants they return to v1 and >> uses NetBios that they could make a decision on their own >> And this will be fully identical functioning as Windows DCs behaviour. >> As for compatibility also. >> >> Cp Service SPb... > > The latest versions of Windows have SMBv1 turned off by default, but can > be turned on again, but this is not recommended. To use netbios, you > need SMBv1, Samba is working towards removing SMBv1 and, like Windows, > has turned it off by default, but it can be turned on again, this is not > recommended. > > Eventually, SMBv1 will be removed from Samba, whether this is before or > after Windows removes it, is up to Windows, but it will be removed by both. > > If you are still using netbios, can I suggest you make plans to stop > using it, before you are forced to. > > Rowland >... 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.
> ... 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 of wsdd2 from C-code daemon (not python one) and started it successfully. And all seems working well except a one fly in the ointment. Namely, Windows 2016 is disappeared from ITS OWN neighborhood after Refresh menu item pressing. All clients are still remained here. And it appears again either after pressing "Refresh" menu item after some time from first pressing. But such "way" works time to time only, not always. Or Windows 2016 server is appeared again in ITS OWN list almost always just after restarting service "Function Discovery Resource Publication" . Windows 7 and Windows 2008R2 were tested as well and there was not noticed such situation with these OSes. But at the same time my Ubuntu machines (2 servers) are appeared at all Windows lists correctly always.
On 27/10/2020 15:43, CpServiceSPb via samba wrote:> >> ... 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 of wsdd2 from C-code daemon (not python > one) and started it successfully. > And all seems working well except a one fly in the ointment. > > Namely, Windows 2016 is disappeared from ITS OWN neighborhood after > Refresh menu item pressing. > All clients are still remained here. > And it appears again either after pressing "Refresh" menu item after > some time from first pressing. > But such "way" works time to time only, not always. > Or Windows 2016 server is appeared again in ITS OWN list almost always > just after restarting service "Function Discovery Resource > Publication" . > Windows 7 and Windows 2008R2 were tested as well and there was not > noticed such situation with these OSes. > > But at the same time my Ubuntu machines (2 servers) are appeared at > all Windows lists correctly always. >I don't know about wsdd2, but wsdd appears to have limitations with some network types (vpn and docker were mentioned). I think your best source of information is from the wsdd or wsdd2 site.
> I don't know about wsdd2, but wsdd appears to have limitations with some > network types (vpn and docker were mentioned). I think your best source > of information is from the wsdd or wsdd2 site.There is https://github.com/Andy2244/wsdd2 wsdd2. At the time it's simple network of C class. ??, 27 ???. 2020 ?. ? 18:43, CpServiceSPb <cpservicespb at gmail.com>:> > ... 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 of wsdd2 from C-code daemon (not python one) and started it successfully. > And all seems working well except a one fly in the ointment. > > Namely, Windows 2016 is disappeared from ITS OWN neighborhood after Refresh menu item pressing. > All clients are still remained here. > And it appears again either after pressing "Refresh" menu item after some time from first pressing. > But such "way" works time to time only, not always. > Or Windows 2016 server is appeared again in ITS OWN list almost always just after restarting service "Function Discovery Resource Publication" . > Windows 7 and Windows 2008R2 were tested as well and there was not noticed such situation with these OSes. > > But at the same time my Ubuntu machines (2 servers) are appeared at all Windows lists correctly always. > >