In fact, I was even able to login after I shut down the windows server,
because of the "winbind offline logon = Yes" setting. I got a notice
saying that the controller was offline, but logged in to the desktop
without further problems, launched applications, etc.
--
You received this bug
Please attach these logs from when the login failure happens:
- /var/log/auth.log
- /var/log/syslog
- /var/log/samba/log*
I configured a VM with your smb.conf, joined a windows 2016 AD server
via net ads join -k and AD users can login just fine immediately after a
reboot.
I also used your
Thanks for the feedback.
I haven't tried the sssd gpo controls myself yet, and I see you have
them set at "permissive", which tells me it would not be preventing
users from changing things. But let's say there is a bug in that area,
would the GPO controls be able to cause what you are seeing?
I think that time is past, we were in beta freeze in the past week, and
are in final freeze now. Unless there is a clear test case showing under
which conditions this happens and how widespread it is, it's probably
best to start thinking in SRU terms.
It looks like a safe change, but since I
Ok, what are the contents of the netplan file?
On Fri, Apr 20, 2018, 04:31 msaxl <1764...@bugs.launchpad.net> wrote:
> /etc/netplan/ contains 01-network-manager-all.yaml, if I remove it I get
> no network connection.
> This systems seems to be already migrated to netplan.
>
>
