similar to: NT style domain users on Win10 cannot connect WIFI

On 15/08/2019 13:02, lejeczek via samba wrote: > hi guys, > > I realize it's not necessarily Samba type of a question but since this > community here is vast with lots of win experience I thought I'd poke - > same one winstation(ver. 1903) and computer's domain users when logged > in can connect WIFI no problems, only Samba domain users cannot (to the > same

hi everybody 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? many thanks L.

hi guys, I had a user (as I understand root should/must not be used for that) which is in "domain admins" group(ldapsam backend) which now(it worked for many years) with win10 fails, at Win10 end's: "The join operation was not successful. This could be because and existing computer account having name 'win7' was previously created using a different set of

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

Not only NT domains, but also Samba 3.6! Wow! I'm a retro-sysadmin! ;-) I know i'm asking a rather hard thinks but... we are upgrading, but also solving some troubles. We have ''decently'' integrated some W10 1803 in a NT domain, but now with some other 1903 there's no way to make roaming profiles work. Looking at samba logs, seems that the client don't try at

[ 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

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?

On 09/10/2019 11:27, Rowland penny via samba wrote: > On 09/10/2019 10:56, lejeczek via samba wrote: >> friendly advice: read the subjects carefully as you do with the body of >> the messages > Even friendlier advice, ask the question in the post ;-) neutral remark - everybody has, including myself, but gee man... you have some issues... to solve. cheers, L. >>> list

On 09/10/2019 09:35, Rowland penny via samba wrote: > On 09/10/2019 09:14, lejeczek via samba wrote: >> hi guys, >> >> what would be an absolute minimum on the list of sevices one should have >> for NT style domain? (userdb in separate LDAP, dns too is in bind9) >> >> And maybe even less need for stand-alone server? >> >> many thanks, L. >>

hi guys, what would be an absolute minimum on the list of sevices one should have for NT style domain? (userdb in separate LDAP, dns too is in bind9) And maybe even less need for stand-alone server? many thanks, L.

On 09/10/2019 10:08, Rowland penny via samba wrote: > On 09/10/2019 09:47, lejeczek via samba wrote: >> On 09/10/2019 09:35, Rowland penny via samba wrote: >>> On 09/10/2019 09:14, lejeczek via samba wrote: >>>> hi guys, >>>> >>>> what would be an absolute minimum on the list of sevices one should >>>> have >>>> for NT

hi everyone I realise this not exactly on topic, I'm hoping an expert or two could confirm that following is not caused somehow by samba: I try xfreerdp to connect to a Win10 which is a member of NT-style domain and it fails this way: [14:55:33:905] [8048:8055] [ERROR][com.freerdp.core.nla] - SPNEGO failed with NTSTATUS: 0xC0000017 [14:55:33:905] [8048:8055] [ERROR][com.freerdp.core] -

On 27/08/2020 08:49, L.P.H. van Belle via samba wrote: > https://support.microsoft.com/en-us/help/3181029/smb-file-server-share-access-is-unsuccessful-through-dns-cname-alias > @Rowland have a good look at this one. This one is hitting the list.. (i have seen this problem also). I think everyone knows my views on NT4-style domains, they were a good idea at the time, but that time is most

hi guys, I updated to qemu-kvm-common-ev-2.12.0-18.el7_6.1.1.x86_64 (also libvirt) and my Centos 6.10 kvm guests now do not start. Funnily enough Win10 guest are fine, only Centoses cannot start, silently & without any errors. Any care to comment? many thanks, L.

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

A not so technical friend in India is shopping for a laptop. He often travels and stays months in Malaysia and so needs to be able to use the laptop there as well. He typically connects to the internet via wifi, but sometimes must use a telephone line (yes, with a modem). And of course there will be times when he has to plug into mains power to recharge the battery. So to be able to fully use

Hi. Ok - I took a shortcut: I finally found a 4.6.5 deb package for Ubuntu: https://launchpad.net/~rewi/+archive/ubuntu/samba I know that this package is just as fresh as bread from the oven, and that the packager states "not for production". Anyway, it installs without make, make install and configure, and there is no issues with paths. Wonderful :-) I can even install a printer on

Given an existing NT4 Samba 4 DC, a recently upgraded Win10 machine can no longer access NETLOGON to authenticate to the network. This lead to the research revealing that my Samba4 PDC SMB.CONF must be changed to limit MAX PROTOCOL = NT1 to avoid negotiating a version of SMB2 from Win10 that Samba4 can't resolve. Doing this broke authentication via other resources that no longer support NT1,

Hello all, I recently bought a brand new Dell Precision 7540 laptop.? Before buying I checked the specifications from the RedHat hardware list and they said that it was "fully RedHat 8 Certified" and listed all the hardware that was "certified" to work with that laptop. https://access.redhat.com/ecosystem/hardware/3979771 I have had good results the last few years with

On Mon, Feb 08, 2016 at 04:50:09PM -0800, Joshua Pincus wrote: > Mr Jones, > > I recently came across your excellent 2010 blog entry, > https://rwmj.wordpress.com/2010/04/30/tip-install-a-device-driver-in-a-windows-vm/. > The blog entry was incredibly useful for Win7. I was wondering if you have > any similar insights for Win10? The CDDB is gone, and it's replacement, or