The system detected a possible attempt to compromise security
- From: jlee161@xxxxxxxxx
- Date: Wed, 13 Feb 2008 08:15:09 -0800 (PST)
"The system detected a possible attempt to compromise security.
Please ensure that you can contact the server that authenticated you."
I have the solution already. I'm posting this should anyone else
experience an issue like it.
We were have issues with a tree in one of our Forests. The tree no
longer was able to replicate with any other domains in the forest, and
although the machines, and users could authenticate some applications,
like siebel, oracle were unable to.
Problems:
*-We were getting this error attempting validate the trust with
NETDOM, although it would claim to validate in Domain & Trust MMC.
*-We would also get the same error message when attempting to connect
with AD User and Computers trying connect TO the tree root of the
affected domain.
*-Any attempt to replicate with sites and service would generate an
Access Denied error
*-Repadmin would show error 1265
Here's how the domain is set up
Forest root domain, with two domain controllers, one global gatalog in
Office "A".
Seperate Tree, with two domain controllers, one global catalog, in
Office "B"
for the root, the PDC and the schema master are hosted in Office A, on
the GC.
the RID, IM, DM roles are hosted on the root dc, office B
for the other tree the IM role is hosted on the NON-GC Domain
Controller in Office A
the PDC, and RID are hosted on the GC domain controller in Office B
Here is the scenario in which this occured:
The motherboard in the PDC in the office B in the tree failed. It was
replaced, but the BIOS on the new board had a date that was from
2004. The result was the authorative time source for the tree now
became suspect to the root domain.
The resolution is described here, with one exception: I had to use
the /transitive and /force switches to make it work
so the command, run from the ROOT domain, looked like this
c:\>netdom trust "root domain" /domain: "child, or tree root domai" /
reset /transitive:yes /force
http://support.microsoft.com/kb/892426
RESOLUTION
To resolve this issue, reset the trust relationship. To do this,
follow these steps: 1. At a command prompt, type c:\>netdom trust
domain on which the trust is created /domain:the parent, child, or
tree root domain being trusted /reset, and then press ENTER.
Important You must use the fully qualified domain names (FQDNs) in
this command.
After you run this command, you receive the following message:
Resetting the trust passwords between domain on which the trust is
created and the parent, child, or tree root domain being trusted The
trust between domain on which the trust is created and the parent,
child, or tree root domain being trusted has been successfully reset
and verified The command completed successfully.
2. Obtain the domain on which the trust is created domain controller
object GUID. To do this, follow these steps: a. At the command
prompt, type repadmin /showreps mydc1, and then press ENTER, where
mydc1 is the computer name of the domain on which the trust is created
domain controller.
b. Note the objectGUID line at the top of the output. The object GUID
looks similar to the following object GUID:
a6999e16-99b5-432f-9bc5-3eecf5dc192f
3. Make sure that replication occurs correctly between the two
replication partners. To do this, run the c:\repadmin /sync
cn=configuration,dc=mydomain,dc=com mydc1objectGUID command at a
command prompt by using the object GUID that you noted in step 2. You
receive output that is similar to the following output:
Sync from a6999e16-99b5-432f-9bc5-3eecf5dc192f to mydc1 completed
successfully.
.
- Follow-Ups:
- Re: The system detected a possible attempt to compromise security
- From: Jorge Silva
- Re: The system detected a possible attempt to compromise security
- Prev by Date: Re: Decision criteria for AD replication
- Next by Date: Re: Decision criteria for AD replication
- Previous by thread: RE: dsmod error with Domain Users Group
- Next by thread: Re: The system detected a possible attempt to compromise security
- Index(es):
Relevant Pages
|
