similar to: interdomain trust broken after upgrade to 4.1.17

On 25/03/16 14:15, Oliver Freyd wrote: > Hi samba folks, > > I'm running an NT$-style samba PDC and 2 BDCs. They are all on > samba 3.6.25 (the SERNET packages on debian wheezy) > > I have a domain trust with another server on another subnet, > I think they run samba 3.5, also NT4-style domain. > > Everything ran fine, they can login to our machines and vice versa,

Hello, I've upgraded a classic NT4 style BDC to samba 4.2.10 (and after that to 4.2.12, but no improvement...) It was running on 4.1.17 and wbinfo -u showed a list of our users, and users of the trusted domain. running on 4.2.12 it lists only our users. on a working server: wbinfo --domain=EXAMPLE -t checking the trust secret for domain EXAMPLE via RPC calls succeeded On 4.2.12:

On 25/04/15 14:02, Daniel Carrasco Mar?n wrote: > Sorry, I forgot to revert another test i did, but the result is the same: > > --------------------------------------------------------------------------------------------------------------------------------------- >

I am using Samba v4.0.16. Join to the domain controller with two NIC's, it will fail once every two times. Response from the DNS, will succeed in domain join in the case of reachable IP addresses. However, it seems to fail to join domain in the case of unreachable IP addresses. ( V3.5.15 succeed in both cases. ) Please help someone. attach debug log ========== Windows Server2008r2

On 25/04/15 13:27, Daniel Carrasco Mar?n wrote: > Hi, I'm sorry for my english. > > i've migrated an old 3.6 samba domain to Samba 4.1 and the windows part is > working fine (i can join and manage the server from a Windows Machine), but > when I try to join the domain from another linux server it fails. > > I've followed this guide to migrate: >

2015-04-25 15:17 GMT+02:00 Rowland Penny <rowlandpenny at googlemail.com>: > On 25/04/15 14:02, Daniel Carrasco Mar?n wrote: > >> Sorry, I forgot to revert another test i did, but the result is the same: >> >> >> --------------------------------------------------------------------------------------------------------------------------------------- >>

Sorry, I forgot to revert another test i did, but the result is the same: --------------------------------------------------------------------------------------------------------------------------------------- --------------------------------------------------------------------------------------------------------------------------------------- sudo net ads join -U "Administrator" -d 5

Hi, I'm sorry for my english. i've migrated an old 3.6 samba domain to Samba 4.1 and the windows part is working fine (i can join and manage the server from a Windows Machine), but when I try to join the domain from another linux server it fails. I've followed this guide to migrate: https://wiki.samba.org/index.php/Samba_Classic_Upgrade_%28NT4-style_domain_to_AD%29 and this for

Hi all, I get an error when I try to join domain from CentOS 6.5. Have you an idea ? /etc/samba/smb.conf : --------------------- [global] workgroup = XXX server string = Samba Server Version %v log file = /var/log/samba/log.%m max log size = 50 realm = XXX.YYY security = ads idmap uid = 10000-20000 idmap gid = 10000-20000

Hi, we have a winbind issue with Samba (Version 4.2.7-SerNet-RedHat-19.el6) on one of our servers. After a while (once a day) one of the winbind daemons causes a very high cpu load (100%). This load remains until we kill this process. This server is a member of a AD domain with several trusted domains. I think this happens because winbind has problems with one of the trusted domains (ALS2)

Getting the following error when trying to add to the domain the username and password are correct because they work on other machines. =~=~=~=~=~=~=~=~=~=~=~= PuTTY log 2015.04.16 09:50:06 =~=~=~=~=~=~=~=~=~=~=~= 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

Hi Due to putting a DVD in my Virtual Machine Host Computer which then filled the logs with errors and subsequently filled the drive crashing all vms. Luckily I had a backup of the DC image which I restored and some machines just worked and some can?t find KDC kinit: Cannot contact any KDC for realm 'BALEWAN.UNICORN.COM' while getting initial credentials I have tried leaving the domain

Hi all! I'm trying to join Debian Jessie to an existing AD domain as a member server (AD DC is Server 2012R2) to run it as a file server. I installed acl, samba, winbind, libnss-winbind, and krb5-user using APT, and configured /etc/samba/smb.conf according to the Samba wiki article. The error the join command is producing is " Failed to join domain: failed to join domain

On Fri, 10 May 2024 23:19:32 +1200 "Samba @ Pegasusnz via samba" <samba at lists.samba.org> wrote: > Hi > > Due to putting a DVD in my Virtual Machine Host Computer which then > filled the logs with errors and subsequently filled the drive > crashing all vms. So, to all intents and purposes, your domain was dead. > Luckily I had a backup of the DC image which

Linux debian1 3.2.0-4-686-pae #1 SMP Debian 3.2.68-1+deb7u1 i686 GNU/Linux it is serving as file server for a few windows pcs in a satellite office. I am trying to join the machine to a AD Domain in our main office. tried[b] net join -U duper%5HaveLefT -d5[/b] debug results:[code]INFO: Current debug levels: all: 5 tdb: 5 printdrivers: 5 lanman: 5 smb: 5 rpc_parse: 5 rpc_srv: 5 rpc_cli: 5

I'll bet static ip, with correct resolv.conf hosts and nsswitch.conf and krb5.conf. This must be the clue... > Creation of workstation account failed: NT_STATUS_OBJECT_NAME_NOT_FOUND So the join reaches the AD but here something happens. Russelt, can you try again with debug 10 and post both logs. net ads join -UAdministrator and net ads join -UAdministratos -S YOUR_ADDC.domain.tld.

> On 10 May 2024, at 11:55?PM, Rowland Penny via samba <samba at lists.samba.org> wrote: > > On Fri, 10 May 2024 23:19:32 +1200 > "Samba @ Pegasusnz via samba" <samba at lists.samba.org <mailto:samba at lists.samba.org>> wrote: > >> Luckily I had a backup of the DC image which I >> restored > > In an instance like this, you should be

Edit: When running 'winbindd -SFd5', I see a little more of the problem after I run my two ntlm_auth commands one after the other. I believe the 'crap' part is an acronym for 'Challenge Response Authentication Protocol', so why would it be failing? [ 2202]: request interface version (version = 28) [ 2202]: request location of privileged pipe getgroups root Could not

Hi Belle, Below is the output after I performed the suggested steps. root at esmad1apl01:~# net ads join -U media\\svc_domjoin02 -d6 INFO: Current debug levels: all: 6 tdb: 6 printdrivers: 6 lanman: 6 smb: 6 rpc_parse: 6 rpc_srv: 6 rpc_cli: 6 passdb: 6 sam: 6 auth: 6 winbind: 6 vfs: 6 idmap: 6 quota: 6 acls: 6 locking: 6 msdfs: 6 dmapi: 6 registry: 6

Hi Paul, I think -U is just ignored when -k and a valid ticket is available. Here you have a valid ticket, you use -k to ask smbclient to use credentials from that ticket, and you add -U for another user. Please try same smbclient command without -k, it should ask you the password for test123 user. That's not a bug, for me it is a lack of documentation on how to use -k switches with almost