similar to: samba 3 domain and win10 logon scripts

Hallo, Jeremy, Du meintest am 12.01.16: >>> Run under gdb please and type "bt" to get a backtrace when >>> it crashes. [...] >> [?1034h(gdb) run >> Starting program: /usr/bin/smbclient >> [Thread debugging using libthread_db enabled] >> Using host libthread_db library "/lib/libthread_db.so.1". >> >> Program received

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

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 WIFIs). Anybody? many thanks, L.

Hallo, Jeremy, Du meintest am 11.01.16: >> "smbclient" doesn't work with the slackware packages samba-4.3.1 and >> 4.3.2, it has worked with 4.2.1 and older versions. >> >> smbclient >> >> answers with "segmentation fault", on two testing machines (where >> 4.2.1 has worked well). [...] > Run under gdb please and

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] -

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.

Hallo, I''d like to get some explanations ... # btrfs filesystem show Label: ''MMedia'' uuid: 120b036a-883f-46aa-bd9a-cb6a1897c8d2 Total devices 3 FS bytes used 3.80TB devid 1 size 1.82TB used 1.29TB path /dev/sdg1 devid 3 size 1.81TB used 1.29TB path /dev/sdc1 devid 2 size 1.81TB used 1.28TB path /dev/sdb1 Btrfs Btrfs v0.19 # btrfs filesystem df /srv/MM

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

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,

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

Hi, When I upgraded from Fedora 22 to Fedora 25 my Win10 box lost the ability to connect to shares on the F25 box. The F25 box can still access shares on the Win10 box. F25 is currently running Samba 4.5.13 and I have a simple workgroup setup. Let's call the Win10 box 'fred' and the F25 box 'ethel'. When fred tries to access a share on ethel, I am prompted for username and

On 23.04.19 14:51, Rowland Penny via samba wrote: > On Tue, 23 Apr 2019 14:35:16 +0200 > basti via samba <samba at lists.samba.org> wrote: > >> Hello, >> I have a Win10 Client connected via openVPN to the company LAN. >> openVPN seem to work fine. I get Routes, the AD DNS server, can ping >> domain controller file Server etc. > > It looks like you

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

Hello, I have a Win10 Client connected via openVPN to the company LAN. openVPN seem to work fine. I get Routes, the AD DNS server, can ping domain controller file Server etc. Authendicaten on Fileserver fail (cant connect to domaincontroller) gpupdate fail with the same error. Firewall haas open all port list here: https://wiki.samba.org/index.php/Samba_AD_DC_Port_Usage I have try to debug with

Hi, I'm having a problem with significant clock skew on fedora29 with qemu-system-x86-3.0.0 and ibvirt-daemon-kvm-4.7.0. This is on my desktop and appears to happen between suspends of the host each night. It appears like the time just stops while the guest is suspended, of course, but then doesn't update once the guest is resumed. I'm pretty sure time is configured correctly on the

hi everyone I've had a Win 10 Pro client to a non-AD samba fine for a long time. Suddenly I could not logon new user(which had not logged in on that Win box before). I was lazy, I remember that quickest thing that worked once in the past was remove & re-add client, you know, in Windows itself, to the domain. Now I cannot login any user at all at that Win box(even though the box was

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 Tue, 16 Jun 2020, Rowland penny via samba wrote: > On 16/06/2020 12:41, Harald Hannelius via samba wrote: >> I have Samba AD-domain with two fileservers and two Samba DS-servers. Most >> people can authenticate OK, but one user always gets "wrong password". > What versions of Samba ? All servers are 4.9.5-Debian. >> Auth: [SMB2,(null)] user [SAD]\[username]

I cannot connect as guest from Win10 to Samba anymore, since I removed "server max protocol = NT1" net use \\%IP%\testshare /user:"" "" /persistent:no System error 58 has occurred. The specified server cannot perform the requested operation. It works when I supply a userid and password. It works from Win7. It fails only in the combination Win10, SMB3,