search for: ad51

Hi all. If I have AD domain dc.samges.ru, how to setup a hostname, hosts file and resolv.conf file? DNS is samba internal type. Now I have settigs as here: (ad41 is dc with fsmo roles, ip 172.16.214.141, ad51 is a second dc, ip 172.16.214.151) root at ad51:~# hostname -s ad51 root at ad51:~# hostname -d samges.ru root at ad51:~# hostname -f ad51.samges.ru Must I have an $SERV.$ADDOMAIN hostname, like ad51.dc.samges.ru ? If I change hostname now, what will happen in AD domain ? And second part of que...

...Lykov via samba <samba at lists.samba.org> wrote: > Hi all. > > If I have AD domain dc.samges.ru, how to setup a hostname, hosts file > and resolv.conf file? DNS is samba internal type. > > Now I have settigs as here: > (ad41 is dc with fsmo roles, ip 172.16.214.141, ad51 is a second dc, > ip 172.16.214.151) > > root at ad51:~# hostname -s > ad51 > root at ad51:~# hostname -d > samges.ru > root at ad51:~# hostname -f > ad51.samges.ru > > Must I have an $SERV.$ADDOMAIN hostname, like ad51.dc.samges.ru ? Yes > If I change hostname...

Tom In Shorewall6 4.4.27 the following proxyndp entry: 2001:4d48:ad51:24::f3 eth2 eth0 no no does not add the required route. The code produced in /var/lib/shorewall6/.restart is: qt $IP -6 route del 2001:4d48:ad51:24::f3/128 dev eth2 run_ip route add 2001:4d48:ad51:24::f3/128 dev eth2 Splitting the line into 2 separate lines: qt $IP -6 route del 2001:4d...

...on command line we have tried to use > the "heal" command but elements remain always unsynced .... > > Below the heal command "status": > > [root at node01 ~]# gluster volume heal engine info > Brick node01:/gluster/engine/brick > /.shard/8aa74564-6740-403e-ad51-f56d9ca5d7a7.48 > /.shard/8aa74564-6740-403e-ad51-f56d9ca5d7a7.64 > /.shard/8aa74564-6740-403e-ad51-f56d9ca5d7a7.60 > /.shard/8aa74564-6740-403e-ad51-f56d9ca5d7a7.2 > /.shard/8aa74564-6740-403e-ad51-f56d9ca5d7a7.68 > /8f215dd2-8531-4a4f-b6ed-ea789dd8821b/images/19d71267- > 52a4-42...

18.11.2016 15:22, Rowland Penny via samba пишет: >> root at ad51:~# hostname -f >> ad51.samges.ru >> Must I have an $SERV.$ADDOMAIN hostname, like ad51.dc.samges.ru ? > Yes > >> If I change hostname now, what will happen in AD domain ? > > Your machine will not be found. But it can be found via DNS, why changing local (for this ser...

On 07/20/2017 02:20 PM, yayo (j) wrote: > Hi, > > Thank you for the answer and sorry for delay: > > 2017-07-19 16:55 GMT+02:00 Ravishankar N <ravishankar at redhat.com > <mailto:ravishankar at redhat.com>>: > > 1. What does the glustershd.log say on all 3 nodes when you run > the command? Does it complain anything about these files? > > >

...#39;t, please provide the getfattr outputs of the 12 files from > all 3 nodes using `getfattr -d -m . -e hex */gluster/engine/brick/* > path-to-file` ? > > *NODE01:* *getfattr: Removing leading '/' from absolute path names* *# file: gluster/engine/brick/.shard/8aa74564-6740-403e-ad51-f56d9ca5d7a7.68* *trusted.afr.dirty=0x000000000000000000000000* *trusted.afr.engine-client-1=0x000000000000000000000000* *trusted.afr.engine-client-2=0x000000120000000000000000* *trusted.bit-rot.version=0x090000000000000059647d5b000447e9* *trusted.gfid=0xe3565b5014954e5bae883bceca47b7d9* *getfattr...

Hai, Since your getting. finddcs: No matching server found > ERROR: Invalid IP address '3(NXDOMAIN)'! There is something wrong in the base of you setup. Check all DC's for ipnumbers (A) and PTR records. Dont forget to create the reverse zone yourself. https://wiki.samba.org/index.php/Samba_AD_DC_Troubleshooting

...e is something wrong in the base of you setup. yes, and it is a server own local hostname see "DC server own hostname must be part of ad dc domain?" thread your script relies on "hostname -d" output, but my server have hostname domain != AD DC domain hostname domain : root at ad51:~# hostname -d samges.ru AD DC domain: dc.samges.ru local fqdn hostname for server root at ad51:~# hostname -f ad51.samges.ru server in ad dc domain: root at ad51:/var/log/samba# host -t A ad51.dc.samges.ru ad51.dc.samges.ru has address 172.16.214.151 > Check all DC's for ipnumbers (A)...

...tried to use the "heal" command but elements remain always > unsynced .... > > Below the heal command "status": > > [root at node01 ~]# gluster volume heal engine info > Brick node01:/gluster/engine/brick > /.shard/8aa74564-6740-403e-ad51-f56d9ca5d7a7.48 > /.shard/8aa74564-6740-403e-ad51-f56d9ca5d7a7.64 > /.shard/8aa74564-6740-403e-ad51-f56d9ca5d7a7.60 > /.shard/8aa74564-6740-403e-ad51-f56d9ca5d7a7.2 > /.shard/8aa74564-6740-403e-ad51-f56d9ca5d7a7.68 > /8f215dd2-8531-4a4f-b6ed-ea789dd8821b/images/19...

Hi, Thank you for the answer and sorry for delay: 2017-07-19 16:55 GMT+02:00 Ravishankar N <ravishankar at redhat.com>: 1. What does the glustershd.log say on all 3 nodes when you run the > command? Does it complain anything about these files? > No, glustershd.log is clean, no extra log after command on all 3 nodes > 2. Are these 12 files also present in the 3rd data brick?

...the 12 files > from all 3 nodes using `getfattr -d -m . -e hex > //gluster/engine/brick//path-to-file` ? > > > */NODE01:/* > /getfattr: Removing leading '/' from absolute path names/ > /# file: > gluster/engine/brick/.shard/8aa74564-6740-403e-ad51-f56d9ca5d7a7.68/ > /trusted.afr.dirty=0x000000000000000000000000/ > /trusted.afr.engine-client-1=0x000000000000000000000000/ > /trusted.afr.engine-client-2=0x000000120000000000000000/ > /trusted.bit-rot.version=0x090000000000000059647d5b000447e9/ > /trusted.gfid=0...

...it to the list so everybody can learn from it. > Why you use "hostname -i" ? man hostname wil tell.. But i'll try to explain it a bit. Read the Description, its also about how the hostnames are resolved within the systemfuntions. Like gethostname and gethostbyname > root at ad51:~# hostname -i > 127.0.0.1 > root at ad51:~# hostname -I > 172.16.214.151 Hostname -i , works only if the hostname can be resolved. Hostname -I , Displays all network addresses of the host. ( but not 127.0.0.1 ) Now remembering that. Imo, hostname -i and hostname -I should imo not re...

...samges.ru, internet zone samges.ru Forward zones: dc.samges.ru _msdcs.dc.samges.ru All worked normal, but then my coworker create forward zone samges.ru (using windows RSAT tools) It serves some names, I can add names to it but not delete records from it. When I try, I got this error: root at ad51:~# samba-tool dns delete ad51.samges.ru samges.ru vjud A 213.156.210.216 -U lmy GENSEC backend 'gssapi_spnego' registered GENSEC backend 'gssapi_krb5' registered GENSEC backend 'gssapi_krb5_sasl' registered GENSEC backend 'schannel' registered GENSEC backend 'sp...

...: > dc.samges.ru > _msdcs.dc.samges.ru > > All worked normal, but then my coworker create forward zone > samges.ru (using windows RSAT tools) > > It serves some names, I can add names to it but not delete records > from it. When I try, I got this error: > > root at ad51:~# samba-tool dns delete ad51.samges.ru samges.ru vjud A > 213.156.210.216 -U lmy > GENSEC backend 'gssapi_spnego' registered > GENSEC backend 'gssapi_krb5' registered > GENSEC backend 'gssapi_krb5_sasl' registered > GENSEC backend 'schannel' register...

...rn from it. > > > Why you use "hostname -i" ? > man hostname wil tell.. But i'll try to explain it a bit. > Read the Description, its also about how the hostnames are resolved > within the systemfuntions. Like gethostname and gethostbyname > > > root at ad51:~# hostname -i > > 127.0.0.1 > > root at ad51:~# hostname -I > > 172.16.214.151 > > Hostname -i , works only if the hostname can be resolved. > Hostname -I , Displays all network addresses of the host. ( but not > 127.0.0.1 ) Now remembering that. > > Imo, h...

...gt; Why you use "hostname -i" ? > > man hostname wil tell.. But i'll try to explain it a bit. > > Read the Description, its also about how the hostnames are resolved > > within the systemfuntions. Like gethostname and gethostbyname > > > > > root at ad51:~# hostname -i > > > 127.0.0.1 > > > root at ad51:~# hostname -I > > > 172.16.214.151 > > > > Hostname -i , works only if the hostname can be resolved. > > Hostname -I , Displays all network addresses of the host. ( but not > > 127.0.0.1 ) Now r...

On 12/8/2017 2:54 PM, Taylor Hammerling via samba wrote: > Glad you guys replied, here is my output :D > > root at dc1:~# ./samba-setup-checkup.sh > Check hostnames : Ok > ./samba-setup-checkup.sh: line 89: [: too many arguments > Checking detected host ipnumbers from resolv.conf and default gateway > Ping gateway ip : 172.28.0.1 : Ok > ping nameserver1: 172.28.255.49 : Ok

Hello, I try to add a new dc to my domain, but the sysadmin installed the main dc left misconfigured dns zones that I can not remove. ¿Is it possible to provision the domain again using new samba as main dc Keeping users and passwords Of the previous dc? The current main dc runs samba 4.4. Best regards, Santiago. -- Santiago Londoño Mejía Analista de Infraestructura t. (574) 605 25