similar to: Fwd: Samba AD DC not working properly within Docker [NT_STATUS_INTERNAL_ERROR]

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

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 all, I have found this: time smbclient -L //debian -U% Sharename Type Comment --------- ---- ------- print$ Disk Printer Drivers software Disk IPC$ IPC IPC Service (Samba 4.7.7-Debian) HP_F4100 Printer HP Deskjet F4100 series MX870-series Printer Canon MX870 series l6p Printer l6p MX435

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

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

Hi, I've changed /etc/resolv.conf, rebooted, here is the output: cat /etc/resolv.conf domain rona.loc search rona.loc nameserver 192.168.19.2 ------ smbclient -L $(hostname -f) -UAdministrator%<password> -d5 INFO: Current debug levels: all: 5 tdb: 5 printdrivers: 5 lanman: 5 smb: 5 rpc_parse: 5 rpc_srv: 5 rpc_cli: 5 passdb: 5 sam: 5 auth: 5 winbind: 5 vfs: 5

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)

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

Hi, thank you for your answer. Yesterday I solved the problem. It turned out that getent passwd and getent group gave entries only from flat files. It related to nsswitch.conf and libnss-ldap. Former was ok, but later was different on the two servers. On the PDC, there was libnss-ldapd, but on the BDC there was libnss-ldap installed. According to the Debian Wiki, libnss-ldapd is simpler, and

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. I'm hoping for some advise/help. I have a domain that won't seem to go online: $ wbinfo --online-status BUILTIN : active connection MY-HOST : active connection FOO : no active connection The log for the domain repeats over and over again: [2019/05/30 09:34:10.259173, 3, pid=1606, effective(0, 0), real(0, 0), class=auth] ../../auth/ntlmssp/ntlmssp_sign.c:514(ntlmssp_sign_reset)

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.

Try this. Check the enabled Guest account, go to Devices and Printers in Control Panel, right click on the network shared default printer and select Printer properties. Next select the Security tab on the Printer Properties page, and you should see Everyone in the list of users. Check the permissions for Everyone. At minimum, Print should be checked in the Allow check box. The print

I have a Windows 7 workstation with physically connected printer and Linux laptop (Linux Mint 19). They are connected to each other via router with internet cord plugged in. I managed to establish file exchange between them: create a shared resource on one computer, then access it from another. But the same trick with printer just do not work: as soon as I try to access it via network from

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 1/11/2018 10:39 AM, Harsh Kukreja via samba wrote: > Hi > > The DRS sync between two Domain Controllers connected on one network is > failing. I have enabled the log level 9. > > samba-tool drs replicate 172.16.10.5 iumsvrpdc DC=iumnet,DC=edu,DC=na > --full-sync -UAdministrator > INFO: Current debug levels: > all: 9 > tdb: 9 > printdrivers: 9 >

Hello, We have a customer that is using Samba version 4.7.12 and Windows 10 clients. When they initiate connections, they are very slow to authenticate (several minutes). It does not readily appear there are network connectivity issues. Of possible note, the following log sequence is, repeatedly, observed within the Samba debug logs: [2023/07/06 11:14:15.676774, 3, pid=2118992, effective(0,

On 1/11/2018 1:57 PM, Harsh Kukreja wrote: > Hi > > I have tried  using FQDN for DC1 and DC2 but still it is > failing.Please assist to fix > > samba-tool drs replicate iumdcdp01.iumnet.edu.na > <http://iumdcdp01.iumnet.edu.na> iumsvrpdc DC=iumnet,DC=edu,DC=na > --sync-forced -UAdministrator > INFO: Current debug levels: >   all: 9 >   tdb: 9 >  

With the ubuntu security updates on Monday that broke everything, I downgraded my 12.04 3.6x samba packages on my NT4 DC - now my windows 7 domain members can join and function OK and am looking into a 14.04 client that was a member and cannot now join, and the downgrade also failed. So I got 4.4.2 source and built on the system and have tried to join, but it fails. Below is some debug

Hi James Thanks for your response. hots -t A iumsvrpdc (use it's fqdn as well) I have verified it with the FQDN which says that the record iumsvrpdc.iumnet.edu.na exists Search for 'iumsvrpdc' objectGUID ldbsearch -H /usr/local/samba/private/sam.ldb '(invocationId=*)' --cross-ncs objectguid : it shows 2 records found # record 1 dn: CN=NTDS