1 Antwort
- Neueste
- Die meisten Stimmen
- Die meisten Kommentare
1
Hi, This is because for some reason the secure comms setup between the client machine and the domain somehow got interrupted/broken (its often not clear why this could have happened) - the remedy is just to log on to the machine as a local user and then remove and re-add the machine to the ADMINDOMAIN - then everything should start working again as normal.
I would have kind of expected the USERDOMAIN to also have some kind of issue as that would somehow be allowed via a trust via the primary domain i would have thought - there must be some reason that is still working OK - but nonetheless - you still need to remove/add the machine back to the admin domain.
Thanks, Rich
beantwortet vor 5 Monaten
Relevanter Inhalt
- AWS OFFICIALAktualisiert vor 2 Jahren
- Wie verbinde ich verschiedene Zweigstellen mithilfe von AWS Site-to-Site VPN und AWS Direct Connect?AWS OFFICIALAktualisiert vor einem Jahr
- AWS OFFICIALAktualisiert vor 2 Jahren
- AWS OFFICIALAktualisiert vor 3 Jahren
Hey Rich, Thank you for the quick response. Do you have any video/blog post on how to do this. I have never done before I am afraid of deleting something I'm not supposed to!