search for: s4dc

...or with server: tsig verify failure all other tests are ok as far i can see. if tested bind9 ( debian wheezy stable ) 9.8.4 and i backported bind from sid, BIND 9.9.3-rpz2+rl.13214.22-P2-Debian-1:9.9.3.dfsg.P2-4 Both do not create these zone files. dlopen is loaded: Dec 19 14:50:58 ws005-s4dc-001 named[301]: generating session key for dynamic DNS Dec 19 14:50:58 ws005-s4dc-001 named[301]: sizing zone task pool based on 5 zones Dec 19 14:50:58 ws005-s4dc-001 named[301]: Loading 'AD DNS Zone' using driver dlopen when i run : samba_upgradedns --dns-backend=BIND9_DLZ it looks ok b...

...(is w2k3) which means 2008R2 (correct?) 2) on the samba4 side if i test samba-tool domain level show i have an error Could not retrieve the actual domain, forest level and/or lowest DC function level! from the ad user and computer mmc a can see that my w2k3 dc are: DCTYPE GC, DCVERSION W2K3 and my s4dc is DCTYPE GC, DCVERSION W2K I cannot connect to dns mmc for samba4dc because an error. Do i have to raise funtional level to w2k3 or w2k8r2 (as objectversion 47 say) of my samba4 dc ? does this action impact to the samba side only ? thanks in advance for any help

Hi guys, I'm about to replace an existing Windows Server 2003 Active Directory domain with Samba4 (package from Debian Wheezy). Joining the Samba4 dc according the Samba Wiki[1] is working great, replication works without errors from both worlds (windows or samba). After transferring the fsmo roles with ntdsutil to the samba4 domain controller (btw: does it matter if ntdsutil or samba-tool

> > > Morning Louis, Unless I totally misread this, the OP only > wants the DC > to query itself, no clients. > > I could understand it if they only wanted domain members to > query the DC. > > Stop and think about this, a client wants to know where > another domain > member is, or worse still, where the DC is, who does it ask ? It asks > its