BTW, where did the file-server go to?
Itâs on my workbench: it will be released soon
Hi guys,
i set up a NS7A3 VM for test and installed Samba AD as discribed above.
I tried to join a win7 machine to this domain, but got a message, that the domain was identified as ânsdc-test.ns7a3.atâ, but however it could not connect to domain controllers.
What did i do wrong?
Make sure your machine is using NS as DNS.
Then, when request the domain for the join, enter âns7a3.atâ.
@giacomo thanks for answering, i did that. the machine is configured with this vm as gateway and dns-server.
You should check the logs and report here your findings:
- journalctl -M nsdc
- less /var/log/messages
journalctl -M nsdc:
-- Logs begin at Tue 2016-05-24 11:17:54 CEST, end at Tue 2016-05-24 13:31:02 CEST. --
May 24 11:17:54 nsdc-test.ns7a3.at systemd-journal[14]: Runtime journal is using 8.0M (max allowed 91.9M, trying to leave 137.9M free of 911.9M available â current limit 91.9M).
May 24 11:17:55 nsdc-test.ns7a3.at systemd-journal[14]: Permanent journal is using 8.0M (max allowed 1.7G, trying to leave 2.6G free of 15.1G available â current limit 1.7G).
May 24 11:17:55 nsdc-test.ns7a3.at systemd-journal[14]: Time spent on flushing to /var is 1.084ms for 2 entries.
May 24 11:17:55 nsdc-test.ns7a3.at systemd-journal[14]: Journal started
May 24 11:17:55 nsdc-test.ns7a3.at systemd[1]: Starting Flush Journal to Persistent Storage...
May 24 11:17:56 nsdc-test.ns7a3.at systemd[1]: Started Flush Journal to Persistent Storage.
May 24 11:17:56 nsdc-test.ns7a3.at systemd[1]: Starting Create Volatile Files and Directories...
May 24 11:17:56 nsdc-test.ns7a3.at systemd[1]: Started Create Volatile Files and Directories.
May 24 11:17:56 nsdc-test.ns7a3.at systemd[1]: Starting Update UTMP about System Boot/Shutdown...
May 24 11:17:56 nsdc-test.ns7a3.at systemd[1]: Started Update UTMP about System Boot/Shutdown.
May 24 11:17:56 nsdc-test.ns7a3.at systemd[1]: Reached target System Initialization.
May 24 11:17:56 nsdc-test.ns7a3.at systemd[1]: Starting System Initialization.
May 24 11:17:56 nsdc-test.ns7a3.at systemd[1]: Started Daily Cleanup of Temporary Directories.
May 24 11:17:56 nsdc-test.ns7a3.at systemd[1]: Starting Daily Cleanup of Temporary Directories.
May 24 11:17:56 nsdc-test.ns7a3.at systemd[1]: Reached target Timers.
May 24 11:17:56 nsdc-test.ns7a3.at systemd[1]: Starting Timers.
May 24 11:17:56 nsdc-test.ns7a3.at systemd[1]: Listening on D-Bus System Message Bus Socket.
May 24 11:17:56 nsdc-test.ns7a3.at systemd[1]: Starting D-Bus System Message Bus Socket.
May 24 11:17:56 nsdc-test.ns7a3.at systemd[1]: Reached target Sockets.
May 24 11:17:56 nsdc-test.ns7a3.at systemd[1]: Starting Sockets.
May 24 11:17:56 nsdc-test.ns7a3.at systemd[1]: Reached target Basic System.
May 24 11:17:56 nsdc-test.ns7a3.at systemd[1]: Starting Basic System.
May 24 11:17:56 nsdc-test.ns7a3.at systemd[1]: Started D-Bus System Message Bus.
May 24 11:17:56 nsdc-test.ns7a3.at systemd[1]: Starting D-Bus System Message Bus...
May 24 11:17:56 nsdc-test.ns7a3.at systemd[1]: Starting Network Service...
May 24 11:17:56 nsdc-test.ns7a3.at systemd[1]: Starting Domain controller provisioning...
May 24 11:17:56 nsdc-test.ns7a3.at systemd[1]: Starting Permit User Sessions...
May 24 11:17:56 nsdc-test.ns7a3.at systemd[1]: Starting Login Service...
May 24 11:17:56 nsdc-test.ns7a3.at systemd[1]: Starting Cleanup of Temporary Directories...
May 24 11:17:56 nsdc-test.ns7a3.at systemd-networkd[24]: host0 : Cannot configure IPv4 forwarding for interface host0: Read-only file system
May 24 11:17:56 nsdc-test.ns7a3.at systemd-networkd[24]: host0 : Cannot configure IPv6 forwarding for interface: Read-only file system
May 24 11:17:56 nsdc-test.ns7a3.at systemd-networkd[24]: Enumeration completed
May 24 11:17:56 nsdc-test.ns7a3.at systemd-networkd[24]: host0 : link configured
May 24 11:17:56 nsdc-test.ns7a3.at systemd[1]: Started Network Service.
May 24 11:17:56 nsdc-test.ns7a3.at systemd[1]: Reached target Network.
May 24 11:17:56 nsdc-test.ns7a3.at systemd[1]: Starting Network.
May 24 11:17:56 nsdc-test.ns7a3.at systemd[1]: Started Cleanup of Temporary Directories.
May 24 11:17:56 nsdc-test.ns7a3.at systemd[1]: Started Permit User Sessions.
May 24 11:17:56 nsdc-test.ns7a3.at systemd[1]: Started Console Getty.
May 24 11:17:56 nsdc-test.ns7a3.at systemd[1]: Starting Console Getty...
May 24 11:17:56 nsdc-test.ns7a3.at systemd[1]: Started Getty on tty1.
May 24 11:17:56 nsdc-test.ns7a3.at systemd[1]: Reached target Login Prompts.
May 24 11:17:56 nsdc-test.ns7a3.at systemd[1]: Starting Login Prompts.
May 24 11:17:56 nsdc-test.ns7a3.at systemd-networkd[24]: host0 : gained carrier
May 24 11:17:56 nsdc-test.ns7a3.at systemd[1]: Started Login Service.
May 24 11:17:56 nsdc-test.ns7a3.at systemd-logind[27]: New seat seat0.
May 24 11:17:56 nsdc-test.ns7a3.at samba-tool[25]: Looking up IPv4 addresses
May 24 11:17:56 nsdc-test.ns7a3.at samba-tool[25]: Looking up IPv6 addresses
May 24 11:17:56 nsdc-test.ns7a3.at samba-tool[25]: No IPv6 address will be assigned
May 24 11:17:56 nsdc-test.ns7a3.at samba-tool[25]: Setting up share.ldb
May 24 11:17:57 nsdc-test.ns7a3.at samba-tool[25]: Setting up secrets.ldb
May 24 11:17:58 nsdc-test.ns7a3.at samba-tool[25]: Setting up the registry
May 24 11:18:04 nsdc-test.ns7a3.at samba-tool[25]: Setting up the privileges database
May 24 11:18:06 nsdc-test.ns7a3.at samba-tool[25]: Setting up idmap db
May 24 11:18:07 nsdc-test.ns7a3.at samba-tool[25]: Setting up SAM db
May 24 11:18:07 nsdc-test.ns7a3.at samba-tool[25]: Setting up sam.ldb partitions and settings
May 24 11:18:07 nsdc-test.ns7a3.at samba-tool[25]: Setting up sam.ldb rootDSE
May 24 11:18:08 nsdc-test.ns7a3.at samba-tool[25]: Pre-loading the Samba 4 and AD schema
May 24 11:18:08 nsdc-test.ns7a3.at samba-tool[25]: Adding DomainDN: DC=ns7a3,DC=at
May 24 11:18:08 nsdc-test.ns7a3.at samba-tool[25]: Adding configuration container
May 24 11:18:08 nsdc-test.ns7a3.at samba-tool[25]: Setting up sam.ldb schema
May 24 11:18:12 nsdc-test.ns7a3.at samba-tool[25]: Setting up sam.ldb configuration data
May 24 11:18:12 nsdc-test.ns7a3.at samba-tool[25]: Setting up display specifiers
May 24 11:18:13 nsdc-test.ns7a3.at samba-tool[25]: Modifying display specifiers
May 24 11:18:13 nsdc-test.ns7a3.at samba-tool[25]: Adding users container
May 24 11:18:13 nsdc-test.ns7a3.at samba-tool[25]: Modifying users container
May 24 11:18:13 nsdc-test.ns7a3.at samba-tool[25]: Adding computers container
May 24 11:18:13 nsdc-test.ns7a3.at samba-tool[25]: Modifying computers container
May 24 11:18:13 nsdc-test.ns7a3.at samba-tool[25]: Setting up sam.ldb data
May 24 11:18:13 nsdc-test.ns7a3.at samba-tool[25]: Setting up well known security principals
May 24 11:18:13 nsdc-test.ns7a3.at samba-tool[25]: Setting up sam.ldb users and groups
May 24 11:18:13 nsdc-test.ns7a3.at samba-tool[25]: Setting up self join
May 24 11:18:17 nsdc-test.ns7a3.at samba-tool[25]: Adding DNS accounts
May 24 11:18:18 nsdc-test.ns7a3.at samba-tool[25]: Creating CN=MicrosoftDNS,CN=System,DC=ns7a3,DC=at
May 24 11:18:22 nsdc-test.ns7a3.at samba-tool[25]: Creating DomainDnsZones and ForestDnsZones partitions
May 24 11:18:28 nsdc-test.ns7a3.at samba-tool[25]: Populating DomainDnsZones and ForestDnsZones partitions
May 24 11:18:41 nsdc-test.ns7a3.at samba-tool[25]: Setting up sam.ldb rootDSE marking as synchronized
May 24 11:18:41 nsdc-test.ns7a3.at samba-tool[25]: Fixing provision GUIDs
May 24 11:18:41 nsdc-test.ns7a3.at samba-tool[25]: A Kerberos configuration suitable for Samba 4 has been generated at /var/lib/samba/private/krb5.conf
May 24 11:18:41 nsdc-test.ns7a3.at samba-tool[25]: Once the above files are installed, your Samba4 server will be ready to use
May 24 11:18:41 nsdc-test.ns7a3.at samba-tool[25]: Server Role: active directory domain controller
May 24 11:18:41 nsdc-test.ns7a3.at samba-tool[25]: Hostname: nsdc-test
May 24 11:18:41 nsdc-test.ns7a3.at samba-tool[25]: NetBIOS Domain: NS7A3
May 24 11:18:41 nsdc-test.ns7a3.at samba-tool[25]: DNS Domain: ns7a3.at
May 24 11:18:41 nsdc-test.ns7a3.at samba-tool[25]: DOMAIN SID: S-1-5-21-2032105811-1728666049-3903918006
May 24 11:18:41 nsdc-test.ns7a3.at cp[35]: '/var/lib/samba/private/krb5.conf' -> '/etc/krb5.conf'
May 24 11:18:41 nsdc-test.ns7a3.at systemd[1]: Started Domain controller provisioning.
May 24 11:18:41 nsdc-test.ns7a3.at systemd[1]: Started Samba domain controller daemon.
May 24 11:18:41 nsdc-test.ns7a3.at systemd[1]: Starting Samba domain controller daemon...
May 24 11:18:41 nsdc-test.ns7a3.at systemd[1]: Reached target Multi-User System.
May 24 11:18:41 nsdc-test.ns7a3.at systemd[1]: Starting Multi-User System.
May 24 11:18:41 nsdc-test.ns7a3.at systemd[1]: Reached target Graphical Interface.
May 24 11:18:41 nsdc-test.ns7a3.at systemd[1]: Starting Graphical Interface.
May 24 11:18:41 nsdc-test.ns7a3.at systemd[1]: Started Stop Read-Ahead Data Collection 10s After Completed Startup.
May 24 11:18:41 nsdc-test.ns7a3.at systemd[1]: Starting Update UTMP about System Runlevel Changes...
May 24 11:18:41 nsdc-test.ns7a3.at systemd[1]: Started Update UTMP about System Runlevel Changes.
May 24 11:18:41 nsdc-test.ns7a3.at systemd[1]: Startup finished in 47.085s.
May 24 11:18:41 nsdc-test.ns7a3.at samba[36]: samba version 4.4.3 started.
May 24 11:18:41 nsdc-test.ns7a3.at samba[36]: Copyright Andrew Tridgell and the Samba Team 1992-2016
May 24 11:18:41 nsdc-test.ns7a3.at samba[36]: samba: using 'standard' process model
May 24 11:18:42 nsdc-test.ns7a3.at samba[36]: Attempting to autogenerate TLS self-signed keys for https for hostname 'NSDC-TEST.ns7a3.at'
May 24 11:18:42 nsdc-test.ns7a3.at winbindd[50]: [2016/05/24 11:18:42.104708, 0] ../source3/winbindd/winbindd_cache.c:3245(initialize_winbindd_cache)
May 24 11:18:42 nsdc-test.ns7a3.at winbindd[50]: initialize_winbindd_cache: clearing cache and re-creating with version number 2
May 24 11:18:42 nsdc-test.ns7a3.at winbindd[50]: [2016/05/24 11:18:42.601264, 0] ../lib/util/become_daemon.c:124(daemon_ready)
May 24 11:18:42 nsdc-test.ns7a3.at winbindd[50]: STATUS=daemon 'winbindd' finished starting up and ready to serve connections
May 24 11:18:43 nsdc-test.ns7a3.at smbd[40]: [2016/05/24 11:18:43.939815, 0] ../lib/util/become_daemon.c:124(daemon_ready)
May 24 11:18:43 nsdc-test.ns7a3.at smbd[40]: STATUS=daemon 'smbd' finished starting up and ready to serve connections
May 24 11:18:44 nsdc-test.ns7a3.at samba[36]: TLS self-signed keys generated OK
May 24 11:19:14 nsdc-test.ns7a3.at systemd[1]: Started /usr/bin/samba-tool domain passwordsettings set --min-pwd-age=0 --max-pwd-age=180.
May 24 11:19:14 nsdc-test.ns7a3.at systemd[1]: Starting /usr/bin/samba-tool domain passwordsettings set --min-pwd-age=0 --max-pwd-age=180...
May 24 11:19:15 nsdc-test.ns7a3.at systemd[1]: Started /usr/bin/samba-tool domain passwordsettings show.
May 24 11:19:15 nsdc-test.ns7a3.at systemd[1]: Starting /usr/bin/samba-tool domain passwordsettings show...
May 24 11:19:16 nsdc-test.ns7a3.at systemd[1]: Started /usr/bin/samba-tool domain passwordsettings show.
May 24 11:19:16 nsdc-test.ns7a3.at systemd[1]: Starting /usr/bin/samba-tool domain passwordsettings show...
May 24 11:19:17 nsdc-test.ns7a3.at systemd[1]: Started /usr/bin/samba-tool domain passwordsettings set --complexity=on --history-length=default.
May 24 11:19:17 nsdc-test.ns7a3.at systemd[1]: Starting /usr/bin/samba-tool domain passwordsettings set --complexity=on --history-length=default...
May 24 11:31:46 nsdc-test.ns7a3.at systemd[1]: Started /usr/bin/samba-tool user add jeckel --random-password --must-change-at-next-login --login-shell=/usr/libexec/openssh/sftp-server --unix
May 24 11:31:46 nsdc-test.ns7a3.at systemd[1]: Starting /usr/bin/samba-tool user add jeckel --random-password --must-change-at-next-login --login-shell=/usr/libexec/openssh/sftp-server --uni
May 24 11:31:48 nsdc-test.ns7a3.at systemd[1]: Started /usr/bin/samba-tool user setexpiry jeckel --days=180.
May 24 11:31:48 nsdc-test.ns7a3.at systemd[1]: Starting /usr/bin/samba-tool user setexpiry jeckel --days=180...
May 24 11:32:17 nsdc-test.ns7a3.at systemd[1]: Started /usr/bin/samba-tool user setpassword jeckel.
May 24 11:32:17 nsdc-test.ns7a3.at systemd[1]: Starting /usr/bin/samba-tool user setpassword jeckel...
May 24 11:32:18 nsdc-test.ns7a3.at systemd[1]: Started /usr/bin/samba-tool user enable jeckel.
May 24 11:32:18 nsdc-test.ns7a3.at systemd[1]: Starting /usr/bin/samba-tool user enable jeckel...
May 24 11:33:06 nsdc-test.ns7a3.at systemd[1]: Started /usr/bin/pdbedit -w administrator.
May 24 11:33:06 nsdc-test.ns7a3.at systemd[1]: Starting /usr/bin/pdbedit -w administrator...
May 24 11:33:41 nsdc-test.ns7a3.at systemd[1]: Started /usr/bin/samba-tool user setpassword administrator.
May 24 11:33:41 nsdc-test.ns7a3.at systemd[1]: Starting /usr/bin/samba-tool user setpassword administrator...
May 24 11:33:42 nsdc-test.ns7a3.at systemd[1]: Started /usr/bin/samba-tool user enable administrator.
May 24 11:33:42 nsdc-test.ns7a3.at systemd[1]: Starting /usr/bin/samba-tool user enable administrator...
May 24 11:33:55 nsdc-test.ns7a3.at systemd[1]: Started /usr/bin/pdbedit -w administrator.
May 24 11:33:55 nsdc-test.ns7a3.at systemd[1]: Starting /usr/bin/pdbedit -w administrator...
May 24 11:35:40 nsdc-test.ns7a3.at systemd[1]: Started /usr/bin/pdbedit -w administrator.
May 24 11:35:40 nsdc-test.ns7a3.at systemd[1]: Starting /usr/bin/pdbedit -w administrator...
May 24 11:39:23 nsdc-test.ns7a3.at systemd[1]: Started /usr/bin/pdbedit -w administrator.
May 24 11:39:23 nsdc-test.ns7a3.at systemd[1]: Starting /usr/bin/pdbedit -w administrator...
May 24 13:30:59 nsdc-test.ns7a3.at systemd[1]: Started /usr/bin/pdbedit -w administrator.
May 24 13:30:59 nsdc-test.ns7a3.at systemd[1]: Starting /usr/bin/pdbedit -w administrator...
May 24 13:31:02 nsdc-test.ns7a3.at systemd[1]: Started /usr/bin/pdbedit -w administrator.
May 24 13:31:02 nsdc-test.ns7a3.at systemd[1]: Starting /usr/bin/pdbedit -w administrator...
lines 87-141/141 (END)
As far as i see there is no error in messages or something strange related to nsdc.
PS: i tried to join a ns6.7-vm-pdc from the same machine (gateway and dns point to this ns6.7-vm) and it worked.
I love this sentences! Deeply. Thank you, your commitment to the project is priceless
After I have configured AD on NS7a3, I managed to join to the newly created domain, an Windows 10 pro notebook.
There are probably to many screenshots below but I wanted to show step by step how I did.
Attention at the screenshot no. 5: the username must be âusername@domain.tldâ!
If you will put only âusernameâ and the domain at âDomain nameâ: âdomain.tldâ, after you click on âNextâ, you will get an error and the joining to the domain will fail (at least at me).
Unfortunatelly, after restart, I could not login (the last screenshots).
I will try again tomorrow and I will check the logs to see if I can find something about this.
I have read the news from @giacomo, here:
Call for action from QA team 2016_05
I donât know if is applicable also to NS7a3 and if this is the reason for the login fail.
Like I said, I will try tomorrow.
BR,
Gabriel
Multi domain email server on NS 7a3 - not possible like on NS 6.7?
Tested on VM with OpenLDAP.
I have created a new domain:
Configuration -> Email: âCREATE NEWâ
I have created a new user:
Management -> Users and groups: âCREATE NEWâ
Oops! The user was created for the main domain, without the posibility to choose for which domain to be create, like on NS 6.7.
The only place where you can choose the domain for a user is in
Management -> Email addresses -> Mail aliases: âCREATE NEWâ
Totally unusable for this approach!
Is this version the end of multi domain email server on NS, even if it is not really a complete separate multidomain email server?
I hope no!
As said above, multiple account domains/realms are not planned at the moment, but we could attempt to set up a custom-template for sssd.conf and OpenLDAP.
Hi Davide,
Thank you for clarification.
When I have tried at that moment, only a single domain was configured, as Samba AD and I know that multiple domains are not supported on Samba.
Indeed, you referred also to OpenLDAP.
If I remember well, I think I read somewhere about how to use Samba for multiple domains. If I will find that article, I will tell you. Maybe is interesting.
Thank you again!
Kind regards,
Gabriel
EDIT:
I have bookmarked that articles in browser.
http://samba.2283325.n4.nabble.com/Samba-with-multiple-domains-with-LDAP-backend-td3323460.html
HOLYBET777: No #1 Gambling Sites For Fun & For Your Daily Jackpot
Hi guys,
Some observations regarding NS 7a3 acting as DC (Samba4 AD):
In Web UI, I can enter and switch between âmenusâ from the left side easily, except when I want to enter or exit in / from Status -.> Domain accounts or in Management -> Users and groups.
Usually, I must to click for many times on âDomain accountsâ and wait long time to open that menu and see something in the right side.
When finally the right side window is open, I must click for at least 3 times, again, on âDomain accountsâ to see the domain settings.
I donât know if Iâm well understood; please see the screenshots.
I understand that Samba AD is like a VM inside NS.
Maybe is a problem of interconnection between the two âcomponentsâ?
Itâs like as the Samba VM is not started and trying to start when I click on âDomain accountsâ.
Almost the same problem with âUsers and groupsâ.
The SSSD service is âenabledâ and âRunningâ all time. How can I check?
Maybe this is the reason that I cannot login in the domain.
Does anybody encountered the same problem?
Another question:
I have only 3 users and no group, but in the âDashboardâ there are more users, groups and machine accounts. I think some of them are from Samba VM. Am I right?
That pages are quite slow; surely, we should improve the loading times!
Machines should be at least 2. About users and groups counters, the dashboard counts also some hidden accounts, thus it seems there are more than what we see on the âUsers and groupsâ page.
I reproduced the error with test.ro
as hostname:
# journalctl -M nsdc
...
May 25 10:33:37 nsdc-test.ro samba-tool[23]: ERROR(<class 'samba.provision.ProvisioningError'>): Provision failed - ProvisioningError: guess_names: Realm 'RO' must not be equal to short domain name 'RO'!
Iâm going to restrict the FQDN validator to avoid similar problems.
Thank you Davide!
Can you look at this, please? Itâs only from today.
I still cannot log in.
I can ping the AD by IP but not by name. This could be the problem?
TIA,
Gabriel
Using username ârootâ.
root@192.168.1.8âs password:
************ Welcome to NethServer ************
This is a NethServer installation.
Before editing configuration files, be aware
of the automatic events and templates system.
http://docs.nethserver.org
[root@pdc-ad ~]# journalctl -M nsdc
â Logs begin at Mon 2016-05-23 15:12:49 EEST, end at Wed 2016-05-25 09:34:19 EEST. â
May 25 09:16:20 nsdc-pdc-ad.abt.ro systemd[1]: Received SIGRTMIN+3.
May 25 09:16:20 nsdc-pdc-ad.abt.ro systemd[1]: Stopped target Timers.
May 25 09:16:20 nsdc-pdc-ad.abt.ro systemd[1]: Stopping Timers.
May 25 09:16:20 nsdc-pdc-ad.abt.ro systemd[1]: Stopped target Graphical Interface.
May 25 09:16:20 nsdc-pdc-ad.abt.ro systemd[1]: Stopping Graphical Interface.
May 25 09:16:20 nsdc-pdc-ad.abt.ro systemd[1]: Started Restore /run/initramfs.
May 25 09:16:20 nsdc-pdc-ad.abt.ro systemd[1]: Removed slice system-getty.slice.
May 25 09:16:20 nsdc-pdc-ad.abt.ro systemd[1]: Stopping system-getty.slice.
May 25 09:16:20 nsdc-pdc-ad.abt.ro systemd[1]: Stopped target Multi-User System.
May 25 09:16:20 nsdc-pdc-ad.abt.ro systemd[1]: Stopping Multi-User System.
May 25 09:16:20 nsdc-pdc-ad.abt.ro systemd[1]: Stopping Login ServiceâŚ
May 25 09:16:20 nsdc-pdc-ad.abt.ro systemd[1]: Stopping D-Bus System Message BusâŚ
May 25 09:16:20 nsdc-pdc-ad.abt.ro systemd[1]: Stopped target Login Prompts.
May 25 09:16:20 nsdc-pdc-ad.abt.ro systemd[1]: Stopping Login Prompts.
May 25 09:16:20 nsdc-pdc-ad.abt.ro systemd[1]: Stopped Daily Cleanup of Temporary Directories.
May 25 09:16:20 nsdc-pdc-ad.abt.ro systemd[1]: Stopping Daily Cleanup of Temporary Directories.
May 25 09:16:20 nsdc-pdc-ad.abt.ro systemd[1]: Stopping Console GettyâŚ
May 25 09:16:20 nsdc-pdc-ad.abt.ro winbindd[541]: [2016/05/25 09:16:20.120287, 0] âŚ/source3/winbindd/winbindd.c:280(winbindd_sig_term_handler)
May 25 09:16:20 nsdc-pdc-ad.abt.ro winbindd[541]: Got sig[15] terminate (is_parent=0)
May 25 09:16:20 nsdc-pdc-ad.abt.ro winbindd[43]: [2016/05/25 09:16:20.120720, 0] âŚ/source3/winbindd/winbindd.c:280(winbindd_sig_term_handler)
May 25 09:16:20 nsdc-pdc-ad.abt.ro winbindd[43]: Got sig[15] terminate (is_parent=0)
May 25 09:16:20 nsdc-pdc-ad.abt.ro samba[24]: SIGTERM: killing children
May 25 09:16:20 nsdc-pdc-ad.abt.ro samba[24]: Exiting pid 24 on SIGTERM
May 25 09:16:20 nsdc-pdc-ad.abt.ro samba[24]: Exiting pid 40 on SIGTERM
May 25 09:16:20 nsdc-pdc-ad.abt.ro samba[24]: Exiting pid 39 on SIGTERM
May 25 09:16:20 nsdc-pdc-ad.abt.ro samba[24]: Exiting pid 38 on SIGTERM
May 25 09:16:20 nsdc-pdc-ad.abt.ro samba[24]: Exiting pid 36 on SIGTERM
May 25 09:16:20 nsdc-pdc-ad.abt.ro samba[24]: Exiting pid 35 on SIGTERM
May 25 09:16:20 nsdc-pdc-ad.abt.ro samba[24]: Exiting pid 29 on SIGTERM
May 25 09:16:20 nsdc-pdc-ad.abt.ro samba[24]: Exiting pid 32 on SIGTERM
May 25 09:16:20 nsdc-pdc-ad.abt.ro samba[24]: Exiting pid 30 on SIGTERM
May 25 09:16:20 nsdc-pdc-ad.abt.ro samba[24]: Exiting pid 27 on SIGTERM
May 25 09:16:20 nsdc-pdc-ad.abt.ro samba[24]: Exiting pid 26 on SIGTERM
May 25 09:16:20 nsdc-pdc-ad.abt.ro systemd[1]: Stopping Samba domain controller daemonâŚ
May 25 09:16:20 nsdc-pdc-ad.abt.ro samba[24]: Exiting pid 31 on SIGTERM
May 25 09:16:20 nsdc-pdc-ad.abt.ro samba[24]: Exiting pid 33 on SIGTERM
May 25 09:16:20 nsdc-pdc-ad.abt.ro samba[24]: Exiting pid 34 on SIGTERM
May 25 09:16:20 nsdc-pdc-ad.abt.ro systemd[1]: Stopped D-Bus System Message Bus.
May 25 09:16:20 nsdc-pdc-ad.abt.ro systemd[1]: Stopped Login Service.
May 25 09:16:20 nsdc-pdc-ad.abt.ro systemd[1]: Stopped Console Getty.
May 25 09:16:20 nsdc-pdc-ad.abt.ro systemd[1]: Stopping Permit User SessionsâŚ
May 25 09:16:20 nsdc-pdc-ad.abt.ro systemd[1]: Stopped Permit User Sessions.
May 25 09:16:20 nsdc-pdc-ad.abt.ro systemd[1]: Stopped target Remote File Systems.
May 25 09:16:20 nsdc-pdc-ad.abt.ro systemd[1]: Stopping Remote File Systems.
May 25 09:16:20 nsdc-pdc-ad.abt.ro systemd[1]: Stopped Samba domain controller daemon.
May 25 09:16:20 nsdc-pdc-ad.abt.ro systemd[1]: Stopped target Network.
May 25 09:16:20 nsdc-pdc-ad.abt.ro systemd[1]: Stopping Network.
May 25 09:16:20 nsdc-pdc-ad.abt.ro systemd[1]: Stopped target Basic System.
May 25 09:16:20 nsdc-pdc-ad.abt.ro systemd[1]: Stopping Basic System.
May 25 09:16:20 nsdc-pdc-ad.abt.ro systemd[1]: Stopped target Sockets.
May 25 09:16:20 nsdc-pdc-ad.abt.ro systemd[1]: Stopping Sockets.
May 25 09:16:20 nsdc-pdc-ad.abt.ro systemd[1]: Closed D-Bus System Message Bus Socket.
May 25 09:16:20 nsdc-pdc-ad.abt.ro systemd[1]: Stopping D-Bus System Message Bus Socket.
May 25 09:16:20 nsdc-pdc-ad.abt.ro systemd[1]: Stopped target Slices.
May 25 09:16:20 nsdc-pdc-ad.abt.ro systemd[1]: Stopping Slices.
May 25 09:16:20 nsdc-pdc-ad.abt.ro systemd[1]: Removed slice User and Session Slice.
May 25 09:16:20 nsdc-pdc-ad.abt.ro systemd[1]: Stopping User and Session Slice.
May 25 09:16:20 nsdc-pdc-ad.abt.ro systemd[1]: Stopped target Paths.
May 25 09:16:20 nsdc-pdc-ad.abt.ro systemd[1]: Stopping Paths.
May 25 09:16:20 nsdc-pdc-ad.abt.ro systemd[1]: Stopped Forward Password Requests to Wall Directory Watch.
May 25 09:16:20 nsdc-pdc-ad.abt.ro systemd[1]: Stopping Forward Password Requests to Wall Directory Watch.
May 25 09:16:20 nsdc-pdc-ad.abt.ro systemd[1]: Stopped Dispatch Password Requests to Console Directory Watch.
May 25 09:16:20 nsdc-pdc-ad.abt.ro systemd[1]: Stopping Dispatch Password Requests to Console Directory Watch.
May 25 09:16:20 nsdc-pdc-ad.abt.ro systemd[1]: Stopped target System Initialization.
May 25 09:16:20 nsdc-pdc-ad.abt.ro systemd[1]: Stopping System Initialization.
May 25 09:16:20 nsdc-pdc-ad.abt.ro systemd[1]: Stopping Load/Save Random SeedâŚ
May 25 09:16:20 nsdc-pdc-ad.abt.ro systemd[1]: Stopped target Encrypted Volumes.
May 25 09:16:20 nsdc-pdc-ad.abt.ro systemd[1]: Stopping Encrypted Volumes.
May 25 09:16:20 nsdc-pdc-ad.abt.ro systemd[1]: Stopped target Swap.
May 25 09:16:20 nsdc-pdc-ad.abt.ro systemd[1]: Stopping Swap.
May 25 09:16:20 nsdc-pdc-ad.abt.ro systemd[1]: Stopping Update UTMP about System Boot/ShutdownâŚ
May 25 09:16:20 nsdc-pdc-ad.abt.ro systemd[1]: Stopped Load/Save Random Seed.
May 25 09:16:20 nsdc-pdc-ad.abt.ro systemd[1]: Stopped Update UTMP about System Boot/Shutdown.
May 25 09:16:20 nsdc-pdc-ad.abt.ro systemd[1]: Stopped Create Volatile Files and Directories.
May 25 09:16:20 nsdc-pdc-ad.abt.ro systemd[1]: Stopping Create Volatile Files and DirectoriesâŚ
May 25 09:16:20 nsdc-pdc-ad.abt.ro systemd[1]: Reached target Shutdown.
May 25 09:16:20 nsdc-pdc-ad.abt.ro systemd[1]: Starting Shutdown.
May 25 09:16:20 nsdc-pdc-ad.abt.ro systemd[1]: Stopped target Local File Systems.
May 25 09:16:20 nsdc-pdc-ad.abt.ro systemd[1]: Stopping Local File Systems.
May 25 09:16:20 nsdc-pdc-ad.abt.ro systemd[1]: Unmounting Temporary DirectoryâŚ
May 25 09:16:20 nsdc-pdc-ad.abt.ro systemd[1]: Unmounting /run/systemd/nspawn/incomingâŚ
May 25 09:16:20 nsdc-pdc-ad.abt.ro systemd[1]: Unmounting /proc/sys/kernel/random/boot_idâŚ
May 25 09:16:20 nsdc-pdc-ad.abt.ro systemd[1]: Unmounted /run/systemd/nspawn/incoming.
May 25 09:16:20 nsdc-pdc-ad.abt.ro systemd[1]: Stopped target Local File Systems (Pre).
May 25 09:16:20 nsdc-pdc-ad.abt.ro systemd[1]: Stopping Local File Systems (Pre).
May 25 09:16:20 nsdc-pdc-ad.abt.ro systemd[1]: Unmounted Temporary Directory.
May 25 09:16:20 nsdc-pdc-ad.abt.ro systemd[1]: Unmounted /proc/sys/kernel/random/boot_id.
May 25 09:16:20 nsdc-pdc-ad.abt.ro systemd[1]: Reached target Unmount All Filesystems.
May 25 09:16:20 nsdc-pdc-ad.abt.ro systemd[1]: Starting Unmount All Filesystems.
May 25 09:16:20 nsdc-pdc-ad.abt.ro systemd[1]: Reached target Final Step.
May 25 09:16:20 nsdc-pdc-ad.abt.ro systemd[1]: Starting Final Step.
May 25 09:16:20 nsdc-pdc-ad.abt.ro systemd[1]: Starting HaltâŚ
May 25 09:16:20 nsdc-pdc-ad.abt.ro systemd[1]: Shutting down.
May 25 09:16:20 nsdc-pdc-ad.abt.ro systemd-journal[14]: Journal stopped
â Reboot â
May 25 09:20:02 nsdc-pdc-ad.abt.ro systemd-journal[14]: Runtime journal is using 8.0M (max allowed 91.9M, trying to leave 137.9M free of 911.9M available â c
May 25 09:20:02 nsdc-pdc-ad.abt.ro systemd-journal[14]: Permanent journal is using 8.0M (max allowed 3.1G, trying to leave 4.0G free of 29.3G available â cur
May 25 09:20:02 nsdc-pdc-ad.abt.ro systemd-journal[14]: Time spent on flushing to /var is 110.140ms for 2 entries.
May 25 09:20:02 nsdc-pdc-ad.abt.ro systemd-journal[14]: Journal started
May 25 09:20:02 nsdc-pdc-ad.abt.ro systemd[1]: Starting Flush Journal to Persistent StorageâŚ
May 25 09:20:02 nsdc-pdc-ad.abt.ro systemd[1]: Started Flush Journal to Persistent Storage.
May 25 09:20:02 nsdc-pdc-ad.abt.ro systemd[1]: Starting Create Volatile Files and DirectoriesâŚ
May 25 09:20:02 nsdc-pdc-ad.abt.ro systemd[1]: Started Create Volatile Files and Directories.
May 25 09:20:02 nsdc-pdc-ad.abt.ro systemd[1]: Starting Update UTMP about System Boot/ShutdownâŚ
May 25 09:20:02 nsdc-pdc-ad.abt.ro systemd[1]: Started Update UTMP about System Boot/Shutdown.
May 25 09:20:02 nsdc-pdc-ad.abt.ro systemd[1]: Reached target System Initialization.
May 25 09:20:02 nsdc-pdc-ad.abt.ro systemd[1]: Starting System Initialization.
May 25 09:20:02 nsdc-pdc-ad.abt.ro systemd[1]: Listening on D-Bus System Message Bus Socket.
May 25 09:20:02 nsdc-pdc-ad.abt.ro systemd[1]: Starting D-Bus System Message Bus Socket.
May 25 09:20:02 nsdc-pdc-ad.abt.ro systemd[1]: Reached target Sockets.
May 25 09:20:02 nsdc-pdc-ad.abt.ro systemd[1]: Starting Sockets.
May 25 09:20:02 nsdc-pdc-ad.abt.ro systemd[1]: Reached target Basic System.
May 25 09:20:02 nsdc-pdc-ad.abt.ro systemd[1]: Starting Basic System.
May 25 09:20:02 nsdc-pdc-ad.abt.ro systemd[1]: Started Domain controller provisioning.
May 25 09:20:02 nsdc-pdc-ad.abt.ro systemd[1]: Starting Login ServiceâŚ
May 25 09:20:02 nsdc-pdc-ad.abt.ro systemd[1]: Started D-Bus System Message Bus.
May 25 09:20:03 nsdc-pdc-ad.abt.ro dbus-daemon[20]: dbus[20]: [system] Successfully activated service âorg.freedesktop.systemd1â
May 25 09:20:03 nsdc-pdc-ad.abt.ro dbus[20]: [system] Successfully activated service âorg.freedesktop.systemd1â
May 25 09:20:03 nsdc-pdc-ad.abt.ro systemd[1]: Starting D-Bus System Message BusâŚ
May 25 09:20:03 nsdc-pdc-ad.abt.ro systemd[1]: Starting Network ServiceâŚ
May 25 09:20:03 nsdc-pdc-ad.abt.ro systemd[1]: Starting Permit User SessionsâŚ
May 25 09:20:03 nsdc-pdc-ad.abt.ro systemd[1]: Started Daily Cleanup of Temporary Directories.
May 25 09:20:03 nsdc-pdc-ad.abt.ro systemd[1]: Starting Daily Cleanup of Temporary Directories.
May 25 09:20:03 nsdc-pdc-ad.abt.ro systemd[1]: Reached target Timers.
May 25 09:20:03 nsdc-pdc-ad.abt.ro systemd[1]: Starting Timers.
May 25 09:20:03 nsdc-pdc-ad.abt.ro systemd[1]: Started Login Service.
May 25 09:20:03 nsdc-pdc-ad.abt.ro systemd-logind[19]: New seat seat0.
May 25 09:20:03 nsdc-pdc-ad.abt.ro systemd[1]: Started Permit User Sessions.
May 25 09:20:03 nsdc-pdc-ad.abt.ro systemd[1]: Started Getty on tty1.
May 25 09:20:03 nsdc-pdc-ad.abt.ro systemd[1]: Started Console Getty.
May 25 09:20:03 nsdc-pdc-ad.abt.ro systemd[1]: Starting Console GettyâŚ
May 25 09:20:03 nsdc-pdc-ad.abt.ro systemd[1]: Reached target Login Prompts.
May 25 09:20:03 nsdc-pdc-ad.abt.ro systemd[1]: Starting Login Prompts.
May 25 09:20:03 nsdc-pdc-ad.abt.ro systemd-networkd[21]: host0 : Cannot configure IPv4 forwarding for interface host0: Read-only file system
May 25 09:20:03 nsdc-pdc-ad.abt.ro systemd-networkd[21]: host0 : Cannot configure IPv6 forwarding for interface: Read-only file system
May 25 09:20:03 nsdc-pdc-ad.abt.ro systemd-networkd[21]: Enumeration completed
May 25 09:20:03 nsdc-pdc-ad.abt.ro systemd[1]: Started Network Service.
May 25 09:20:03 nsdc-pdc-ad.abt.ro systemd-networkd[21]: host0 : gained carrier
May 25 09:20:03 nsdc-pdc-ad.abt.ro systemd-networkd[21]: host0 : link configured
May 25 09:20:03 nsdc-pdc-ad.abt.ro systemd[1]: Reached target Network.
May 25 09:20:03 nsdc-pdc-ad.abt.ro systemd[1]: Starting Network.
May 25 09:20:03 nsdc-pdc-ad.abt.ro systemd[1]: Started Samba domain controller daemon.
May 25 09:20:03 nsdc-pdc-ad.abt.ro systemd[1]: Starting Samba domain controller daemonâŚ
May 25 09:20:03 nsdc-pdc-ad.abt.ro systemd[1]: Reached target Multi-User System.
May 25 09:20:03 nsdc-pdc-ad.abt.ro systemd[1]: Starting Multi-User System.
May 25 09:20:03 nsdc-pdc-ad.abt.ro systemd[1]: Reached target Graphical Interface.
May 25 09:20:03 nsdc-pdc-ad.abt.ro systemd[1]: Starting Graphical Interface.
May 25 09:20:03 nsdc-pdc-ad.abt.ro systemd[1]: Starting Update UTMP about System Runlevel ChangesâŚ
May 25 09:20:03 nsdc-pdc-ad.abt.ro systemd[1]: Started Stop Read-Ahead Data Collection 10s After Completed Startup.
May 25 09:20:03 nsdc-pdc-ad.abt.ro systemd[1]: Started Update UTMP about System Runlevel Changes.
May 25 09:20:03 nsdc-pdc-ad.abt.ro systemd[1]: Startup finished in 2.505s.
May 25 09:20:04 nsdc-pdc-ad.abt.ro samba[24]: samba version 4.4.3 started.
May 25 09:20:04 nsdc-pdc-ad.abt.ro samba[24]: Copyright Andrew Tridgell and the Samba Team 1992-2016
May 25 09:20:06 nsdc-pdc-ad.abt.ro samba[24]: samba: using âstandardâ process model
May 25 09:20:07 nsdc-pdc-ad.abt.ro winbindd[37]: [2016/05/25 09:20:06.993431, 0] âŚ/source3/winbindd/winbindd_cache.c:3245(initialize_winbindd_cache)
May 25 09:20:07 nsdc-pdc-ad.abt.ro winbindd[37]: initialize_winbindd_cache: clearing cache and re-creating with version number 2
May 25 09:20:07 nsdc-pdc-ad.abt.ro winbindd[37]: [2016/05/25 09:20:07.573177, 0] âŚ/lib/util/become_daemon.c:124(daemon_ready)
May 25 09:20:07 nsdc-pdc-ad.abt.ro winbindd[37]: STATUS=daemon âwinbinddâ finished starting up and ready to serve connections
May 25 09:20:08 nsdc-pdc-ad.abt.ro smbd[28]: [2016/05/25 09:20:08.216764, 0] âŚ/lib/util/become_daemon.c:124(daemon_ready)
May 25 09:20:08 nsdc-pdc-ad.abt.ro smbd[28]: STATUS=daemon âsmbdâ finished starting up and ready to serve connections
May 25 09:34:19 nsdc-pdc-ad.abt.ro systemd[1]: Starting Cleanup of Temporary DirectoriesâŚ
May 25 09:34:19 nsdc-pdc-ad.abt.ro systemd[1]: Started Cleanup of Temporary Directories.
lines 483-540/540 (END)
Solved this: Configuration â DNS â added 192.168.1.8 as primary DNS.
I will try again to loggin.
dnsmasq should automatically forward DNS requests for abt.ro to your DC (192.168.1.8). Other names should be forwarded to the upstream DNS: config show dns
.
Primary DNS should be an external DNS, like Google 8.8.4.4, or similar⌠Do not set it to the DC IP, otherwise Internet names cannot be resolved!