similar to: Problem with Samba4 DB

Thx mathias for your reply First, yes im using internal DNS, i just try to add new dns from other dc but it doesnt work, i think the (maybe) corrupted dns data already sync to other dc And i still run my samba4 installation, because sofar the only problem is, i cant add new dns record In other case i found up one of my team just re install 2 samba4 server in site office with different AD

hi mathias let me confirm your statement so.. you think if we demote those 2 DC server that already offline, the DNS will be running well well if this is one of option we have, i will consider to upgrade our FSMO DC from samba 4.1.X to 4.4.x , by the way, are there any consideration if we update samba directly from 4.1 to 4.4 ? let me answer some of your question *1 - what command are you

dear roland and mathias i already upgrade samba server version to 4.4.4 i have domote 3 of 4 offline dc successfully one dc that i cant demote shown this error message /**//*[root at pdc ~]# samba-tool domain demote --remove-other-dead-server=dc25*//* *//*ERROR: Demote failed: DemoteException: dc25 is not an AD DC in domain.co.id*//* *//*A transaction is still active in ldb context

Oki Doki. First the fact you can't add new DNS entry in your DNS zones is not a blocking point to remove a DC. It's a blcoking point to add new entries. Now you are the one deciding if you would remove it or not, but seriously, for me that's not a reason to keep up it running: you can replace it by another DC which will do exactly the same job and if you are lucky enough you would be

hi guys i need some advice for my case that i faced here.. i have Two AD with two different domain, platform and network : i expect all user in different domain can resolve the other domain dns let say 1. domainwin.com >> windows 2008 AD >> 172.16.1.2 2. domainnux.com >> Samba 4 AD >> 172.16.2.2 is it possible if i create 1 new BIND DNS Server in 172.16.3.2

On 15/06/16 10:14, bentunx wrote: > hi mathias > > let me confirm your statement > so.. you think if we demote those 2 DC server that already offline, > the DNS will be running well > well if this is one of option we have, i will consider to upgrade our > FSMO DC from samba 4.1.X to 4.4.x , by the way, are there any > consideration if we update samba directly from 4.1

hi all i have problem with my multi-site AD-DC installation, one of my DC, suddently cant start well, i think problem(corrupt) with the LDAP database then i try to re join it, but every time i try to join it i always has issue like this /Finding a writeable DC for domain 'domain.co.id' Found DC pdc.domain.co.id Password for [domain\administrator]: workgroup is domain realm is

On Mon, Aug 8, 2016 at 5:49 AM, Stefan Kania <stefan at kania-online.de> wrote: > -----BEGIN PGP SIGNED MESSAGE----- > Hash: SHA1 > > you should set up a dns-proxy and use this proxy as forwarder in your > domains Really, really not the same thing as a DNS slave. If your DNS master, such as your Samba or AD server, goes toes up for whatever reason, the DNS slave can continue

On Tue, 15 Aug 2017 20:52:12 +0700 zhia chandra via samba <samba at lists.samba.org> wrote: > hai belle > > Was this pc a member of any NT4 Domain in the past? nope .. > > but actually our samba4 server was upgrated from samba3 base on > clearOS 5 .. > > and actually i still running samba3 in stand alone mode for netbios > only, incase some PC cannot map /

On Mon, 21 Aug 2017 22:15:58 +0700 zhia chandra <bentunx at gmail.com> wrote: > hi rowland > > > *OK, you were asked 'Was this pc a member of any NT4 Domain in the > past?'You replied with:'nope ..'* > > well all the pc who had trust relationship problem is new PC with > windows 7 or earlier .. they never connected to PDC in clear OS > > i

Hello, i have two samba 4 domain controllers v4.1.0, with bind_dlz running so far without problems, but now i have some problems with dns. Running samba-tool dns query dc1 samdom.example.com @ ALL returns this error: ERROR(runtime): uncaught exception - (1383, 'WERR_INTERNAL_DB_ERROR') File "/usr/local/samba/lib64/python2.6/site-packages/samba/netcmd/__init__.py", line 175,

Hi, I just solved this problem for myself: # samba-tool user add my-username-here User 'my-username-here' added successfully # samba-tool group addmembers 'Domain Admins' my-username-here Added members to group Domain Admins # samba-tool dns add localhost example.com testname A 10.0.0.2 -U my-username-here --password="my-password-here" Record added successfully >

hii all i have some issue with my samba 4 installation, i use samba 4.1.3, suddenty my dns stop working and i try to restart the service but nothing good happen i check on samba log i found this Aug 25 21:15:39 pdc samba[6605]: [2014/08/25 21:15:39.206091, 0] ../lib/util/fault.c:72(fault_report) Aug 25 21:15:39 pdc samba[6605]: ===============================================================

hii guys i have some issue with dns in samba 4 i have install and setup 2 samba dc in different Site site2 dc joint to site1 dc, with internal dns topology : site1 --- openvpn server --- firewall --- wan --- openvpn client --- site2 192.168.1.0/24 192.168.2.0/24 in site1 i have some application let say email server: mail.local.lan > 192.168.1.2 web server : web.local.lan > 192.168.1.3

Hai, Was this pc a member of any NT4 Domain in the past? You can try the following. Login as a Local Administrator on the pc. ( you may need to create one first. ) Open PowerShell as administrator ( you need powershell 3.0 for this ) Run: Reset-ComputerMachinePassword -Server AD_DC.DOMAIN.TLD -Credential YOUR_AD_DOM\Adminstrator Restart-Computer No powershell V3. netdom.exe resetpwd

hi all i have some issues with my samba4 installation here is the case 1. i have about 1 dc in my head office as a PDC and 9 dcs in 9 different site office 2. each site office connected to head office by VPN, but each site office cant connect each other 3. each site and head office have a different network 4. i user samba 4.1.3 5. i put all dc in same site , because i think samba 4.1.* has

and you have added the following to the /etc/hosts 172.16.99.3 pdc.domain.co.id pdc and you did setup your krb5.conf in that way you point directly to the correct hosts without the use of a search like: [logging] default = FILE:/var/log/krb5libs.log kdc = FILE:/var/log/krb5kdc.log admin_server = FILE:/var/log/kadmind.log [libdefaults] default_realm = SMBDOM.EXAMPLE.COM dns_lookup_realm =

hii all i think i have finished trial to upgrade my samba 3 pdc server base on clearos 5.2 into new samba 4.1.1 in new machine and different network but then i realized when i check my user with samba-tool, i cant find any of my samba 3 user account, all i find is [root at pdcs4 ~]# samba-tool user list Administrator dns-pdc krbtgt Guest has anyone got same problem with me ? how to overcome it

hii all i need some suggestion about implementing samba 4 in multisite environment im still new in samba 4, i have finish install my first samba 4 DC in my centos 6 machine without any problem. i have plan to implement samba 4 in distribute / multisite environment, i have one head quarter office and aroung 20 site office, in my head quarter office i have not more than 50 PC client and in every

> I have metadata enabled, and I am doing a relay from my home dsl > system to the t-1 system, which is doing the yp updates. However, my > shoutcast entry doesn't have the longer description or the "now > playing" option - should metadata take care of this, and will metadata > survive through a relay? Now playing only works with title streaming. this