similar to: PDC died, broken after reboot

Did you have a backup of your information? My upbringing and was tought to have backups of backups. In case of emergencies. Your situation is not different your a very good admin but always keep backups. My advice is try to find matching components and see if that fires up your server to get it going. Then if it starts to work. If not. ...... Your up a creek. Sent from my T-Mobile 4G LTE device

Last month I struggled with a severe DLZ issue and today I could solve it. Credits for the important idea go to Peter Serbe, thanks! I checked the DNS contents using RSAT. There was nothing wrong with SOA nor NS entries, but the reverse zones were actually forward zones with proper names in the in-addr.arpa. domain. I built proper reverse zones and deleted the forward-reverse zones and Bind

I run a Samba4 AD and joined a Synology NAS running Samba 3.6.9. I can access the shares using smbclient or mount -t cifs from all Linux machines (usually running Samba 3.6.6 clients). I can mount the shares from WinXP home and Win7 home. However, with a Win7 Ultimate machine joined to the AD most of the time it doesn't work. I can logon to the machine with my AD credentials, but I am

I created a demo share on my AD DC. After obtaining a copy of Win7 Ultimate I could now verify that the share has all rights granted to anyone (don't know how Windoze call "Jeder" in English). I can read and write the Share using AD\Administrator. AD\StandardUser can mount the share and read, what the Administrator put there. But he cannot create or modify files.

I have a running Bind9 infrastructure and intend to have Samba its specialities, but leave the bulk to Bind. My idea is to configure a slave zone with Samba as master in my top level Bind. However, this would need Samba to allow-forward. Is there any way to configure the internal DNS like that? Or do I have to run a Bind instance on the samba machine for that purpose? Thanks for your help, -

Dear Roland, and here we have one reasons / prove regarding Debian and current Samba BIND DLZ issues : http://metadata.ftp-master.debian.org/changelogs//main/b/bind9/bind9_9.8.4.dfsg.P1-6+nmu2+deb7u3_changelog MSG >> " * disable dlz until we get a patch to make it build again" Well Debian Maintainers seems seeking missing the dlz patches that RHEL & SLES maintainers created

I set-up a basic AD DC using samba 4.1.9 successfully. I joined my NAS to the domain, i.e. I saw no errors and see the users and groups of my AD listed in the GUI of the NAS. When I try to connect to a share of the NAS the following happens: mgr at ws1:~$ smbclient -U 'AD\mgr' //nas/Test Enter AD\mgr's password: Domain=[AD] OS=[Unix] Server=[Samba 3.6.9] tree connect failed:

And some more information about this strange effect apparently no-one has seen before. I now added the missing zone: samba-tool dns zonecreate verdandi 10.16.172.in-addr.arpa -U Administrator and it claims that the zone is okay, but the next one is missing: Dec 29 10:31:12 verdandi named[2601]: Loading 'ad.microsult.de' using driver dlopen Dec 29 10:31:12 verdandi named[2601]:

Hi, I'm going to migrate my old CUPS server to a new setup. It shall provide the printing backend for Samba4 and should integrate as seamless as possible. Both Windows and Linux users should not require additional passwords, but should be authenticated by their Kerberos tickets. Is there anything particular to consider? E.g. has the CUPS server to be joined to the AD and should it run a

I set up two AD DC with external bind and it used to work for a while. Following a Bind9 upgrade named complained about missing SOA and NS records in the DLZ zones and could not be started anymore. Monday, due to a misinterpretation of some queries, I restarted Bind on the hitherto working system and I got the same error messages. No nothing changed - no changes in configuration, no updates.

I just upgraded bind9 on my backup DC to 9.9.5-7-Debian and restarting the service failed: Dec 22 12:25:55 verdandi named[18534]: starting BIND 9.9.5-7-Debian -u bind -4 Dec 22 12:25:55 verdandi named[18534]: built with '--prefix=/usr' '--mandir=/usr/share/man' '--infodir=/usr/share/info' '--sysconfdir=/etc/bind' '--localstatedir=/var'

Greg, > Unfortunately, these attributes do not exist as standard, so you would > either have to add a user with ADUC or manually add them yourselves with > ldbedit. As standard on windows, they both start at '10000', though you > can set them to whatever you require, just make sure that they do not > interfere with any local Unix users. If you like to manage Unix users

I?ve been doing some testing on Ubuntu server 14.04 (Version 4.1.6-Ubuntu) over the last week or so. I found some fairly good guidance and configured a PDC using BIND9 as the dnsbackend without too much trouble. Configuring a BDC is proving to be a bit more of a challenge but I think I?m closing in on it (no cheating on AppArmor, permissions and such). I?m reading the wiki

I found in my firewall logs something that looked somewhat like a port scan originating from my AD DC. So I started to check the machine and already found something strange using ps aux: root at samba:/# samba -V Version 4.1.11-Debian root at samba:/# ps aux USER PID %CPU %MEM VSZ RSS TTY STAT START TIME COMMAND [...] root 10675 0.0 2.8 457368 29620 ? S Nov04

Am 19.01.2015 um 12:30 schrieb Ashish Yadav: > Hi, > > On Mon, Jan 19, 2015 at 3:45 PM, Lars Hanke <debian at lhanke.de > <mailto:debian at lhanke.de>> wrote: > > I run a Samba4 AD and joined a Synology NAS running Samba 3.6.9. I > can access the shares using smbclient or mount -t cifs from all > Linux machines (usually running Samba 3.6.6 clients).

Thanks to both of you - exactly the piece I was missing. -----Original Message----- From: tms3 at tms3.com [mailto:tms3 at tms3.com] Sent: Monday, January 10, 2011 12:52 PM To: Christ Schlacta Cc: samba at lists.samba.org Subject: Re: [Samba] Reestablishing trust with PDC > > > you haven't tried experimenting with backing up and restoring the > samba password cache. look in

Am 18.12.2015 um 12:30 schrieb Rowland penny: > On 18/12/15 11:19, Ole Traupe wrote: >> Hi Rowland, >> >> I am very thankful, that you take the time and test all this! > > No problem. > >> >> Before I go and check if this is the same with my setup and possibly >> the problem, could you perhaps try a logon to a member server, while >> the 1st

It is actually rather easy to set the attributes via powershell, and that is probably the best way to add them in a Server 2012 R2 environment. I wrote a powershell script to do this automatically for users and groups in an entire domain that should be pretty generic to be reused. It also mirrors the logic used in automatic winbind UID/GID generation to be able to coexist in an environment where

Am 18.12.2015 um 14:56 schrieb Rowland penny: > On 18/12/15 12:07, Ole Traupe wrote: >> >> >> Am 18.12.2015 um 12:30 schrieb Rowland penny: >>> On 18/12/15 11:19, Ole Traupe wrote: >>>> Hi Rowland, >>>> >>>> I am very thankful, that you take the time and test all this! >>> >>> No problem. >>>

Mandi! Rowland Penny via samba In chel di` si favelave... > So, it sounds like you have a PDC for the domain 'DOMAIN' and an AD DC > for the domain 'DOMAIN' both using the same SID, I don't think this is > going to work. I suggest you turn the old PDC off. No no no! I'm not mad! ;-) There's the OLD PDC for the domain 'SVCORSI', and the new AD DC