similar to: Win10 - can't create domain user

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

I have the issue that a PC running Win10pro in a Samba 3.6.25 (NT4) domain is not able to successfully connect to an Office365 account. With a local user the same account works, with the domain user: no I am not able to instantly upgrade to ADS and/or samba4 there, so I got to come up with a quick solution. Do the changes in the registry conflict here? I did: sc.exe config lanmanworkstation

Hello, i'm using Samba Version : 2:3.5.5~dfsg-1~bpo50+2 from backports Patch applied : http://support.microsoft.com/kb/2171571 Key modified : [HKEY_LOCAL_MACHINE\System\CurrentControlSet\Services\LanManWorkstation\Parameters] "DNSNameResolutionRequired"=dword:00000000 "DomainCompatibilityMode"=dword:00000001

Windows 7 Professional 32-bit HKEY_LOCAL_MACHINE\Software\Microsoft\Windows NT\CurrentVersion: 7600 Ubuntu-8.04.4 LTS samba-3.0.28a-1ubuntu4.13 I applied the Registry settings as documented at http://wiki.samba.org/index.php/Windows7 HKLM\System\CCS\Services\LanmanWorkstation\Parameters DWORD DomainCompatibilityMode = 1 DWORD DNSNameResolutionRequired = 0 Attempting

I've got myself in a bit of a pickle trying to install the latest Samba 3.6.20-31 package from SerNet on a Debian Wheezy server. The installed Debian version of Samba was 3.6.6. It's an off-line test server, and I'm still getting to grips with Debian, so no harm done, but I'd like to know the proper procedure to install this software! What I've done is: Edited

Dear all Is ist possible to join a windows7 pc to a samba 3.2.15 domain? I tried the registry hack: [HKEY_LOCAL_MACHINE\SYSTEM\CurrentControlSet\services\LanmanWorkstation\Para meters] "DomainCompatibilityMode"=dword:00000001 "DNSNameResolutionRequired"=dword:00000000 And I got succesfull joind to domain. But after a restart I could not login the domain: "the

Hi all Follow up to this post, as it didn't seem to go through the first time. We have a common problem occurring with our Samba setups. We run 3 (identical) processing environments that each contain a Samba host sharing approx .5TB of data to 6 Wintel machines. Normally these hosts operate fine, though we intermittently experience a Samba panic (intermittent = every 2-3 days) as per below.

Could you see if anything useful in the logs indicating why the ACL was not returned? Instructions are at: https://wiki.samba.org/index.php/LinuxCIFS_troubleshooting#Enabling_Debugging (it is easier for newer kernels due to dynamic tracing e.g. "trace-cmd record -e cifs" but even with these older kernels it should be enough information in the dmesg logs - if not a wireshark trace

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

I've got myself in a bit of a pickle trying to install the latest Samba 3.6.20-31 package from SerNet on a Debian Wheezy server. The installed Debian version of Samba was 3.6.6. It's an off-line test server, and I'm still getting to grips with Debian, so no harm done, but I'd like to know the proper procedure to install this software! What I've done is: Edited

On 06/12/14 18:17, Michael Tokarev wrote: > Hello. > > For may years we're running a classic (NT-style) domain with many > machines (mostly windows7 these days). Initially it was set up > using samba3, and now we upgraded samba to samba4 (4.1.11), without > introducing AD functionality (it is not needed). > > I especially asked in several places whenever samba4

Hey all,  I've been running a Win10 Pro (64bit) guest for some time now.... and originally it was pretty snappy and I had no complaints. Somewhere in about the last 3-6 months I've been noticing sluggish performance -- but not overall. The system is mostly remote so I do a lot of my admin via RDP or the local console with the KVM Manager. I recently did a complete fresh install 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

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

Hello Claus, I have an openSUSE with Samba 4.4.4-3.1-3676 as PDC. There is no AD running. We use roaming profiles. I upgraded 11 Machines to Windows 10 having lot's of trouble with the Startmenu and the Win10-Apps. I can confirm the logon-script isn't executed since the Windows-Upgrade. Nobody - even Microsoft - could ever answer my questions to have a working startmenu with Windows 10.

Hi Jeremy, Hi Steve, Hi Ronnie, thanks for your replies and the profound discussion. I think, it's best to demonstrate my problem case along an real world example: The following log of a console sesssion shows how I am doing the mounts on behalf Linux Kernel CIFS-FS Module on the client side against a Samba 4.5 file server (both running on Debian Stretch 9.8) via SMB/CIFS resp. SMB2 protocol:

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,

I have a Debian machine running Unstable acting as a samba server. The server was installed a few days ago after a reinstall of the OS. The older installation's samba configs were backed up and restored after installation. The Samba shares are accessible if I access them from a Windows 7 client. The shares, however, cannot be accessed from a Debian client (newly installed amd64 Testing).

Hello. For may years we're running a classic (NT-style) domain with many machines (mostly windows7 these days). Initially it was set up using samba3, and now we upgraded samba to samba4 (4.1.11), without introducing AD functionality (it is not needed). I especially asked in several places whenever samba4 supports NT-style domains, and got several positive answers. Now, we're trying to

I'm searching for the SRPM corresponding to this installed RPM. % yum list | grep gfs2 gfs2-kmod-debuginfo.x86_64 1.92-1.1.el5_2.2 It is missing from: http://msync.centos.org/centos-5/5/os/SRPMS/ What I need from the SRPM are the patches. I'm working through some issues using the source code, and the patches in the RedHat SRPM