Lionel Monchecourt
2020-Feb-27 12:39 UTC
[Samba] Samba AD - Different IP than the existing one assigned
Hi,
I want to use samba as AD.
everything seemed to be ok so far with the install and the config.
STATUS=daemon 'smbd' finished starting up and ready to serve connections
Feb 27 10:34:03 ip-1XX winbindd[22083]: [2020/02/27 10:34:03.002858, 0]
../lib/util/become_daemon.c:124(daemon_ready)
Feb 27 10:34:03 ip-1XX winbindd[22083]: STATUS=daemon 'winbindd'
finished
starting up and ready to serve connections
Now, when I performed a check for the adc1, I get an answer BUT ,the IP is
not the one of the machine
I'm using the internal_samba DNS, I understood that when the service starts,
it updates himself with proper IP. am I wrong ? how can I solve this problem
?
Thx
host -t A adc1.mydomain.com
adc1.mydomain.com has address 172.31.44.6
but I have :
eth0: flags=4419<UP,BROADCAST,RUNNING,PROMISC,MULTICAST> mtu 1500
inet 172.31.6.15 netmask 255.255.240.0 broadcast 172.31.15.255
inet6 fe80::bf:52ff:fe4a:fe3c prefixlen 64 scopeid 0x20<link>
ether 02:bf:52:4a:fe:3c txqueuelen 1000 (Ethernet)
RX packets 7111658 bytes 9681867004 (9.6 GB)
RX errors 0 dropped 0 overruns 0 frame 0
TX packets 2255773 bytes 398129876 (398.1 MB)
TX errors 0 dropped 0 overruns 0 carrier 0 collisions 0
--
Sent from: http://samba.2283325.n4.nabble.com/Samba-General-f2403709.html
Rowland penny
2020-Feb-27 13:04 UTC
[Samba] Samba AD - Different IP than the existing one assigned
On 27/02/2020 12:39, Lionel Monchecourt via samba wrote:> Hi, > I want to use samba as AD. > everything seemed to be ok so far with the install and the config. > > STATUS=daemon 'smbd' finished starting up and ready to serve connections > Feb 27 10:34:03 ip-1XX winbindd[22083]: [2020/02/27 10:34:03.002858, 0] > ../lib/util/become_daemon.c:124(daemon_ready) > Feb 27 10:34:03 ip-1XX winbindd[22083]: STATUS=daemon 'winbindd' finished > starting up and ready to serve connectionsI think we need to see more of that log, particularly the lines above 'STATUS'> Now, when I performed a check for the adc1, I get an answer BUT ,the IP is > not the one of the machine > I'm using the internal_samba DNS, I understood that when the service starts, > it updates himself with proper IP. am I wrong ? how can I solve this problemWhere did you get that idea from ? A DC should have a fixed IP and that is what Samba should use. Do you have more than one ethernet device ? What OS is this ? What version of Samba ? Can you post the contents of the following files: /etc/resolv.conf /etc/hostname /etc/hosts /etc/samba/smb.conf (or wherever smb.conf is on your DC) Rowland
Lionel Monchecourt
2020-Feb-27 13:25 UTC
[Samba] Samba AD - Different IP than the existing one assigned
Hi, Thanks for helping. Answers in line : Hi, I want to use samba as AD. everything seemed to be ok so far with the install and the config. STATUS=daemon 'smbd' finished starting up and ready to serve connections Feb 27 10:34:03 ip-1XX winbindd[22083]: [2020/02/27 10:34:03.002858, 0] ../lib/util/become_daemon.c:124(daemon_ready) Feb 27 10:34:03 ip-1XX winbindd[22083]: STATUS=daemon 'winbindd' finished starting up and ready to serve connections I think we need to see more of that log, particularly the lines above 'STATUS' Log.smbd :>[2020/02/24 10:02:22.602083, 0] ../source3/smbd/server.c:1815(main) server role = 'active directory domain controller' not compatible with running smbd standalone. You should start 'samba' instead, and it will control starting smbd if required [2020/02/24 10:02:38.247239, 0] ../lib/util/become_daemon.c:124(daemon_ready) STATUS=daemon 'smbd' finished starting up and ready to serve connections [2020/02/24 10:17:43.198864, 0] ../lib/util/become_daemon.c:124(daemon_ready) STATUS=daemon 'smbd' finished starting up and ready to serve connections [2020/02/27 10:11:32.523331, 0] ../lib/util/become_daemon.c:124(daemon_ready) STATUS=daemon 'smbd' finished starting up and ready to serve connections [2020/02/27 10:34:02.981826, 0] ../lib/util/become_daemon.c:124(daemon_ready) STATUS=daemon 'smbd' finished starting up and ready to serve connections Log.samba ../source4/dsdb/dns/dns_update.c:290: Failed DNS update - with error code 110 [2020/02/27 12:44:23.443080, 0] ../source4/dsdb/dns/dns_update.c:290(dnsupdate_nameupdate_done) ../source4/dsdb/dns/dns_update.c:290: Failed DNS update - with error code 110 [2020/02/27 12:54:23.503162, 0] ../source4/dsdb/dns/dns_update.c:290(dnsupdate_nameupdate_done) ../source4/dsdb/dns/dns_update.c:290: Failed DNS update - with error code 110 [2020/02/27 13:04:23.561187, 0] ../source4/dsdb/dns/dns_update.c:290(dnsupdate_nameupdate_done) ../source4/dsdb/dns/dns_update.c:290: Failed DNS update - with error code 110 [2020/02/27 13:14:23.616350, 0] ../source4/dsdb/dns/dns_update.c:290(dnsupdate_nameupdate_done) ../source4/dsdb/dns/dns_update.c:290: Failed DNS update - with error code 110 Nothing is running on port 53 : tcp 0 0 0.0.0.0:49153 0.0.0.0:* LISTEN tcp6 0 0 [::]:49153 [::]:* LISTEN udp 0 0 0.0.0.0:53447 0.0.0.0:* unix 2 [ ACC ] STREAM LISTENING 3728453 /var/lib/samba/ntp_signd/socket unix 2 [ ] DGRAM 3729533 /var/lib/samba/private/msg.sock/22087 unix 3 [ ] DGRAM 3892953 unix 3 [ ] STREAM CONNECTED 18537 /run/systemd/journal/stdout unix 2 [ ] DGRAM 3729538 unix 3 [ ] STREAM CONNECTED 21535 unix 3 [ ] STREAM CONNECTED 18536 unix 3 [ ] STREAM CONNECTED 15342 /run/systemd/journal/stdout unix 3 [ ] STREAM CONNECTED 25453 Now, when I performed a check for the adc1, I get an answer BUT ,the IP is not the one of the machine I'm using the internal_samba DNS, I understood that when the service starts, it updates himself with proper IP. am I wrong ? how can I solve this problem Where did you get that idea from ?> I read this in a post somewhere, but obviously it is not the case then ?A DC should have a fixed IP and that is what Samba should use.> yes ok : 172.31.6.15Do you have more than one ethernet device ?> Yes , here are the different devices, but none is matching this strange IPbr-07d306ca3f41: flags=4355<UP,BROADCAST,PROMISC,MULTICAST> mtu 1500 inet 172.19.0.1 netmask 255.255.0.0 broadcast 172.19.255.255 ether 02:42:61:fb:18:40 txqueuelen 0 (Ethernet) RX packets 0 bytes 0 (0.0 B) RX errors 0 dropped 0 overruns 0 frame 0 TX packets 0 bytes 0 (0.0 B) TX errors 0 dropped 0 overruns 0 carrier 0 collisions 0 br-eebd35f33249: flags=4419<UP,BROADCAST,RUNNING,PROMISC,MULTICAST> mtu 1500 inet 172.18.0.1 netmask 255.255.0.0 broadcast 172.18.255.255 inet6 fe80::42:dff:fed5:dd97 prefixlen 64 scopeid 0x20<link> ether 02:42:0d:d5:dd:97 txqueuelen 0 (Ethernet) RX packets 5577 bytes 3892905 (3.8 MB) RX errors 0 dropped 0 overruns 0 frame 0 TX packets 1731 bytes 172505 (172.5 KB) TX errors 0 dropped 0 overruns 0 carrier 0 collisions 0 docker0: flags=4355<UP,BROADCAST,PROMISC,MULTICAST> mtu 1500 inet 172.17.0.1 netmask 255.255.0.0 broadcast 172.17.255.255 ether 02:42:f7:e2:f2:17 txqueuelen 0 (Ethernet) RX packets 0 bytes 0 (0.0 B) RX errors 0 dropped 0 overruns 0 frame 0 TX packets 0 bytes 0 (0.0 B) TX errors 0 dropped 0 overruns 0 carrier 0 collisions 0 eth0: flags=4419<UP,BROADCAST,RUNNING,PROMISC,MULTICAST> mtu 1500 inet 172.31.6.15 netmask 255.255.240.0 broadcast 172.31.15.255 inet6 fe80::bf:52ff:fe4a:fe3c prefixlen 64 scopeid 0x20<link> ether 02:bf:52:4a:fe:3c txqueuelen 1000 (Ethernet) RX packets 7111658 bytes 9681867004 (9.6 GB) RX errors 0 dropped 0 overruns 0 frame 0 TX packets 2255773 bytes 398129876 (398.1 MB) TX errors 0 dropped 0 overruns 0 carrier 0 collisions 0 lo: flags=73<UP,LOOPBACK,RUNNING> mtu 65536 inet 127.0.0.1 netmask 255.0.0.0 inet6 ::1 prefixlen 128 scopeid 0x10<host> loop txqueuelen 1000 (Local Loopback) RX packets 372613 bytes 46260682 (46.2 MB) RX errors 0 dropped 0 overruns 0 frame 0 TX packets 372613 bytes 46260682 (46.2 MB) TX errors 0 dropped 0 overruns 0 carrier 0 collisions 0 What OS is this ?> Ubuntun 18.04What version of Samba ? Can you post the contents of the following files: /etc/resolv.conf> search transmitcorp.comnameserver 127.0.0.1 options edns0 /etc/hostname 127.0.0.1 localhost php7.localhost adc1 120.0.0.1 php7.localhost 172.31.6.15 adc1 # The following lines are desirable for IPv6 capable hosts ::1 ip6-localhost ip6-loopback fe00::0 ip6-localnet ff00::0 ip6-mcastprefix ff02::1 ip6-allnodes ff02::2 ip6-allrouters ff02::3 ip6-allhosts /etc/hosts>search transmitcorp.com nameserver 127.0.0.1 options edns0 /etc/samba/smb.conf (or wherever smb.conf is on your DC)> # Global parameters[global] dns forwarder = 8.8.8.8 netbios name = ADC1 realm = TRANSMITCORP.COM server role = active directory domain controller workgroup = TRANSMITCORP idmap_ldb:use rfc2307 = yes [netlogon] path = /var/lib/samba/sysvol/transmitcorp.com/scripts read only = No [sysvol] path = /var/lib/samba/sysvol read only = No Rowland Lionel -- To unsubscribe from this list go to the following URL and read the instructions: https://lists.samba.org/mailman/options/samba
Rowland penny
2020-Feb-27 13:48 UTC
[Samba] Samba AD - Different IP than the existing one assigned
On 27/02/2020 13:25, Lionel Monchecourt via samba wrote:> Hi, Thanks for helping. > > Answers in line : > > > > Log.smbd : > [2020/02/24 10:02:22.602083, 0] ../source3/smbd/server.c:1815(main) > server role = 'active directory domain controller' not compatible with running smbd standalone. > You should start 'samba' instead, and it will control starting smbd if requiredReally big hint there, you are not starting 'samba-ad-dc', you seem to be starting the individual Samba binaries> Nothing is running on port 53 :There wouldn't be, the 'samba' binary isn't starting.> Now, when I performed a check for the adc1, I get an answer BUT ,the IP is > not the one of the machine > > A DC should have a fixed IP and that is what Samba should use. > >> yes ok : 172.31.6.15 >> >> >> Do you have more than one ethernet device ? >> >> Yes , here are the different devices, but none is matching this strange IPThis is strange, but possibly related to the DC not running.> What OS is this ? > >> Ubuntun 18.04 > Can you post the contents of the following files: > > /etc/resolv.conf > >> search transmitcorp.com >> >> nameserver 127.0.0.1 >> >> options edns0Do not use '127.0.0.1', use the computers ipaddress>> /etc/hostname >> >> 127.0.0.1 localhost php7.localhost adc1 >> >> 120.0.0.1 php7.localhost >> >> 172.31.6.15 adc1No, /etc/hostname should just contain the computers short hostname 'adc1'>> /etc/hosts >> >> search transmitcorp.com >> >> nameserver 127.0.0.1 >> >> options edns0Have you mixed up your files ? I would have expected /etc/hosts to look like this: 127.0.0.1 localhost 172.31.6.15 adc1.transmitcorp.com adc1 Rowland
L.P.H. van Belle
2020-Feb-27 14:07 UTC
[Samba] Samba AD - Different IP than the existing one assigned
Run the debug script and we know all we need to know.
https://github.com/thctlo/samba4/raw/master/samba-collect-debug-info.sh
There is more here going on then only the hosts files..
Also like :
systemctl stop smbd nmbd winbind
systemctl disable smbd nmbd winbind
systemctl mask smbd nmbd winbind
systemctl unmask samba-ad-dc
systemctl enable samba-ad-dc
systemctl start samba-ad-dc
This was ubuntu 18.04 correct? .. Ah.. run script we know. ;-)
Greetz,
Louis
> -----Oorspronkelijk bericht-----
> Van: samba [mailto:samba-bounces at lists.samba.org] Namens
> Rowland penny via samba
> Verzonden: donderdag 27 februari 2020 14:49
> Aan: samba at lists.samba.org
> Onderwerp: Re: [Samba] Samba AD - Different IP than the
> existing one assigned
>
> On 27/02/2020 13:25, Lionel Monchecourt via samba wrote:
> > Hi, Thanks for helping.
> >
> > Answers in line :
> >
> >
> >
> > Log.smbd :
> > [2020/02/24 10:02:22.602083, 0] ../source3/smbd/server.c:1815(main)
> > server role = 'active directory domain controller' not
> compatible with running smbd standalone.
> > You should start 'samba' instead, and it will control
> starting smbd if required
> Really big hint there, you are not starting 'samba-ad-dc',
> you seem to
> be starting the individual Samba binaries
> > Nothing is running on port 53 :
> There wouldn't be, the 'samba' binary isn't starting.
> > Now, when I performed a check for the adc1, I get an answer
> BUT ,the IP is
> > not the one of the machine
> >
> > A DC should have a fixed IP and that is what Samba should use.
> >
> >> yes ok : 172.31.6.15
> >>
> >>
> >> Do you have more than one ethernet device ?
> >>
> >> Yes , here are the different devices, but none is matching
> this strange IP
> This is strange, but possibly related to the DC not running.
> > What OS is this ?
> >
> >> Ubuntun 18.04
> > Can you post the contents of the following files:
> >
> > /etc/resolv.conf
> >
> >> search transmitcorp.com
> >>
> >> nameserver 127.0.0.1
> >>
> >> options edns0
> Do not use '127.0.0.1', use the computers ipaddress
> >> /etc/hostname
> >>
> >> 127.0.0.1 localhost php7.localhost adc1
> >>
> >> 120.0.0.1 php7.localhost
> >>
> >> 172.31.6.15 adc1
> No, /etc/hostname should just contain the computers short
> hostname 'adc1'
> >> /etc/hosts
> >>
> >> search transmitcorp.com
> >>
> >> nameserver 127.0.0.1
> >>
> >> options edns0
>
> Have you mixed up your files ? I would have expected
> /etc/hosts to look
> like this:
>
> 127.0.0.1 localhost
>
> 172.31.6.15 adc1.transmitcorp.com adc1
>
> Rowland
>
>
>
> --
> To unsubscribe from this list go to the following URL and read the
> instructions: https://lists.samba.org/mailman/options/samba
>
>
Lionel Monchecourt
2020-Feb-27 14:27 UTC
[Samba] Samba AD - Different IP than the existing one assigned
Hi, Thanks for helping. Answers in line : Log.smbd : [2020/02/24 10:02:22.602083, 0] ../source3/smbd/server.c:1815(main) server role = 'active directory domain controller' not compatible with running smbd standalone. You should start 'samba' instead, and it will control starting smbd if required Really big hint there, you are not starting 'samba-ad-dc', you seem to be starting the individual Samba binaries> This is what I?m starting :service samba-ad-dc start Nothing is running on port 53 : There wouldn't be, the 'samba' binary isn't starting. Now, when I performed a check for the adc1, I get an answer BUT ,the IP is not the one of the machine A DC should have a fixed IP and that is what Samba should use. yes ok : 172.31.6.15 Do you have more than one ethernet device ? Yes , here are the different devices, but none is matching this strange IP This is strange, but possibly related to the DC not running. What OS is this ? Ubuntun 18.04 Can you post the contents of the following files: /etc/resolv.conf search transmitcorp.com nameserver 127.0.0.1 options edns0 Do not use '127.0.0.1', use the computers ipaddress> ok , changed it to l72.31.6.15/etc/hostname 127.0.0.1 localhost php7.localhost adc1 120.0.0.1 php7.localhost 172.31.6.15 adc1 No, /etc/hostname should just contain the computers short hostname 'adc1'> yes, bad copy/paste sorryroot at TransmitCorp/etc/samba# more /etc/hostname adc1 /etc/hosts search transmitcorp.com nameserver 127.0.0.1 options edns0 Have you mixed up your files ? I would have expected /etc/hosts to look like this: 127.0.0.1 localhost 172.31.6.15 adc1.transmitcorp.com adc1 Yes sorry, /etc/hosts 127.0.0.1 localhost php7.localhost adc1 120.0.0.1 php7.localhost 172.31.6.15 adc1 # The following lines are desirable for IPv6 capable hosts ::1 ip6-localhost ip6-loopback fe00::0 ip6-localnet ff00::0 ip6-mcastprefix ff02::1 ip6-allnodes ff02::2 ip6-allrouters ff02::3 ip6-allhosts Rowland -- To unsubscribe from this list go to the following URL and read the instructions: https://lists.samba.org/mailman/options/samba
Lionel Monchecourt
2020-Feb-27 14:31 UTC
[Samba] Samba AD - Different IP than the existing one assigned
Hi Louis
Here we go for the output of the script
Collected config --- 2020-02-27-14:28 -----------
Hostname: adc1
DNS Domain:
FQDN: localhost
ipaddress: 172.31.6.15 172.17.0.1 172.18.0.1 172.19.0.1
-----------
Kerberos SRV _kerberos._tcp. record verified ok, sample output:
Server: 172.31.6.15
Address: 172.31.6.15#53
Non-authoritative answer:
*** Can't find _kerberos._tcp.: No answer
Authoritative answers can be found from:
.
origin = a.root-servers.net
mail addr = nstld.verisign-grs.com
serial = 2020022700
refresh = 1800
retry = 900
expire = 604800
minimum = 86400
From: Lionel Monchecourt [mailto:lionel.monchecourt at free.fr]
Sent: 27 February 2020 15:21
To: lionel Monchecourt
Subject: Fwd: [Samba] Samba AD - Different IP than the existing one assigned
Lionel
sent from my Iphone, sorry for typo
D?but du message transf?r? :
Exp?diteur: Rowland penny via samba <samba at lists.samba.org>
Date: 27 f?vrier 2020 ? 14:50:27 UTC+1
Destinataire: samba at lists.samba.org
Objet: R?p: [Samba] Samba AD - Different IP than the existing one assigned
R?pondre ?: Rowland penny <rpenny at samba.org>
?On 27/02/2020 13:25, Lionel Monchecourt via samba wrote:
Hi, Thanks for helping.
Answers in line :
Log.smbd :
[2020/02/24 10:02:22.602083, 0] ../source3/smbd/server.c:1815(main)
server role = 'active directory domain controller' not compatible with
running smbd standalone.
You should start 'samba' instead, and it will control starting smbd if
required
Really big hint there, you are not starting 'samba-ad-dc', you seem to
be starting the individual Samba binaries
Nothing is running on port 53 :
There wouldn't be, the 'samba' binary isn't starting.
Now, when I performed a check for the adc1, I get an answer BUT ,the IP is
not the one of the machine
A DC should have a fixed IP and that is what Samba should use.
yes ok : 172.31.6.15
Do you have more than one ethernet device ?
Yes , here are the different devices, but none is matching this strange IP
This is strange, but possibly related to the DC not running.
What OS is this ?
Ubuntun 18.04
Can you post the contents of the following files:
/etc/resolv.conf
search transmitcorp.com
nameserver 127.0.0.1
options edns0
Do not use '127.0.0.1', use the computers ipaddress
/etc/hostname
127.0.0.1 localhost php7.localhost adc1
120.0.0.1 php7.localhost
172.31.6.15 adc1
No, /etc/hostname should just contain the computers short hostname
'adc1'
/etc/hosts
search transmitcorp.com
nameserver 127.0.0.1
options edns0
Have you mixed up your files ? I would have expected /etc/hosts to look like
this:
127.0.0.1 localhost
172.31.6.15 adc1.transmitcorp.com adc1
Rowland
--
To unsubscribe from this list go to the following URL and read the
instructions: https://lists.samba.org/mailman/options/samba
Rowland penny
2020-Feb-27 14:39 UTC
[Samba] Samba AD - Different IP than the existing one assigned
On 27/02/2020 14:27, Lionel Monchecourt via samba wrote:>> This is what I?m starting :Then you haven't stopped Ubuntu from starting smbd, nmbd and winbind>> Ubuntun 18.04Please go and read this: https://github.com/thctlo/samba4/blob/master/full-howto-Ubuntu18.04-samba-AD_DC.txt Rowland
L.P.H. van Belle
2020-Feb-27 14:53 UTC
[Samba] Samba AD - Different IP than the existing one assigned
.. I almost mailed the same.. So i'll add a bit more to this. Short resume. Now you talk about "strange" devices. You have 1 eth0, the real interface 2 briding interfaces. 1 docker interface. Before you proceed, you should know more about this. /etc/hosts is wrong /etc/resolv.conf is wrong. /etc/hostname is empty. This is the base of most of you current problems. Per example. /etc/hosts 127.0.0.1 localhost php7 172.31.6.15 adc1.transmitcorp.com adc1 # IF you really need php7, but you can only use it internaly on the server itself, like this. # Note even if you add php7 to the adc1.transmitcorp.com line. # Or you would need to add both. php7.transmitcorp.com php7 # The following lines are desirable for IPv6 capable hosts ::1 localhost ip6-localhost ip6-loopback ff02::1 ip6-allnodes ff02::2 ip6-allrouters /etc/resolv.conf search transmitcorp.com nameserver 172.31.6.15 options edns0 /etc/hostsname adc1 Reboot and rerun the script. Anonimize it and show the full output. Greetz, Louis> -----Oorspronkelijk bericht----- > Van: samba [mailto:samba-bounces at lists.samba.org] Namens > Rowland penny via samba > Verzonden: donderdag 27 februari 2020 15:40 > Aan: samba at lists.samba.org > Onderwerp: Re: [Samba] Samba AD - Different IP than the > existing one assigned > > On 27/02/2020 14:27, Lionel Monchecourt via samba wrote: > >> This is what I?m starting : > Then you haven't stopped Ubuntu from starting smbd, nmbd and winbind > >> Ubuntun 18.04 > > Please go and read this: > > https://github.com/thctlo/samba4/blob/master/full-howto-Ubuntu18.04-samba-AD_DC.txt> > Rowland > > -- > To unsubscribe from this list go to the following URL and read the > instructions: https://lists.samba.org/mailman/options/samba > >
Lionel Monchecourt
2020-Feb-27 15:34 UTC
[Samba] Samba AD - Different IP than the existing one assigned
J?en ai profit? pour desactive VPN et autre.
Du coup, je n?ai que :
root at TransmitCorp~# ifconfig -a
eth0: flags=4163<UP,BROADCAST,RUNNING,MULTICAST> mtu 9001
inet 172.31.6.15 netmask 255.255.240.0 broadcast 172.31.15.255
inet6 fe80::bf:52ff:fe4a:fe3c prefixlen 64 scopeid 0x20<link>
ether 02:bf:52:4a:fe:3c txqueuelen 1000 (Ethernet)
RX packets 3542 bytes 1140588 (1.1 MB)
RX errors 0 dropped 0 overruns 0 frame 0
TX packets 3222 bytes 585973 (585.9 KB)
TX errors 0 dropped 0 overruns 0 carrier 0 collisions 0
lo: flags=73<UP,LOOPBACK,RUNNING> mtu 65536
inet 127.0.0.1 netmask 255.0.0.0
inet6 ::1 prefixlen 128 scopeid 0x10<host>
loop txqueuelen 1000 (Local Loopback)
RX packets 685 bytes 85847 (85.8 KB)
RX errors 0 dropped 0 overruns 0 frame 0
TX packets 685 bytes 85847 (85.8 KB)
TX errors 0 dropped 0 overruns 0 carrier 0 collisions 0
Contenu du /etc/hosts
127.0.0.1 localhost
172.31.6.15 adc1 adc1.transmitcorp.com
Contenu du /etc/resolv.conf
search transmitcorp.com
nameserver 172.31.6.15
options edns0
script de test :
root at TransmitCorp~# sh samba-collect-debug-info.sh
samba-collect-debug-info.sh: 15: [: Illegal number:
Please wait, collecting debug info.
root at TransmitCorp~# more /tmp/samba-debug-info.txt
Collected config --- 2020-02-27-15:28 -----------
Hostname: adc1
DNS Domain:
FQDN: adc1
ipaddress: 172.31.6.15
-----------
WARNING: kinit Administrator will fail and this needs to be fixed first.
unable to verify DNS kerberos._tcp SRV records
Server: 172.31.6.15
Address: 172.31.6.15#53
** server can't find _kerberos._tcp: NXDOMAIN
Le
Host -t A transmitcorp.com qui marchait avant ne marche plus
Status du service :
ot at TransmitCorp~# service samba-ad-dc status
? samba-ad-dc.service - Samba AD Daemon
Loaded: loaded (/lib/systemd/system/samba-ad-dc.service; enabled; vendor
preset: enabled)
Active: failed (Result: exit-code) since Thu 2020-02-27 15:23:34 UTC; 9min
ago
Docs: man:samba(8)
man:samba(7)
man:smb.conf(5)
Process: 897 ExecStart=/usr/sbin/samba --foreground --no-process-group
$SAMBAOPTIONS (code=exited, status=1/FAILURE)
Main PID: 897 (code=exited, status=1/FAILURE)
Feb 27 15:23:33 adc1 samba[1737]: task[dns][1737]: Failed to bind to
0.0.0.0:53 TCP - NT_STATUS_ADDRESS_ALREADY_ASSOCIATED
Feb 27 15:23:33 adc1 samba[1737]: task[dns][1737]: [2020/02/27 15:23:33.910256,
0] ../source4/smbd/service_task.c:36(task_server_terminate)
Feb 27 15:23:33 adc1 samba[1737]: task[dns][1737]: task_server_terminate:
task_server_terminate: [dns failed to setup interfaces]
Feb 27 15:23:33 adc1 samba[897]: root process[897]: [2020/02/27 15:23:33.915968,
0] ../source4/smbd/server.c:288(samba_terminate)
Feb 27 15:23:33 adc1 samba[897]: root process[897]: samba_terminate:
samba_terminate of samba 897: dns failed to setup interfaces
Feb 27 15:23:34 adc1 systemd[1]: samba-ad-dc.service: Main process exited,
code=exited, status=1/FAILURE
Feb 27 15:23:34 adc1 samba[1724]: task[ldapsrv][1724]: [2020/02/27
15:23:34.684245, 0]
../source4/smbd/process_standard.c:81(sigterm_signal_handler)
Feb 27 15:23:34 adc1 samba[1724]: task[ldapsrv][1724]: sigterm_signal_handler:
Exiting pid 1724 on SIGTERM
Feb 27 15:23:34 adc1 systemd[1]: samba-ad-dc.service: Failed with result
'exit-code'.
Feb 27 15:23:34 adc1 systemd[1]: Failed to start Samba AD Daemon.
root at TransmitCorp~#
merci
Seemingly Similar Threads
- Samba AD - Different IP than the existing one assigned
- Samba AD - Different IP than the existing one assigned
- Samba AD - Different IP than the existing one assigned
- Samba AD - Different IP than the existing one assigned
- Samba AD - Different IP than the existing one assigned