search for: dc_ip

Hai eveyone.   I know about the dns "things" in the past. DNS Islanding problems etc. This one is a bit hijacking the subject : “Horrible BIND9_DLZ DNS breakage after DC replaced and samba-tool domain demote --remove-other-dead-server”     I would like to suggest a smale change in how we suggest to setup samba ADDC dns things, and i do think this help in the setup of the AD

...; 28589/named > udp 0 0 127.0.0.1:53 0.0.0.0:* > 28589/named > > Which plainly shows that it is listening on both 192.168.0.5:53 and > 127.0.0.1:53 > > Which to me means: > > On a single Samba AD DC: > > search <your dns domain> > DC_IP OR 127.0.0.1 > > With 2 DCs: > > First DC: > > search <your dns domain> > IP_OF_OTHER_DC > DC_IP OR 127.0.0.1 > > Second DC: > > search <your dns domain> > IP_OF_OTHER_DC > DC_IP OR 127.0.0.1 > > Rowland > Nothing wrong with tha...

...'s user_info struct [2004/07/15 09:59:39, 3] auth/auth.c:check_ntlm_password(219) ... Continues on and authenticats against the addresses above and works. The appears to be happening in libsmb/trust_utils.c enumerate_domain_trusts (): if ( !get_dc_name(domain, NULL, dc_name, &dc_ip) ) { DEBUG(3,("enumerate_domain_trusts: can't locate a DC for domain %s\n", domain)); The function get_dc_name was changed in libsmb/namequery_dc.c (1.5 to 1.6 in MAIN) from: if ( (our_domain && lp_security()==SEC_ADS) || strchr_m(domain, '.'...

...28589/named udp 0 0 127.0.0.1:53 0.0.0.0:* 28589/named Which plainly shows that it is listening on both 192.168.0.5:53 and 127.0.0.1:53 Which to me means: On a single Samba AD DC: search <your dns domain> DC_IP OR 127.0.0.1 With 2 DCs: First DC: search <your dns domain> IP_OF_OTHER_DC DC_IP OR 127.0.0.1 Second DC: search <your dns domain> IP_OF_OTHER_DC DC_IP OR 127.0.0.1 Rowland

Hello I've modified AD schema by adding a new auxiliary class (iscA) with an auxilairy attribute (iscA1). I've followed this explanation /_*entirely*_/ : http://semifershome.free.fr/semifer/index.php?2008/02/12/42-etendre-le-schema-active-directory-classes-attributs-et-display-specifiers I've named the menu item with the same name (AllowedService). By right-clicking on a AD user

...p Kerberos and can receive tickets correctly. I run net -d 4 ads join createcomputer=[Delegated OU] -U [account with join permissions] After filling in a password, I get the following: [2008/04/01 16:06:01, 4] libsmb/namequery_dc.c:ads_dc_name(139) ads_dc_name: using server= dc_server' IP=dc_ip ccspmed's password: [2008/04/01 16:06:03, 3] libsmb/namequery.c:get_dc_list(1489) get_dc_list: preferred server list: ", *" [2008/04/01 16:06:03, 4] libsmb/namequery.c:get_dc_list(1599) get_dc_list: returning 3 ip addresses in an ordered list [2008/04/01 16:06:03, 4] libsmb/namequ...

Hi All, can anyone make any sense of the error below, please advise if I need to log this as a bug but I'm not sure how to further diagnose what is happening. This is from my winbindd log file, thanks Andy. [2003/11/07 17:47:59, 1] nsswitch/winbindd.c:main(832) winbindd version 3.0.0 started. Copyright The Samba Team 2000-2003 [2003/11/07 17:48:00, 1]

Yes, you re right. Im using the *Samba Internal DNS Back End*. This is my config: # smb.conf [global] netbios name = DC1 realm = DOMAIN.DE workgroup = DOMAIN dns forwarder = <IP FIRST DNS SERVER> <IP SECOND DNS SERVER> server role = active directory domain controller idmap_ldb:use rfc2307 = yes log level = 3 tls

I am trying to join an existing samba server but I get an error message that the DNS update failed. I have read that this doesn?t matter and the join is still successful. But the problem comes when I try to grant privileges to the unix admins. root at dna:/home/pi# net ads join -U administrator Enter administrator's password: Using short domain name -- DOMAIN Joined 'DNA' to dns