search for: opaperjam

On 17/03/15 10:13, Sense Zeng wrote: > And use ntlm_auth fail too: > > ntlm_auth --username=testuser > password: > NT_STATUS_LOGON_FAILURE: Logon failure (0xc000006d) > > > 2015-03-17 7:30 GMT+00:00 Sense Zeng <opaperjam at gmail.com>: > >> My AD server is Win2003. And my linux server is ubuntu. Samba version is >> 2:3.6.3-2ubuntu2.12 and 2:4.1.6+dfsg-1ubuntu2.14.04.7. They are join into >> the Win2003 AD as normal smb servers (not DC). >> >> After Win2003 DC autoupdate last week...

My AD server is Win2003. And my linux server is ubuntu. Samba version is 2:3.6.3-2ubuntu2.12 and 2:4.1.6+dfsg-1ubuntu2.14.04.7. They are join into the Win2003 AD as normal smb servers (not DC). After Win2003 DC autoupdate last week, I can't use smbclient access all samba server with NTLMv2: ~$ smbclient //172.16.3.13/share -U testuser Enter DOMAIN\testuser's password: session setup

And use ntlm_auth fail too: ntlm_auth --username=testuser password: NT_STATUS_LOGON_FAILURE: Logon failure (0xc000006d) 2015-03-17 7:30 GMT+00:00 Sense Zeng <opaperjam at gmail.com>: > My AD server is Win2003. And my linux server is ubuntu. Samba version is > 2:3.6.3-2ubuntu2.12 and 2:4.1.6+dfsg-1ubuntu2.14.04.7. They are join into > the Win2003 AD as normal smb servers (not DC). > > After Win2003 DC autoupdate last week, I can't use smbcli...

I had a AD with 4 Win2003 DC. Now I use a samba4 server as a additional DC. Samba4 server system version: ubuntu 15.04 Samba version: samba 4.3.0 The replication from win2003 DC to samba4 DC was success. But have some problem from samba4 DC to win2003 DC. I can run samba-tool drs showrepl without error. But in log.samba it can found many message like: [2015/10/09 12:53:11.562088, 0]

I'm testing a samba4 server join AD (had 1 win2003 dc) as dc. Version: Samba4 DC: samba 4.1.1 with ubuntu (172.16.3.8) Win2003 DC: Win2003 SP2 (172.16.3.3) AD domain name: dotest.com The samba server had joined to AD as DC. When win2003 dc online, it seems works fine. When I test win2003 dc online, simulate the win2003 DC was failue, found the samba4 DC can't work fine along. The AD

I just upgrade samba 3.6 to samba 4.3, folow the ubuntu 12.04 upgrade to 14.04. And I found out Samba 4 removed "force security mode" and "force directory security" from smb.conf. I don't understand why remove them, because I think they are irreplaceable. I need to keep some permission of the file or directory in the samba share and make sure them can't change by anyone

Thanks for reply. But I think "force security mode" and "force directory security" are very very helpful. It's not necessary to remove them. Maybe just a warning to the users remain that these parameters cost the acl problem, they should use them carefully.

I'm new for samba4 and I'm trying to test samba4(Version 4.0.8) with internal dns. Did internal dns can config? Could I just manual add some host(A) in?

I'm testing the samba4 with bind. Samba: 4.0.9 Bind: 9.9.3-P2 I configured with the document http://wiki.samba.org/index.php/Dns-backend_bind and seems dns update completed. I trying to find out where is the DLZ zone file. Is there? Or it's just the ldb file?

My AD is using win2003 DC now. Domain functional level and Forest functional level are 2003. I try to use the samba4 server replace the win2003 server. User account: 6044 Group: 111 Computer account: about 1000 I tried use a computer (system: ubuntu 13.10) with 1G ram to join domain as DC (samba-tool domain join ... DC ...) and 1G ram gone fast. Samba-tool domain join did not success. How many

I had a AD with 4 Win2003 DC. Now I use a samba4 server as a additional DC. Samba4 server system version: ubuntu 15.04 Samba version: samba 4.3.0 The replication from win2003 DC to samba4 DC was success. But have some problem from samba4 DC to win2003 DC. I can run "samba-tool drs showrepl" without error. But in log.samba it can found many message like: [2015/10/09 12:53:11.562088, 0]