Domaincontroller with Samba AD - activation fails

ka.rot · February 22, 2017, 5:27pm

NethServer Version: your_version nethserver-7.2.1511-alpha3-x86_64
Module: your_module Account Provider Samba Active Directory

After Trying to activate the Domain Controller via WEB-Interface I get subsequent errors:
Task completed with errors
S95nethserver-dc-waitstart #5 (exit status 256)
S96nethserver-dc-join #6 (exit status 256)
S97nethserver-dc-password-policy #7 (exit status 768)
S98nethserver-dc-createadmins #8 (exit status 768)
Template /var/lib/machines/nsdc/etc/sysconfig/samba-provision #102 (exit status 1)
expansion of /var/lib/machines/nsdc/etc/sysconfig/samba-provision failed

In /var/log/messages I get the following information
Feb 22 15:19:57 i7quad kernel: IPv4: martian source 192.168.201.141 from 192.168.201.128, on dev br0
Feb 22 15:19:57 i7quad kernel: ll header: 00000000: ff ff ff ff ff ff 08 00 27 9f 97 2e 08 06 …’…
Feb 22 15:19:57 i7quad kernel: br0: received packet on enp0s3 with own address as source address
Feb 22 15:19:57 i7quad kernel: br0: received packet on enp0s3 with own address as source address
Feb 22 15:19:58 i7quad kernel: br0: received packet on enp0s3 with own address as source address
Feb 22 15:19:58 i7quad kernel: IPv4: martian source 192.168.201.141 from 192.168.201.128, on dev br0
Feb 22 15:19:58 i7quad kernel: ll header: 00000000: ff ff ff ff ff ff 08 00 27 9f 97 2e 08 06 …’…
Feb 22 15:20:01 i7quad kernel: br0: received packet on enp0s3 with own address as source address
Feb 22 15:20:01 i7quad kernel: br0: received packet on enp0s3 with own address as source address
Feb 22 15:20:02 i7quad kernel: br0: received packet on enp0s3 with own address as source address
Feb 22 15:20:06 i7quad kernel: br0: received packet on enp0s3 with own address as source address
Feb 22 15:20:06 i7quad kernel: br0: received packet on enp0s3 with own address as source address
Feb 22 15:20:06 i7quad esmith::event[1714]: [ERROR] could not connect to Samba Domain Controller
Feb 22 15:20:06 i7quad esmith::event[1714]: Action: /etc/e-smith/events/nethserver-dc-save/S95nethserver-dc-waitstart FAILED: 1 [1201.073592]

Additional Information see screenshot-uploads

fasttech · February 22, 2017, 6:07pm

I’m not an expert, if it was me, based on your error and the limited information you’ve posted, I would use an fqdn of i7quad.samba.local. To change that would require you to either use the nethserver samba reset procedure or start over with your, I’m guessing from the looks of your setup, test install, I would post or link to the reset, but now I can’t find it.

ok, ‘factory reset’;
http://docs.nethserver.org/projects/nethserver-devel/en/v7/nethserver-dc.html#factory-reset

giacomo · February 23, 2017, 8:14am

I also see a problem in your network configuration: it seems you have two active interfaces with the same IP address.

My advice: fix the network configuration by creating a bridge on the green interface, than follow documentation pointed out by @fasttech.

ka.rot · February 27, 2017, 6:56pm

Hello Giacomo,

Thank you for your quick response. I have been busy since then in trying to improve with my objective. I failed to reset according to the nethserver samba reset procedure as indicated by fasttech. I found differences in directory structure, directory names, file names etc in my system compared with the document given. Therefore I redid everything from scratch several times, changing domain names etc. But it ended up always with the same errors as shown hereafter.

Sorry for using mail as communication means. That was more flexible and more convenient to handle.

Given a solution will become available, I am prepared to describe this publicly for the Nethserver community.

Many regards

Karl

1 Creation of Virtual Machine for Nethserver with Virtual Box

Create Virtual Machine

Name: Nethserver 3

Typ : Linux

Version Red Hat (64 bit)

Memory Size: 1024MB

Create Hard Disk

Controller: Nethserver 7.2.1511-alpha3-x86_64

Controller SATA: Nethserver. vdihost

Network: Adapter 1 only, Networkbridge, Raltek RTL8168, Type Intel PRO/1q000 MT, MAC-Address: 0800279F972E

2 Configuration of Nethserver

Host name. server3.samba.local

IP Address of Nethserver: 192.168.201.109/24

Dashboard of Nethserver shows one Interface enp0s3Dashboard of Nethserver

3 Software configuration and Updates

Packages: Account Provider Samba Active directory, Basic Firewall, Fileserver

Updates: Installed Software is up to date.

Configuration of Account provider: IP Address 192.168.201.141, Create Network Bridge, LOCALDOMAIN (given by the System and could not be changed)

4 DC failure

5 Some additional information (config show nsdc, ifconfig, /var/log/messages)

[root@server3 ~]# config show nsdc

nsdc=service

IpAddress=192.168.201.141

bridge=br0

status=enabled

[root@server3 ~]#

[root@server3 ~]# ifconfig

br0: flags=4163<UP,BROADCAST,RUNNING,MULTICAST> mtu 1500

    inet 192.168.201.109  netmask 255.255.255.0  broadcast 192.168.201.255

    inet6 fe80::a00:27ff:febd:23fa  prefixlen 64  scopeid 0x20<link>

    ether 08:00:27:bd:23:fa  txqueuelen 1000  (Ethernet)

   RX packets 544  bytes 72895 (71.1 KiB)

    RX errors 0  dropped 0  overruns 0  frame 0

    TX packets 112  bytes 13905 (13.5 KiB)

    TX errors 0  dropped 0 overruns 0  carrier 0  collisions 0

enp0s3: flags=4163<UP,BROADCAST,RUNNING,MULTICAST> mtu 1500

    inet6 fe80::a00:27ff:febd:23fa  prefixlen 64  scopeid 0x20<link>

    ether 08:00:27:bd:23:fa  txqueuelen 1000  (Ethernet)

    RX packets 1175  bytes 216156 (211.0 KiB)

    RX errors 0  dropped 0  overruns 0  frame 0

    TX packets 121  bytes 16693 (16.3 KiB)

    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 1  (Local Loopback)

    RX packets 70  bytes 4820 (4.7 KiB)

    RX errors 0  dropped 0  overruns 0  frame 0

    TX packets 70  bytes 4820 (4.7 KiB)

    TX errors 0  dropped 0 overruns 0  carrier 0  collisions 0

[root@server3 ~]# ^C

Parts of /var/log/messages

First significant part:

eb 26 17:40:08 server3 network: Bringing up interface enp0s3:

Feb 26 17:40:08 server3 kernel: IPv6: ADDRCONF(NETDEV_UP): enp0s3: link is not ready

Feb 26 17:40:08 server3 kernel: e1000: enp0s3 NIC Link is Up 1000 Mbps Full Duplex, Flow Control: RX

Feb 26 17:40:08 server3 kernel: IPv6: ADDRCONF(NETDEV_CHANGE): enp0s3: link becomes ready

Feb 26 17:40:08 server3 dhclient[751]: DHCPDISCOVER on enp0s3 to 255.255.255.255 port 67 interval 7 (xid=0x690b7ebd)

Feb 26 17:40:09 server3 kernel: IPv6: enp0s3: IPv6 duplicate address fe80::a00:27ff:febd:23fa detected!

Feb 26 17:40:09 server3 dhclient[751]: DHCPREQUEST on enp0s3 to 255.255.255.255 port 67 (xid=0x690b7ebd)

Feb 26 17:40:09 server3 dhclient[751]: DHCPOFFER from 192.168.201.1

Feb 26 17:40:09 server3 dhclient[751]: DHCPACK from 192.168.201.1 (xid=0x690b7ebd)

Feb 26 17:40:11 server3 NET[800]: /usr/sbin/dhclient-script : updated /etc/resolv.conf

Feb 26 17:40:11 server3 dhclient[751]: bound to 192.168.201.109 – renewal in 363055 seconds.

Feb 26 17:40:11 server3 network: Determining IP information for enp0s3… done.

Feb 26 17:40:12 server3 NET[881]: /etc/sysconfig/network-scripts/ifup-post : updated /etc/resolv.conf

Feb 26 17:40:12 server3 network: [ OK ]

Part 2

Feb 26 20:07:36 server3 kernel: ll header: 00000000: ff ff ff ff ff ff 08 00 27 bd 23 fa 08 06 …’.#…

Feb 26 20:07:36 server3 kernel: br0: received packet on enp0s3 with own address as source address

Feb 26 20:07:37 server3 kernel: br0: received packet on enp0s3 with own address as source address

Feb 26 20:07:37 server3 kernel: IPv4: martian source 192.168.201.141 from 192.168.201.109, on dev br0

Feb 26 20:07:37 server3 kernel: ll header: 00000000: ff ff ff ff ff ff 08 00 27 bd 23 fa 08 06 …’.#…

Feb 26 20:07:41 server3 kernel: br0: received packet on enp0s3 with own address as source address

Feb 26 20:07:45 server3 kernel: br0: received packet on enp0s3 with own address as source address

Feb 26 20:07:45 server3 journal: Suppressed 2443 messages from /system.slice/httpd-admin.service

Feb 26 20:07:45 server3 esmith::event[7067]: [ERROR] could not connect to Samba Domain Controller

Feb 26 20:07:45 server3 esmith::event[7067]: Action: /etc/e-smith/events/nethserver-dc-save/S95nethserver-dc-waitstart FAILED: 1 [1201.17001]

Feb 26 20:07:45 server3 kernel: br0: received packet on enp0s3 with own address as source address

Feb 26 20:07:45 server3 /sbin/e-smith/db[23163]: /var/lib/nethserver/db/configuration: OLD sssd=service|AdDns||LdapURI||Provider|none|status|disabled

Feb 26 20:07:45 server3 /sbin/e-smith/db[23163]: /var/lib/nethserver/db/configuration: NEW sssd=service|AdDns|192.168.201.141|LdapURI||Provider|none|status|disabled

Feb 26 20:07:45 server3 dbus[585]: [system] Activating via systemd: service name=‘org.freedesktop.timedate1’ unit=‘dbus-org.freedesktop.timedate1.service’

Feb 26 20:07:45 server3 dbus-daemon: dbus[585]: [system] Activating via systemd: service name=‘org.freedesktop.timedate1’ unit=‘dbus-org.freedesktop.timedate1.service’

Feb 26 20:07:45 server3 systemd: Cannot add dependency job for unit microcode.service, ignoring: Unit is not loaded properly: Invalid argument.

Part 3

07 server3 esmith::event[7067]: Invalid argument

Feb 26 20:09:07 server3 esmith::event[7067]: Failed to create bus connection: Host is down

Feb 26 20:09:07 server3 esmith::event[7067]: [ERROR] User admin creation failed

Feb 26 20:09:07 server3 esmith::event[7067]: Action: /etc/e-smith/events/nethserver-dc-save/S98nethserver-dc-createadmins FAILED: 3 [21.094766]

Feb 26 20:09:07 server3 esmith::event[7067]: Event: nethserver-dc-save FAILED

Feb 26 20:09:07 server3 kernel: net_ratelimit: 1 callbacks suppressed

Feb 26 20:09:07 server3 kernel: br0: received packet on enp0s3 with own address as source address

Feb 26 20:09:07 server3 kernel: IPv4: martian source 192.168.201.141 from 192.168.201.109, on dev br0

Feb 26 20:09:07 server3 kernel: ll header: 00000000: ff ff ff ff ff ff 08 00 27 bd 23 fa 08 06 …’.#…

Feb 26 20:09:08 server3 kernel: br0: received packet on enp0s3 with own address as source address

Feb 26 20:09:08 server3 kernel: IPv4: martian source 192.168.201.141 from 192.168.201.109, on dev br0

Feb 26 20:09:08 server3 kernel: ll header: 00000000: ff ff ff ff ff ff 08 00 27 bd 23 fa 08 06 …’.#…

Feb 26 20:09:09 server3 kernel: br0: received packet on enp0s3 with own address as source address

dj_marian · February 27, 2017, 7:42pm

Hi, i also had problems with samba so i propose:
-remove br0 fom interfaces
-check that you have only one DHCP server in 192.168.201.0/24 network and put nethserver and samba address outside the dhcp pool
-set static addres on nethserver interface
-set FQDN at least two parts, but three are better eg. yourhostname.yourdomain.local, for testing would be ok, then your NetBIOS name would be YOURDOMAIN,
if not only for testing think about yourhostname.localsubdomain.yourdomain.com, then your NetBIOS name would be LOCALSUBDOMAIN,
-folow “factory reset” procedure

-start provisioning procedure from the beginning (take samba addres distinct from nethserver addres, chose “create bridge…” option.

I hope it helps. Cheers

ka.rot · March 3, 2017, 8:30am

Hello dj-marian, hello Giacomo and hello at fasttech quality team,

you all have been great and very helpful to my activity. I have finally succeeded. Essential for the success has probably been:

setting the name to server3.samba.local
setting the server address to static and outside the dhcp addressrange of my network
setting the address of the samba Linux container to a value different from the host address
I am lucky, that with your help, I could achieve this.good result.
Many regards
Karl

davidep · March 3, 2017, 8:35am

Good work! Thank you all!

Please, @ka.rot mark this topic solved!

alefattorini · March 3, 2017, 11:10am

Good to know man! Thanks for showing us your appreciation @fasttech @dj_marian