search for: cobra

I just upgraded one of my DCs ununtu 20.04 -> 22.04 and samba 4.18 -> 4.19, but the Dc is not yet working again. systemctl status samba-ad-dc shows: Dec 05 12:48:39 cobra samba[749]: [2023/12/05 12:48:39.562920, 0] ../../source4/samba/service_task.c:36(task_server_terminate) Dec 05 12:48:39 cobra samba[749]: task_server_terminate: task_server_terminate: [winbindd child process exited] Dec 05 12:48:39 cobra systemd[1]: Started Samba AD Daemon. Dec 05 12:48:39 c...

05.12.2023 17:21, Joachim Lindenberg via samba: > I just upgraded one of my DCs ununtu 20.04 -> 22.04 and samba 4.18 -> 4.19, but the Dc is not yet working again. > > systemctl status samba-ad-dc shows: > > Dec 05 12:48:39 cobra samba[749]: [2023/12/05 12:48:39.562920, 0] ../../source4/samba/service_task.c:36(task_server_terminate) > Dec 05 12:48:39 cobra samba[749]: task_server_terminate: task_server_terminate: [winbindd child process exited] > Dec 05 12:48:39 cobra systemd[1]: Started Samba AD Daemon. > Dec 0...

...ec 2023 at 15:45 +0100, Joachim Lindenberg via samba <samba at lists.samba.org>, wrote: > I just upgraded one of my DCs ununtu 20.04 -> 22.04 and samba 4.18 -> 4.19, but the Dc is not yet working again. > > systemctl status samba-ad-dc shows: > > > > Dec 05 12:48:39 cobra samba[749]: [2023/12/05 12:48:39.562920, 0] ../../source4/samba/service_task.c:36(task_server_terminate) > > Dec 05 12:48:39 cobra samba[749]: task_server_terminate: task_server_terminate: [winbindd child process exited] > > Dec 05 12:48:39 cobra systemd[1]: Started Samba AD Daemon. &gt...

In installed a new DC (Samba 4.12.8 on Ubuntu 20.4) and initially everything appeared to work smoothly. Now I experience issues: DCDIAG /s:cobra.samba.lindenberg.one Directory Server Diagnosis Performing initial setup: [cobra.samba.lindenberg.one] LDAP bind failed with error 1326, The user name or password is incorrect.. With the other DC (still samba 4.11.14 on Ubuntu 18.4) many test succeed, but replication is obviousl...

...NT domain. The following is how I went about the exercise: 1. On the NT domain, I added the SAMBA domain A/C in the TRUSTING DOMAINS list, providing a certain password. 2. On the SAMBA domain, I executed the following command feeding the same password given in step 1, but without success: [root@cobra root]# net rpc trustdom establish asnt01 Password: Could not connect to server ASNT1 [2004/11/03 17:43:37, 0] rpc_parse/parse_prs.c:prs_mem_get(530) prs_mem_get: reading data of size 4 would overrun buffer. [2004/11/03 17:43:37, 0] utils/net_rpc.c:rpc_trustdom_establish(3035) WksQueryInfo call...

...w did you upgrade ? If I remember correctly, both 20.04 and 22.04 come with 4.15.13 (latest Samba version available), so could it be that the upgrade from 20.04 to 22.04 managed to install unrequired packages ? > > systemctl status samba-ad-dc shows: > > > > Dec 05 12:48:39 cobra samba[749]: [2023/12/05 12:48:39.562920, 0] > ../../source4/samba/service_task.c:36(task_server_terminate) > > Dec 05 12:48:39 cobra samba[749]: task_server_terminate: > task_server_terminate: [winbindd child process exited] > > Dec 05 12:48:39 cobra systemd[1]: Started Samba...

Please see replies inline: On 22/10/2020 19:06, Joachim Lindenberg wrote: > root at cobra:/home/joachim# cat /tmp/samba-debug-info.txt > Collected config --- 2020-10-22-17:57 ----------- > > Hostname: cobra > DNS Domain: > FQDN: cobra > ipaddress: 192.168.177.19 I actually expected more output, but lets start with what we have :-) You do not seem to have a domain na...

On 22/10/2020 19:49, Joachim Lindenberg wrote: > Password for Administrator at SAMBA.LINDENBERG.ONE: > > Failed to bind to uuid 50abc2a4-574d-40b3-9d66-ee4fd5fba076 for ncacn_ip_tcp:192.168.177.19[49153,sign,target_hostname=cobra.samba.lindenberg.one,abstract_syntax=50abc2a4-574d-40b3-9d66-ee4fd5fba076/0x00000005,localaddress=192.168.177.19] NT_STATUS_LOGON_FAILURE > ERROR: Connecting to DNS RPC server cobra.samba.lindenberg.one failed with (3221225581, 'The attempted logon is invalid. This is either due to a bad use...

...by a shell script). Later on I figured out that I can also define that zone in AD, and maintain internal names easy with the RSAT DNS tool, and also removed the zone file. Now I also installed a new DC, but used the internal backend. The issue now is, that they resolve differently: joachim at cobra:/etc/bind$ dig backup.lindenberg.one @cobra ; <<>> DiG 9.11.3-1ubuntu1.8-Ubuntu <<>> backup.lindenberg.one @cobra ;; global options: +cmd ;; Got answer: ;; ->>HEADER<<- opcode: QUERY, status: NOERROR, id: 24127 ;; flags: qr rd ra; QUERY: 1, ANSWER: 3, AUT...

I figured it out myself. The kerberos configuration on the old dc cobra was bad ? no clue why it worked at all until yesterday. After fixing it, testing with kinit, and restarting the dc processes it resumed replication. Joachim Von: Joachim Lindenberg <samba at lindenberg.one> Gesendet: Friday, 19 July 2019 16:54 An: samba at lists.samba.org Betreff: rep...

...ific appliction type. Support for XA transactions which would allow your tables to be spread over multiple databases and solve this. Apart from that is seems any one database vendor can be choosen for its particular features and approprietness for an install size/needs. In the past we have used COBRA and Borlands MIDAS to connect our applications to the database. I know some people are touchy about saying Rails is not Enterprise ready ;) Its only version 1, you wouldn''t expect it to be. Is is likly Rails will develop in these areas? Being at only version 1 there are a number of wa...

...one. succeeded, but we failed to find a matching DNS entry for A samba.lindenberg.one 192.168.177.69 need update: A samba.lindenberg.one 192.168.177.69 Looking for DNS entry SRV _ldap._tcp.samba.lindenberg.one python.samba.lindenberg.one 389 as _ldap._tcp.samba.lindenberg.one. Checking 0 100 389 cobra.samba.lindenberg.one. against SRV _ldap._tcp.samba.lindenberg.one python.samba.lindenberg.one 389 Checking 0 100 389 boa.samba.lindenberg.one. against SRV _ldap._tcp.samba.lindenberg.one python.samba.lindenberg.one 389 Lookup of _ldap._tcp.samba.lindenberg.one. succeeded, but we failed to find a...

...; that I can also define that zone in AD, and maintain internal > names easy with the RSAT DNS tool, and also removed the zone file. > > Now I also installed a new DC, but used the internal backend. > The issue now is, that they resolve differently: > > > > joachim at cobra:/etc/bind$ dig backup.lindenberg.one @cobra > > > > ; <<>> DiG 9.11.3-1ubuntu1.8-Ubuntu <<>> backup.lindenberg.one @cobra > > ;; global options: +cmd > > ;; Got answer: > > ;; ->>HEADER<<- opcode: QUERY, status: NOERROR, id: 2...

...S entry for A samba.lindenberg.one 192.168.177.69 >> >> need update: A samba.lindenberg.one 192.168.177.69 >> >> Looking for DNS entry SRV _ldap._tcp.samba.lindenberg.one python.samba.lindenberg.one 389 as _ldap._tcp.samba.lindenberg.one. >> >> Checking 0 100 389 cobra.samba.lindenberg.one. against SRV _ldap._tcp.samba.lindenberg.one python.samba.lindenberg.one 389 >> >> Checking 0 100 389 boa.samba.lindenberg.one. against SRV _ldap._tcp.samba.lindenberg.one python.samba.lindenberg.one 389 >> >> Lookup of _ldap._tcp.samba.lindenberg.one. s...

Until yesterday replication between my two DCs (boa and cobra) was running fine. Now I am observing one direction boa->cobra being stuck. I noticed this with a missing update of a DNS entry, but samba-tool drs showrepl confirms? Output of cobra shows plenty entries like the following (including just he first of each type): ==== INBOUND NEIGHBORS =...

...SSH tunnel client running on Win32. I was wondering if OpenSSH had a portable library component that I could leverage to manage the connection and tunneling functionality without any interface components...? Thanks in advance for any help or direction you can provide! ========== Robert Bates Cobra Powersports * http://www.cobrasales.com rob at cobrasales.com * 713-866-6262 x109

I set up a new windows machine and joined it to my existing domain (two Samba DCs). Now it turns out there is a computer in AD, but the associated DNS A/AAAA records of the new machine are missing. I already tried to leave and rejoin, but that didn?t fix the issue. Due to the long ACL I don?t really like the idea of creating the records manually. How can I fix or diagnose that situation?

Hello guys. Continuing Zhuchenko Valery question,I would like to know if someone from the list has deployed a child domain in samba 4. I have a samba 4 domain controller running on gentoo.My goal is to set up a domain and authentication domain only. But I need a root domain forest and a child domain.I am using verion 4.2.11I would like to know if someone has accomplished this either using dcpromo

Sure. Here they are: root at cobra:/var/log/samba# cat /etc/apt/sources.list # See http://help.ubuntu.com/community/UpgradeNotes for how to upgrade to # newer versions of the distribution. deb http://de.archive.ubuntu.com/ubuntu focal main restricted # deb-src http://de.archive.ubuntu.com/ubuntu focal main restricted ## Major bug f...

Hi, I have a system running FC2 with SAMBA-3.0.10-1.fc2 installed on it. I tried de-installing it, but it failed as follows: [root@cobra /]# rpm -e samba error: Failed dependencies: samba is needed by (installed) system-config-samba-1.2.22-0.fc2.1 samba = 0:3.0.10 is needed by (installed) samba-swat-3.0.10-1.fc2 Can anyone suggest how I could go about de-installing the kit? Also, how would I install and use SAMBA...