samba - Jun 2019 - User has no RSOP data ?

is this pc is renamed after it joined the domain?


if yes, then you hitted a bug, cant look, im on the road.. but rowland knows how
to check for missed updated records in ad. is a ms problem.

if no, i still suggest to check these records. ;-).



Greetz,


Louis




Op 3 jun. 2019, om 13:21, Rowland penny via samba <samba at
lists.samba.org> schreef:
On 03/06/2019 12:07, Stefan G. Weichinger via samba wrote:
Am 03.06.19 um 12:48 schrieb Rowland penny via samba:

I read a few more of the results that the google search 'user has no
rsop data' returned. It seems it is something that happens fairly often,
for various reasons, from dns, through 'user not logged in', to
'netlogon server' not running or set to manual, so I repeat, I do not
think this is a Samba problem. Your RSAT problem could be tied into your
main problem or it could be a totally separate problem, but you will not
know until you sort the main problem ;-)
RSAT works when I enter the IP of a DC ... I can edit objects etc -> ok
for me now

I don't know what to fix, though ;-)

I will have them check the DNSs on the one PC. Or check via teamviewer
later.

The windows-server-user pulls the GPOs ok.

dbcheck looks OK on both DCs, wbinfo-queries work ...

Stefan, you didn't have a problem, a new PC was added and you now have 
problem. I would be peering very, very closely at the new PC and ruling 
that out before I looked anywhere else.

Rowland

Am 03.06.19 um 16:56 schrieb L.P.H. van Belle via samba:
> is this pc is renamed after it joined the domain?
> 
> 
> if yes, then you hitted a bug, cant look, im on the road.. but rowland
knows how to check for missed updated records in ad. is a ms problem.
> 
> if no, i still suggest to check these records. ;-).
I also thought of this:

very likely that they didn't remove the PC from the domain before
replacing the hardware.

The old PC died, the ordered a new one and (I assume) named it the same
as the old one.

So the computer account already existed before.

I told the guy to leave and rejoin the domain again, but he seems not to
have done that.