similar to: report on issue of samba_upgradedns

Displaying 20 results from an estimated 1000 matches similar to: "report on issue of samba_upgradedns"

2016 Apr 12
2
Failed to re-index objectSid after botched DLZ back-end update
Alright, I'm taking the plunge: We're switching our three AD DCs from Samba internal to BIND_DLZ back end. I needed a version of BIND with DLZ, as it appears support for that is not so ubiquitous. I went here first: https://wiki.samba.org/index.php/Using_BIND_DLZ_backend_with_secured_/_signed_DNS_updates We use Ubuntu 14.04 here, and the Debian/Ubuntu instructions fail on apt-get
2016 Nov 17
2
readonly DC?
Hello Samba-ers, I tried to continue my Samba setup after a long pause doing other stuff. To recall, I want to run two Samba DCs for one domain as virtual machines on two Windows systems (I switched from VirtualBox to Hyper V, which helps to run them automatically at system startup, but I don´t think that really matters). Both DCs shall use themselves as DNS server as the VPN in between is
2016 Nov 17
0
readonly DC?
On Thu, 2016-11-17 at 18:31 +0000, Jo L via samba wrote: > Hello Samba-ers, > > I tried to continue my Samba setup after a long pause doing other > stuff. > To recall, I want to run two Samba DCs for one domain as virtual > machines on > two Windows systems (I switched from VirtualBox to Hyper V, which > helps to > run them automatically at system startup, but I don´t
2016 Jul 11
2
Successes an failures with Samba 4.3.9 and FreeBSD-10.3
OK. "net cache flush" worked (dunno why a restart isn't equivalent, but hey). So let's start peeling back other issues! On Mon, Jul 11, 2016 at 1:54 PM, Rowland penny <rpenny at samba.org> wrote: > On 11/07/16 17:57, Zaphod Beeblebrox wrote: > >> >> >> - Whether I use BIND9_DLZ or I use SAMBA_INTERNAL, >> samba_dnsupdate
2017 May 09
0
bugid https://bugzilla.samba.org/show_bug.cgi?id=12031
I'm having a similar issue on a new DC I've installed today: [root at theoden ~]# samba-tool ntacl sysvolcheck ERROR(<type 'exceptions.TypeError'>): uncaught exception - must be string, not None File "/usr/lib64/python2.7/site-packages/samba/netcmd/__init__.py", line 176, in _run return self.run(*args, **kwargs) File
2012 Feb 11
1
samba 4 provision fails
Version 4.0.0alpha18-GIT-389bb4f Ubuntu 11.10 Provision fails with: Setting up sam.ldb users and groups Traceback (most recent call last): File "./source4/setup/provision", line 262, in <module> useeadb=eadb, next_rid=opts.next_rid, lp=lp) File "bin/python/samba/provision/__init__.py", line 1757, in provision am_rodc=am_rodc, lp=lp) File
2011 Mar 06
1
Samba4 - Constraint violation - check_password_restrictions: the password does not meet the complexity criteria!'
Hello All, Firstly many apologies if this post has been asked before.? I did google search but not much info.? I've been trying to get the latest samba4 running on a test computer running ubuntu 9.10 (kernel 2.6.31-22-generic), by following the steps found through http://wiki.samba.org/index.php/Samba4/HOWTO.? Samba4 compiled successfully and right through Step 4 . Provision Samba, I'm
2016 Dec 15
4
Error on samba-tool domain provision
Hi, Anyone knows what is this? [root at artemis bin]# ./samba-tool domain provision --use-rfc2307 --interactive Realm [DOM.CITY10.COM.BR]: Domain [DOM]: Server Role (dc, member, standalone) [dc]: DNS backend (SAMBA_INTERNAL, BIND9_FLATFILE, BIND9_DLZ, NONE) [SAMBA_INTERNAL]: DNS forwarder IP address (write 'none' to disable forwarding) [187.85.85.1]: Administrator password: Retype
2017 Mar 11
4
samba 4.6.0 dc provisioning fails with exception
Hello, I have a problem with samba provisioning as DC. CentOS 7, built from tarball using samba howto. Below is the output. I would have filled bug report, but the "New Account" in bugzilla is not working also :( [root at dc samba-4.6.0]# samba-tool domain provision --use-rfc2307 --realm navidom.office.navi.pl --domain NAVIDOM --server-role dc --adminpass DuDu778$$# --dns-backend
2016 Dec 16
2
remove dead server (samba 4.4.4)
Hi, I'm trying to remove a DC from a site we have shutdown. The demote command is throwing up this message: [root at aragorn ~]# samba-tool domain demote --remove-other-dead-server=pippin Removing nTDSConnection: CN=eca08dbb-1f34-476e-96dd-33ec22b2bc94,CN=NTDS Settings,CN=GANDALF,CN=Servers,CN=SAOPAULO,CN=Sites,CN=Configuration,DC=e-trust,DC=com,DC=br Removing nTDSDSA: CN=NTDS
2017 Feb 24
0
Samba firts DC fail over
No, the question is about your client machine. Who are the DNS servers configured on it? Does it have a second dns server configured? If it uses your first DC as DNS, and you take that DC offline, who the client machine will query for domain info? As for the issue below it is normal. Every DC registers an "A" record for your domain name. When you use dig, it will retrieve all
2017 Feb 25
0
Samba firts DC fail over
Hello.In my configuration I have three DCs one who build the domain and two replication. For the configuration of the client I put in the resolv.conf the three DC addresse. So normally the client is able to contact all DCs of domain. But to have domain information only the dc that built the domain provided them, and when I stop it, replication DCs are unable to provide this information to client
2017 Jan 10
0
Winbind PAM RHEL
check your /etc/nsswitch.conf and confirm that passwd and group lines have the winbind keyword passwd: files winbind group: files winbind Em 10/01/2017 10:29, Oliver Werner via samba escreveu: > HI, > > on debian i use pam winbind by adding > > the file /usr/share/pam-configs/winbind and enable this. > > Is there another way on RHEL? i have configure RHEL that wbinfo -u
2017 Feb 17
0
samba ad sysrepl
who are the DNS servers your workstations have configured? Windows does not behave very well if the first DNS is offline, as far as I have tested. Em 17/02/2017 13:20, basti via samba escreveu: > Hello, > I have installed an samba ad1 and an samba ad2 with replication. > On the dc1 "samba-tool drs showrepl" say "... was successful" > On dc2 there is the same. >
2017 Feb 24
0
Samba firts DC fail over
who are the DNS servers used by the client machine? Em 24/02/2017 05:42, Keshia lesly diana Etsiké malam via samba escreveu: > Hello, > I am currently testing for Samba4. The creation of the domain and the secondary Dc implementation works well. But by performing tests for a fail over situation I realized that when the DC that created the domain is in fail over the linux client machine can
2017 Jan 10
1
Winbind PAM RHEL
jep thats also configured. OLIVER WERNER System-Administrator > Am 10.01.2017 um 13:41 schrieb Vinicius Bones Silva via samba <samba at lists.samba.org>: > > check your /etc/nsswitch.conf and confirm that passwd and group lines have the winbind keyword > > passwd: files winbind > group: files winbind > > > > Em 10/01/2017 10:29, Oliver Werner via samba
2016 Nov 10
0
Block samba hosts by domain
PROBABLY its a problem with your reverse dns resolution. From the samba server, if you do a host 172.25.0.12 (change as appropriate) does it resolve to a hostname in the .example.com domain? If it don't, samba wont know that it's uspposed to block the access. Em 09/11/2016 19:37, Erick Ocrospoma via samba escreveu: > Hi everybody, > > > I'm setting up a Samba under
2016 Nov 01
0
NT_STATUS_INVALID_SID
I'm not sure I understood the question. Uncommenting the lines or commenting them yelds the same results, as long as "idmap_ldb:use rfc2307 = yes" is kept in place. Commenting it as well changes the ids to the 3 million range. Cleaning the caches did not affect the results. Em 29/10/2016 07:31, Andrew Bartlett via samba escreveu: > On Thu, 2016-10-27 at 17:23 -0200, Vinicius
2016 Oct 27
0
NT_STATUS_INVALID_SID
Hi Rowland, Just to let you know, we removed all the idmap entries we had on the smb.conf of our two DCs and the ids reported by getent passwd at the DCs were in the 3.000.000 range, as you said. We had to add back 'idmap_ldb:use rfc2307 = yes' to get the user listing with the original numbers on the DCs. Here's what we commented out on the configurationfiles. #
2017 Feb 24
2
Samba firts DC fail over
Just a thought if the client machines are still getting a listing in the DNS for the failed machines wouldn't this be a problem? How would the programs know not to use the failed server? Is there a way to temporarily move the failed machines out of dns listings? On Fri, Feb 24, 2017 at 8:52 AM, Vinicius Bones Silva via samba < samba at lists.samba.org> wrote: > No, the question is