search for: ntlmssp_negotiate_identifi

Hello everyone, does anybody know what the ntlmssp flag NTLMSSP_NEGOTIATE_IDENTIFY is used for? I looked in the samba sources and only found it in .idl but there as far as I can tell there is no implementation of that. I searched for some information on the web but did not really find something useful. Before anyone asks: Microsoft's HTML5 RDP Webclient uses that flag and insists that

On 15/10/2019 13:56, ASW Global via samba wrote: > I've read the documentation that domain trusts should be fully supported with both Kerberos and NTLM authentication. I've created a new 2016 domain on a Windows box and created a Samba domain on a Linux box with a BIND9_DLZ backend. Both servers can resolve both DNS domains forwards and backwards and I am able to connect a Windows 10

I am having problems implementing Samba using security=domain against a Windows 2008R2 server. I have been able to successfully join the domain via a net rpc join. Anytime I try to access a share through smbclient I get a NT_STATUS_TRUSTED_RELATIONSHIP_FAILURE but nothing in the logs (on either side) seems to be giving me any leads on where to look. The system is locked down to allow NTLv2

On 10.03.2015 20:20, Rowland Penny wrote: > > OK, the first will not work (well not yet), the second should, I > take it you ran 'kinit Administrator at AD.DILKEN.EU' as root before > the join ? > > You could try 'net ads join -U Administrator' and enter the > password when prompted, I personally have never seen the point in > using kerberos during the

I've read the documentation that domain trusts should be fully supported with both Kerberos and NTLM authentication. I've created a new 2016 domain on a Windows box and created a Samba domain on a Linux box with a BIND9_DLZ backend. Both servers can resolve both DNS domains forwards and backwards and I am able to connect a Windows 10 client to the Samba domain without any issues. The

Oh, I have a pair of samba-4.1.17-DC's, raspberry-pi and dc2 to which make the domain ad.dilken.eu on site Neuoetting. resolv.conf points to the two dc's: search ad.dilken.eu nameserver 192.168.2.33 nameserver 192.168.2.2 In the output I find some relations to dc2 resp. 192.168.2.2, but perhaps it doesn't work as expected.. Greetings Am 10.03.2015 um 21:23 schrieb Rowland Penny:

On 10/03/15 20:14, Roman Dilken wrote: > On 10.03.2015 20:20, Rowland Penny wrote: > >> OK, the first will not work (well not yet), the second should, I >> take it you ran 'kinit Administrator at AD.DILKEN.EU' as root before >> the join ? >> >> You could try 'net ads join -U Administrator' and enter the >> password when prompted, I

On 10/03/15 20:29, Roman Dilken wrote: > Oh, I have a pair of samba-4.1.17-DC's, raspberry-pi and dc2 to which make the domain ad.dilken.eu on site Neuoetting. > > resolv.conf points to the two dc's: > > search ad.dilken.eu > nameserver 192.168.2.33 > nameserver 192.168.2.2 > > In the output I find some relations to dc2 resp. 192.168.2.2, but perhaps it

Hi, I am running an Ubuntu 14.04 server with Samba 2:4.3.11+dfsg-0ubuntu0.14.04.14, which just provides storage services to the network. It is configured to use an existing Active Directory infrastructure based on Windows servers. Since some weeks I am experiencing issues with accessing the network shares served by Samba (no matter which client/operating system). Connection/mounting attempts

Hi, I upgraded our servers from Wheezy to Jessie. I use samba in classic mode, with openldap backend. After the upgrade, on the PDC (srv3) everything seems to be ok, it authetnicates, the netlogon share is accessible on it, but on the BDC (srv7), what is the file server, the authentication doesn't work, shares are inaccessible. I compared and syncronized the configuration files to as similar

Hi all I'm desperate now. On one of the sites I cannot connect Ubuntu to Windows AD 2003. Error below. On exactly the same setup but on a different network and also on VirtualBox VMs everything works as expected. Looks like something on the network then or mission parameter. Error is about KDC but I can successfully do kinit and get ticket. I can also successfully run: sudo net ads info

On 10.03.2015 19:25, Rowland Penny wrote: > > Hi, what are you trying to join to? > > Remove this line 'idmap_ldp:use rfc2307 = yes' > > one) it should be 'idmap_ldb:use rfc2307 = yes' two) it is only > used on a DC. > > How are you trying to do the join ? > > Rowland > > Hi, I commented it out but it didn't change the behaviour.

Hello! We have Samba v3 (3.5.10) working against an LDAP server, and need to upgrade to Samba v4 (4.7.1), RHEL 7 supports only v4. Tried multiple configs of the smb.conf (including the old config) without success. Cleaned up smb.conf is below. Also, included is the output of a smbclient command on the SMBServer with debug option 10. Hoping that someone can point me in the right direction. Thanks

On 17/04/15 12:29, ivenhov wrote: > Hi all > > I'm desperate now. > > On one of the sites I cannot connect Ubuntu to Windows AD 2003. > Error below. > On exactly the same setup but on a different network and also on VirtualBox > VMs everything works as expected. > Looks like something on the network then or mission parameter. > Error is about KDC but I can

On Tue, 2018-10-16 at 15:18 -0700, Emil Henry wrote: > Hi Andrew! > > I included it in one response, but may have not done a Reply All. Am resending it. > > Thanks. It is reading the hashes, so it looks like it is working. Dumb question, but are you really sure the password is right? Otherwise, it might be some very odd NTLMv2 thing. Try (on the client) 'client ntlmv2 auth

On Tue, 2018-10-16 at 20:20 -0700, Emil Henry wrote: > Hi Andrew! > > I am not 100% sure that the password is correct. I was told that it > was changed to the one I am testing. But, when I try the old > password, I get a different error message (NT_STATUS_INVALID_SID). I > will attached the output.  Then it is the old password, and you have other issues you need to sort out.

Hi Andrew! I am not 100% sure that the password is correct. I was told that it was changed to the one I am testing. But, when I try the old password, I get a different error message (NT_STATUS_INVALID_SID). I will attached the output. I added the 'ntlm auth = yes' to the smb.conf. How would I change the client? The version of Samba that we are running is 4.7.1, which is the latest

I can not see any ldap call, did you try to tcpdump for ldap packets? Michal út 16. 10. 2018 v 21:14 odesílatel Emil Henry via samba < samba at lists.samba.org> napsal: > Hello! > > We have Samba v3 (3.5.10) working against an LDAP server, and need to > upgrade to Samba v4 (4.7.1), RHEL 7 supports only v4. Tried multiple > configs of the smb.conf (including the old config)

I'm sorry for the very long debug pasted below but I'm afraid lower debug levels would not give enough useful information about the problem. I've been investigating it for over two weeks with no result. Maybe developers can tell me where to search for the cause - browsing source code is very hard... I have a Samba PDC with LDAP backend. Configuration works fine on 3.0.x version but

Hi Andrew! Really appreciate the clarification and help. Understood about the password. I have attached the log.127.0.0.1 with the "correct" password being used. I do see entries in that log for the Primary Group of 0. Not sure where I would need to make the change. Any guidance would be really appreciated. Have been fighting this for the last 3 weeks. :-( Thanks. On Tue, Oct 16, 2018