similar to: W10 workstations not connecting to Samba 4.10.5 member

On 27/06/2019 14:53, Marco Gaiarin via samba wrote: > 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

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

Hai Christian, > Can someone reproduce this? No, tried, but sorry, works fine for me on my 4.11.6 server. And what is you try it like this. samba-tool dns add dc1.zone1.domain.de 0.168.192.in-addr.arpa 157 PTR zone1.domain.de -U Administrator samba-tool dns add dc1.zone1.domain.de 1.168.192.in-addr.arpa 157 PTR zone2.domain.de -U Administrator I tested on my production where i have 6

On Mon, Apr 03, 2017 at 07:44:45PM +0300, Pavel Butsykin wrote: > This patch fixes the problem of the first boot after installation virtio block > drivers on Windows 10 / Server 2016. The problem is related to the change in > the behavior of Windows-Kernel-Pnp. To fix we need to add a field "Version" to > HKLM/SYSTEM/DriverDatabase/DriverPackages/drv_inf_label then

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

Hi Marco, the fact that win 10 fails where access from win 7 succeeds makes me wonder whether it is because of tightened security of windows 10, in particular I suspect disabled smb 1. Thus you should probably not try to make windows 10 succeed the same way but look at your security issue. Lowering the security might actually open an attack vector in your provisioning process. Best Regards,

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 =

On 03/04/16 21:39, Achim Klausmann wrote: > 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

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 Mon, 15 May 2017 13:25:03 +0200 "Stefan G. Weichinger via samba" <samba at lists.samba.org> wrote: > > As you may remember I went through a classic-upgrade a few months ago. > > I have a second domain to migrate and I am again/still scared to > attack that ;-) > > As I prepare my test VM and try to remember all those details the > customer has

On Mon, 15 May 2017 14:11:54 +0200 "Stefan G. Weichinger via samba" <samba at lists.samba.org> wrote: > Am 2017-05-15 um 14:06 schrieb Rowland Penny via samba: > > > Windows doesn't support joining Windows 7 to an NT4-style domain, so > > they definitely won't support windows 10. > > Well, I joined Win7 to NT4-domain back then ... (reg-hack, but

On Fri, 13 Apr 2018 22:31:23 -0700 ToddAndMargo via samba <samba at lists.samba.org> wrote: > Hi All, > > Fedora 276, x64 > > I just put a Widows Nein, oops Windows Ten computer on > a samba based network. > > Problem: the W-Nein computer can not see any of the other > shares. You can manually write in the path and it works fine. > The workgroup name is the

Mandi! Rowland penny via samba In chel di` si favelave... > Try it with '%U' instead of '%u', it seems to be using the service name > instead of the username. OK, good hint but... for test users we have created by hand the profiles folders, so surely the script is not the culprit... Anyway, thanks. -- dott. Marco Gaiarin GNUPG Key ID: 240A3D66

On 28/08/2019 17:14, Marco Gaiarin via samba wrote: > [ 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

Hi All, Fedora 276, x64 $ rpm -qa samba\* samba-winbind-clients-4.7.6-0.fc27.x86_64 samba-common-libs-4.7.6-0.fc27.x86_64 samba-client-4.7.6-0.fc27.x86_64 samba-common-tools-4.7.6-0.fc27.x86_64 samba-libs-4.7.6-0.fc27.x86_64 samba-common-4.7.6-0.fc27.noarch samba-4.7.6-0.fc27.x86_64 samba-client-libs-4.7.6-0.fc27.x86_64 samba-winbind-4.7.6-0.fc27.x86_64 samba-dc-libs-4.7.6-0.fc27.x86_64

Hello Rowland thanks for your answer. Am 03.04.2016 um 23:07 schrieb Rowland penny: > Probably the same reason that has been popping up recently, win10 will > not connect to a NT style domain (yes I know you aren't running a > domain) unless you set 'max protocol = NT1' in smb.conf and restart Samba. I will try that. Although the 'max protocol =' is not mentioned in

Am 2017-05-15 um 14:06 schrieb Rowland Penny via samba: > Windows doesn't support joining Windows 7 to an NT4-style domain, so > they definitely won't support windows 10. Well, I joined Win7 to NT4-domain back then ... (reg-hack, but anyway) > You may find a way around this lack of Microsoft support, you may also > find that a subsequent Windows update stops it working

.. Retry, oliver knows .. Have you seen: https://4sysops.com/archives/new-gpo-settings-in-windows-10-1903-enforce-updates-storage-sense-and-logon/ https://www.bleepingcomputer.com/news/microsoft/windows-10-version-1903-drops-password-expiration-policies/ https://www.windowscentral.com/whats-new-sign-experience-windows-10-may-2019-update Hmm, and the more i see the more i dislike.. :-/

On 04/14/2018 01:04 AM, Rowland Penny via samba wrote: > On Fri, 13 Apr 2018 22:31:23 -0700 > ToddAndMargo via samba <samba at lists.samba.org> wrote: > >> Hi All, >> >> Fedora 276, x64 >> >> I just put a Widows Nein, oops Windows Ten computer on >> a samba based network. >> >> Problem: the W-Nein computer can not see any of the other

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