similar to: Samba 3.2 and Windows 10

Displaying 20 results from an estimated 400 matches similar to: "Samba 3.2 and Windows 10"

2020 Aug 26
4
Win10 and NT mode: netlogon script seems does not run anymore.
[ Rowland, i know, i need to upgrade. ;-) ] Some month ago, with a relative big bunch of fix&tweaks, i was able to put a Win10 1903 client in join to a 'NT mode' Samba domain. Now i'm trying to do the same with a 1909 version; all seems to work as before, BUT netlogon script (defined in smb.conf with: logon script = startup.bat ) simply seems does not run. No log event in
2016 Apr 14
2
samba 3 domain and win10 logon scripts
On 13/04/16 21:32, Marc Muehlfeld wrote: > Hello, > > Am 13.04.2016 um 13:20 schrieb lejeczek: >> I have a win10 which is (from what I see) a good member of samba domain >> except for one thing - it does not seem to a few simply things from a >> logon.bat, or does not do anything with it. >> would you share your thoughts? > We can't, if you don't share
2016 Mar 31
5
Windows 10
Hello We have a problem with our Windows 10 Clients. Installed on a SLES12 Server is samba v4.4 I can bind the clients to the domain without any problem. Afterwards I want to login in the domain, I get the error, no logonserver available I can change in the smb conf max protocol to NT1 -> now it is possible to login with user xxx in the domain We don't want to use our samba server
2015 Aug 10
2
Samba Windows 10
Hi Guys, I am trying to connect Windows 10 to Samba domain controller. Windows 10 fails to get GPO’s because it can’t access SysVol with permissions. The domain Windows 10 is going through for SysVol would be \\example.com\SysVol when I navigate to this as Admin it does not let me go with credentials however if I use the servers hostname \\voyager\Sysvol I can access the directory. We have a
2016 Jul 21
3
Win10 to Samba as NT- PDC needs 3 settings
Upgrading Win7-32 (connected to Samba as NT-PDC) to Win10 requires - disable HardenedUncPaths (MutualAuth & Integrity) - install NTVDM - enable LegacyConsole otherwise the logon-script in Netlogon does not run, even if samba.cnf contains "server max level = NT1" Is Samba as NT-PDC supposed to handle HardenedUncPaths? Did I miss that I should have enabled that somehow in smb.conf?
2018 May 29
4
Can't join Windows 10 to classic domain
I've been running Samba 4 in NT4 Domain mode for a few years, and it's been working fine with Windows 7 PCs. I now need to join a new Windows 10 PC to the domain, but I'm not having any success! When I try to join the domain, the Windows 10 PC says "An Active Directory Domain Controller could not be contacted...." I've tried a few things, including:- Setting
2018 May 30
2
Can't join Windows 10 to classic domain
The issue does not seem to be connected to SMB1. It can be installed and it still won't authenticate. Something has been changed to force authentication to AD/DNS either solely or as a first step. The translation of the netbios name never happens even if the computer can resolve the name. Given that the authentication thru netbios resolution seems to get grandfathered in provided the domain
2015 Jul 12
7
Strange issue with share access on domain controllers
Hi list, I've a strange issue with Windows 7 (also occurs on 8.1) when accessing shares on domain controllers. If I use IP address or in-domain FQDN (server.domain.name), all is right. If I use another DNS entry pointing to the same IP, share access fails with following message (translated from french) : \\somehost.somsuffix\someshare is not accessible. […] Invalid parameter Issue
2020 Aug 27
0
Win10 and NT mode: netlogon script seems does not run anymore.
Hai, Thanks for that link, that is very usefull. Only after reading it i see its missing a very important part. This opens a security leak. See link ( dated in : Last Updated: Apr 15, 2015 ) https://support.microsoft.com/en-us/help/3000483/ms15-011-vulnerability-in-group-policy-could-allow-remote-code-executi The examples shown there. \\<Server>\<Share> - Needs to be
2015 Jul 09
2
Windows 10 in Samba 3 domain: netlogon share access denied
any messages in the windows 10 event logs, that could give some extra insight. according to https://social.technet.microsoft.com/Forums/en-US/7f5207cc-b202-47fc-bbb8-9ebe46a31961/network-logon-script-failure?forum=WinPreview2014General >\\foo.lan\netlogon should work. but, https://adsecurity.org/?p=1405 has some good info about the latest patch about hardening GPO. (which imo wil be
2016 Apr 18
0
samba 3 domain and win10 logon scripts
Am 14.04.2016 um 11:33 schrieb lejeczek: > I'm guessing I'm missing some specifics needed for win10 - what are > those I wonder. Is your Samba a NT4-style PDC? You are using Samba 3, I'm using Samba 4. Anyway: In my experiments I also had to set an additional regpatch for Win10 and a Samba 4.3.x NT4-style domain for logon scripts - otherwise the logon scripts are not
2015 Jun 17
5
Windows 10 in Samba 3 domain: netlogon share access denied
I just joined a Windows 10 (build 10130) to our Samba 3 domain. It seems to work. I can login, a home directory is created on the server, and I can access shares. All shares are OK, except "netlogon". Logon scripts don't run, and I cannot open the netlogon share. I get "Access denied" and a prompt to enter my username and password, which keeps coming back. At the
2016 Feb 05
4
Samba 3.2 and Windows 10
Il 05/02/16 14:41, Helmut Hullen ha scritto: >> is: if a client is upgraded to Windows 10, will it still work with >> that old Samba version? > > May be - Samba 3.6 does the job. Hi, you mean that 3.2 will not talk to Windows 10, no way? Unfortunately the latest Samba version for Debian Lenny is 3.2.15 AFAIK. -- 01
2017 Apr 21
4
Domain DFS on new share
Since past the beta-times of samba 4 (and it worked in former times!!) it never worked like this: \\yourdomain\share or \\yourdomain \dfs-share. The only thing working along witch your domain is: \\yourdomain\netlogon. I had another thread open on this case some times ago. Greetings Daniel EDV Daniel Müller Leitung EDV Tropenklinik Paul-Lechler-Krankenhaus Paul-Lechler-Str. 24 72076 Tübingen
2015 Aug 10
0
Samba Windows 10
try these settings for your GPO. Solution: GPEDIT.MSC -> Computer -> Administrative templates -> Network -> Networkprovider -> Hardened UNC Paths Added \\foo.lan\netlogon and Value: RequireMutualAuthentication=0,RequireIntegrity=0,RequirePrivacy=0 add \\foo\netlogon also Greetz, Louis >-----Oorspronkelijk bericht----- >Van: samba [mailto:samba-bounces at
2015 Jul 13
0
Strange issue with share access on domain controllers
Make sure you use the new GPO policies. Looks like the problem "[Samba] Windows 10 in Samba 3 domain: netlogon share access denied" Its not only for windows 10, also 7 and 8.x Solution: GPEDIT.MSC -> Computer -> Administrative templates -> Network -> Networkprovider -> Hardened UNC Paths Added \\foo.lan\netlogon and Value:
2018 May 30
0
Can't join Windows 10 to classic domain
Yes, you correct, you wasted time on this.. Read also, this will give more insight. https://support.microsoft.com/en-us/help/4034314/smbv1-is-not-installed-by-default-in-windows Greetz, Louis > -----Oorspronkelijk bericht----- > Van: samba [mailto:samba-bounces at lists.samba.org] Namens > Marco Shmerykowsky PE via samba > Verzonden: dinsdag 29 mei 2018 19:12 > Aan: samba
2020 Jan 09
2
smbclient can access sysvol Windows clients cannot
Hi everyone, I have two domains with a two way trust (DomA and DomB). When users from DomA (on a DomB Linux PC) access sysvol on DomB's DC using smbclient everything works: # smbclient //DomB /sysvol -Udoma\\user -c 'ls' -k . D 0 Thu Jan 9 13:53:03 2020 .. D 0 Thu Jan 9 14:28:29 2020 domb
2014 Jan 09
5
Re: Best practice for custom iptables rules
Il 08/01/14 16:17, Laine Stump ha scritto: > On 01/08/2014 01:43 PM, ZeroUno wrote: >> Also, regarding the "iptables restart problem" described in the last >> paragraph at <http://libvirt.org/firewall.html>, is there really no >> acceptable way to make libvirt add its rules back automatically upon >> iptables/network restart? > > Take a look at
2015 Oct 07
0
gpo failure
He.. im working also... ;-)   3 phone calls.. main boss in my office mous died... , answering you e-mail and installing windows pc. Working on support tickets... pff.. to much... at once..   And you cant access the server on DC3 at all with   \\dc3.domain.tld\sysvol   Or only \\dc3.domain.tld   Then check you share rights.   And/or apply ( but should not be needed if you use