The saga around the misnamed DC seems over, so let's open a new thread ;-) In the same AD I see this: in smbstatus I see a smbd-PID for a Username "root", Group "root" But the actual user logged in is another one. So I assume there has been some wrong mapping/naming in the past. I don't think that user actually runs with root-privileges or so ... it's just ugly and wrong and I'd like to clean that up as well, if possible. For sure I'd like to avoid deleting/recreating that user. Any ideas how to approach this?
On 05/08/2019 09:33, Stefan G. Weichinger via samba wrote:> The saga around the misnamed DC seems over, so let's open a new thread ;-) > > In the same AD I see this: > > in smbstatus I see a smbd-PID for a Username "root", Group "root" > > But the actual user logged in is another one. So I assume there has been > some wrong mapping/naming in the past.Who is logged in ? and what are they trying to do ? Also, where are they logged in ?> > I don't think that user actually runs with root-privileges or so ... > it's just ugly and wrong and I'd like to clean that up as well, if possible.No user (except for Administrator) needs to log in as root, so you may need to fix this.> > For sure I'd like to avoid deleting/recreating that user.You shouldn't have to, though you may have to change something in the users AD object.> > Any ideas how to approach this? > >Yes, give us more info ;-) Rowland
Am 05.08.19 um 10:41 schrieb Rowland penny via samba:> On 05/08/2019 09:33, Stefan G. Weichinger via samba wrote: >> The saga around the misnamed DC seems over, so let's open a new thread >> ;-) >> >> In the same AD I see this: >> >> in smbstatus I see a smbd-PID for a Username "root", Group "root" >> >> But the actual user logged in is another one. So I assume there has been >> some wrong mapping/naming in the past. > > Who is logged in ? and what are they trying to do ? > > Also, where are they logged in ?Just some plain Windows-10-user on a PC ... using file shares etc Or do I misunderstand the question?>> For sure I'd like to avoid deleting/recreating that user. > You shouldn't have to, though you may have to change something in the > users AD object. >> >> Any ideas how to approach this? >> >> > Yes, give us more info ;-)Happy to do so. Where to start?