search for: esyst

Hi, After enable display information about previous logons on the default domain policy, no one can logon the samba4 domain. How can I disable it by ldap modify or just reset to the default domain policy (if we are unlucky) ? -- Dongsheng

Hello, Am 03.05.2015 um 17:38 schrieb ????????? ????????: > Thank you for your time. What network did you test it? > 100Mb or 1000Mb? I'm using 1Gbit here at home. With a 100Mbit connection it wouldn't be possible to reach transfer rates of 110MB/Sec. A realistic good transfer rate for a 100Mbit connection is just around 11 MB/Sec. Regards, Marc

I set-up a basic AD DC using samba 4.1.9 successfully. I joined my NAS to the domain, i.e. I saw no errors and see the users and groups of my AD listed in the GUI of the NAS. When I try to connect to a share of the NAS the following happens: mgr at ws1:~$ smbclient -U 'AD\mgr' //nas/Test Enter AD\mgr's password: Domain=[AD] OS=[Unix] Server=[Samba 3.6.9] tree connect failed:

I'm on LinuxMint 17 Cinnamon desktop, Samba 4.2.1, and Windows 7 I can share folders fine, but when I unshare a folder, it remains visible and accessible to users. It should disappear and become inaccessible when unshared. Repro steps - sharing the folder: 1. Open up the Cinnamon file manager, navigate to Home folder. 2. Right click on Downloads, choose Sharing Options

Does anyone have a guess as to where I should be looking to fix this? I can run wbinfo -u wbinfo -g and all the names come up right. Kinit works and I get a Ker ticket.. This is an Ubuntu 14.04 with samba 4. THIS IS THE FIRST LINUX COMPUTER I HAVE EVER BUILT!!!!!!! I knew absolutely ZERO about linux last week so I don't even know how to explain the issue. What I want to do is

Not sure about the high CPU load, but you have the [netlogon] share twice in your smb.conf. Your first matches mine, have you added the second yourself? The second one looks weird with 2 path definitions. Cj Tibbetts schreef op do 18-12-2014 om 08:59 [-0700]: > New to linux and new to Samba so any direction in troubleshooting would be > helpful. Here is what I have so far. > > Within