search for: allowinsecureguestauth

Displaying 6 results from an estimated 6 matches for "allowinsecureguestauth".

2015 Dec 15
2
Samba 4.0.21 and Windows 10
...t build) and my Samba PDC (under Fedora). All machines with Windows 7 can join domain successfully. But with Windows 10, I've got "network path not found" error. I've changed all registry keys that we need to change, but no way (DomainCompatibilityMode, DNSNameResolutionRequired, AllowInsecureGuestAuth) My PDC is in NT4 style domain mode. No Active Directory. I've searched with Wireshark any trace of a problem, and I could see that Windows 10 send some LDAP requests to my PDC when I try to join it in the domain. As if he wanted to connect to a PDC with an AD. I don't want upgrade my PDC...
2018 Oct 13
2
Windows Server 2019 / Windows 10 LTSC can't access samba shares on Debian stable 4.5.12
...-10-server-2016 https://getadmx.com/?Category=Windows_10_2016&Policy=Microsoft.Policies.LanmanWorkstation::Pol_EnableInsecureGuestLogons The following command resolved my issue: Set-ItemProperty -Path "HKLM:\SYSTEM\CurrentControlSet\Services\LanmanWorkstation\Parameters" -Name "AllowInsecureGuestAuth" -Type DWord -Value 1 Afterwards it works. Also with the Debian Samba. Cheers, Thomas
2015 Dec 15
0
Samba 4.0.21 and Windows 10
...; (under Fedora). > All machines with Windows 7 can join domain successfully. But with Windows > 10, I've got "network path not found" error. > I've changed all registry keys that we need to change, but no way > (DomainCompatibilityMode, > DNSNameResolutionRequired, AllowInsecureGuestAuth) > > My PDC is in NT4 style domain mode. No Active Directory. I've searched > with > Wireshark any trace of a problem, and I could see that Windows 10 send > some > LDAP requests to my PDC when I try to join it in the domain. As if he > wanted > to connect to a PDC with...
2017 Jun 30
0
Accessing a guest share from Windows 10 gives System error 5 on some computers
...orrelation regarding that. I tcpdumped both types of sessions, and these show that the Windows Client forcefully closes the TCP connection (NT_STATUS_CONNECTION_RESET) right after receiving `NTLMSSP_CHALLENGE` before a working client would send `NTLMSSP_AUTH` with a user. I have checked setting `AllowInsecureGuestAuth` in the geristry without any effect. Help! Best regards Kai -- Kai Ruhnau Software Manager T:+49 202 769302 19 Target Systemelektronik GmbH & Co. KG Heinz-Fangman-Straße 4 42287 Wuppertal Amtsgericht Wuppertal HRA 23898 Persönlich haftende Gesellschafterin Target Systemelektronik Beteiligun...
2018 Oct 13
0
Windows Server 2019 / Windows 10 LTSC can't access samba shares on Debian stable 4.5.12
...x.com/?Category=Windows_10_2016&Policy=Microsoft.Policies.LanmanWorkstation::Pol_EnableInsecureGuestLogons > > The following command resolved my issue: > > Set-ItemProperty -Path > "HKLM:\SYSTEM\CurrentControlSet\Services\LanmanWorkstation\Parameters" > -Name "AllowInsecureGuestAuth" -Type DWord -Value 1 > > Afterwards it works. Also with the Debian Samba. Yes, that is correct, Windows now as 'guest' turned off by default. Rowland
2018 Oct 13
2
Windows Server 2019 / Windows 10 LTSC can't access samba shares on Debian stable 4.5.12
Hello everyone, when using samba 4.9.1 as a standalone filer, I need to start smbd and nmbd, don't I? I'm using: /local/samba/sbin/smbd -s /local/samba-config/common/smb.conf /local/samba/sbin/nmbd -s /local/samba-config/common/smb.conf However smbd. Seems to ignore my lock directory: (infra) [/local/samba-config/common] grep gencache_notrans.tdb log/smbd Opening cache file at