Rowland Penny
2015-Feb-27 10:01 UTC
[Samba] After Windows login black screen with mouse cursor
On 27/02/15 09:50, Tim wrote:> In addition to what I have written I should say that I enabled SSSD on > the DCs this week. Possibly this is the reason for this and sssd > causes winbind problems on a DC? > > I will disable it to test. > > > > Am 27.02.2015 09:32, schrieb Tim: >> Hello, >> >> I did an update from 4.1.16 to 4.1.17 yesterday and had some problems >> with it (using sernet package). But I think it is fine now: Replication >> works so far. Samba-tool drs showrepl has no failure and I created a >> user and it was instantly available on both DCs. >> >> This morning a lot of clients had the following issue: >> They were started as usual and the users do their login. But after this >> a black screen appears where only the mouse cursor is shown. It lasts 10 >> to 15min until the normal desktop appears. >> >> First I suspected two new installed Windows updates (KB3006137 and >> KB3021917) but after deinstallation nothing changed. >> >> I use roaming profiles via gpo and folder redirection for AppData, >> Desktop, Documents and Favorites. >> >> One more note: One client had this two days ago with 4.1.16. >> >> There is a failure on each client: >> Event ID 5719, NETLOGON, This computer was not able to set up a secure >> session with a domain controller in domain Domain due to the following: >> There are currently no logon servers available to service the logon >> request.... >> >> Is this possibly causing the headache? >> >> Any hints are welcome. >> >> Thanks >> TimHi, what version of sssd, I forget the version it was added at, but sssd now comes with its own version of winbind and this could be colliding with samba's winbind. Rowland
And this can cause such behaviour? Am 27. Februar 2015 11:01:15 MEZ, schrieb Rowland Penny <rowlandpenny at googlemail.com>:>On 27/02/15 09:50, Tim wrote: >> In addition to what I have written I should say that I enabled SSSD >on >> the DCs this week. Possibly this is the reason for this and sssd >> causes winbind problems on a DC? >> >> I will disable it to test. >> >> >> >> Am 27.02.2015 09:32, schrieb Tim: >>> Hello, >>> >>> I did an update from 4.1.16 to 4.1.17 yesterday and had some >problems >>> with it (using sernet package). But I think it is fine now: >Replication >>> works so far. Samba-tool drs showrepl has no failure and I created a >>> user and it was instantly available on both DCs. >>> >>> This morning a lot of clients had the following issue: >>> They were started as usual and the users do their login. But after >this >>> a black screen appears where only the mouse cursor is shown. It >lasts 10 >>> to 15min until the normal desktop appears. >>> >>> First I suspected two new installed Windows updates (KB3006137 and >>> KB3021917) but after deinstallation nothing changed. >>> >>> I use roaming profiles via gpo and folder redirection for AppData, >>> Desktop, Documents and Favorites. >>> >>> One more note: One client had this two days ago with 4.1.16. >>> >>> There is a failure on each client: >>> Event ID 5719, NETLOGON, This computer was not able to set up a >secure >>> session with a domain controller in domain Domain due to the >following: >>> There are currently no logon servers available to service the logon >>> request.... >>> >>> Is this possibly causing the headache? >>> >>> Any hints are welcome. >>> >>> Thanks >>> Tim > >Hi, what version of sssd, I forget the version it was added at, but >sssd >now comes with its own version of winbind and this could be colliding >with samba's winbind. > >Rowland > >-- >To unsubscribe from this list go to the following URL and read the >instructions: https://lists.samba.org/mailman/options/samba
Rowland Penny
2015-Feb-27 10:17 UTC
[Samba] After Windows login black screen with mouse cursor
On 27/02/15 10:13, Tim wrote:> And this can cause such behaviour? > > Am 27. Februar 2015 11:01:15 MEZ, schrieb Rowland Penny > <rowlandpenny at googlemail.com>: > > On 27/02/15 09:50, Tim wrote: > > In addition to what I have written I should say that I enabled > SSSD on the DCs this week. Possibly this is the reason for > this and sssd causes winbind problems on a DC? I will disable > it to test. Am 27.02.2015 09:32, schrieb Tim: > > Hello, I did an update from 4.1.16 to 4.1.17 yesterday and > had some problems with it (using sernet package). But I > think it is fine now: Replication works so far. Samba-tool > drs showrepl has no failure and I created a user and it > was instantly available on both DCs. This morning a lot of > clients had the following issue: They were started as > usual and the users do their login. But after this a black > screen appears where only the mouse cursor is shown. It > lasts 10 to 15min until the normal desktop appears. First > I suspected two new installed Windows updates (KB3006137 > and KB3021917) but after deinstallation nothing changed. I > use roaming profiles via gpo and folder redirection for > AppData, Desktop, Documents and Favorites. One more note: > One client had this two days ago with 4.1.16. There is a > failure on each client: Event ID 5719, NETLOGON, This > computer was not able to set up a secure session with a > domain controller in domain Domain due to the following: > There are currently no logon servers available to service > the logon request.... Is this possibly causing the > headache? Any hints are welcome. Thanks Tim > > > Hi, what version of sssd, I forget the version it was added at, but > sssd > now comes with its own version of winbind and this could be colliding > with samba's winbind. > > Rowland >Don't know, but it is something to check, I suppose you have ruled out it being virus related. Rowland
On Fri, 27 Feb 2015, Tim wrote:> And this can cause such behaviour?No, SSSD is only used for local authentication on the machine. Samba 4 as an AD DC is only going to be serving information from it's own LDAP database. BTW, I use SSSD on my domain controllers with no issues.> Am 27. Februar 2015 11:01:15 MEZ, schrieb Rowland Penny <rowlandpenny at googlemail.com>: >> On 27/02/15 09:50, Tim wrote: >>> In addition to what I have written I should say that I enabled SSSD >> on >>> the DCs this week. Possibly this is the reason for this and sssd >>> causes winbind problems on a DC?