"Phillip Windell" wrote:

> I have one XP machine that has start having trouble authenticating with the
> domain controller.
>
> These are the two event log errors on the machine:
>
> ------------------------------------------------------
> Event Type: Error
> Event Source: AutoEnrollment
> Event Category: None
> Event ID: 15
> Date:  11/28/2007
> Time:  11:47:07 AM
> User:  N/A
> Computer: AXIO270
> Description:
> Automatic certificate enrollment for local system failed to contact the
> active directory (0x80072726).  An invalid argument was supplied.
>   Enrollment will not be performed.
>
> Event Type: Error
> Event Source: Userenv
> Event Category: None
> Event ID: 1054
> Date:  11/28/2007
> Time:  11:46:34 AM
> User:  NT AUTHORITY\SYSTEM
> Computer: AXIO270
> Description:
> Windows cannot obtain the domain controller name for your computer network.
> (An invalid argument was supplied. ). Group Policy processing aborted.
> ------------------------------------------------------
>
> I already tried the KB article suggesting to disable Media Sense, it did no
> good. I also tried setting the Nic to specifically 100 Full-Dup.  That did
> no good either. So I put everything back the way it was.
>
> It seems to have a perfect connection at the network level. It can both ping
> and resolve the names of the two DCs.
>
> The TCP/IP settings are via DHCP and they are correct and use the DCs as the
> DNS Servers.  I also tried static settings, but did no good.
>
> I tried once to remove, then rejoin it to the domain. It removed ok, but
> would not rejoin claiming that a DC could not be found.  I left it for a few
> days,..then started it up today, tried to join,..it joined perfectly on the
> first try.  Then about an hour later the whole problem came back again.
>
> All other machines on the LAN (around 100) have no problems at all like
> this.
>
> Any ideas that I have not tried?
>
> --
> Phillip Windell
> www.wandtv.com
>
> The views expressed, are my own and not those of my employer, or Microsoft,
> or anyone else associated with me, including my cats.
> -----------------------------------------------------
>
>
>

"arida" <alnoha***@yahoo.com> wrote in message
news:D8FC5E8A-B3B6-4B91-9311-65379F6466FD@microsoft.com...
> Hi Philip,
> I think u connect to the cash not to the real DC,
> so,
> Try to use the local administrator account to disconnect from the domain
> and
> switch to a workgroup configuration. Then restarte twice and then logged
> in
> again as the local administrator and re-connected to the domain using the
> wizerd. All was well from this point on.
>
> --
> M. Arida
>
>
> "Phillip Windell" wrote:
>
>> I have one XP machine that has start having trouble authenticating with
>> the
>> domain controller.
>>
>> These are the two event log errors on the machine:
>>
>> ------------------------------------------------------
>> Event Type: Error
>> Event Source: AutoEnrollment
>> Event Category: None
>> Event ID: 15
>> Date:  11/28/2007
>> Time:  11:47:07 AM
>> User:  N/A
>> Computer: AXIO270
>> Description:
>> Automatic certificate enrollment for local system failed to contact the
>> active directory (0x80072726).  An invalid argument was supplied.
>>   Enrollment will not be performed.
>>
>> Event Type: Error
>> Event Source: Userenv
>> Event Category: None
>> Event ID: 1054
>> Date:  11/28/2007
>> Time:  11:46:34 AM
>> User:  NT AUTHORITY\SYSTEM
>> Computer: AXIO270
>> Description:
>> Windows cannot obtain the domain controller name for your computer
>> network.
>> (An invalid argument was supplied. ). Group Policy processing aborted.
>> ------------------------------------------------------
>>
>> I already tried the KB article suggesting to disable Media Sense, it did
>> no
>> good. I also tried setting the Nic to specifically 100 Full-Dup.  That
>> did
>> no good either. So I put everything back the way it was.
>>
>> It seems to have a perfect connection at the network level. It can both
>> ping
>> and resolve the names of the two DCs.
>>
>> The TCP/IP settings are via DHCP and they are correct and use the DCs as
>> the
>> DNS Servers.  I also tried static settings, but did no good.
>>
>> I tried once to remove, then rejoin it to the domain. It removed ok, but
>> would not rejoin claiming that a DC could not be found.  I left it for a
>> few
>> days,..then started it up today, tried to join,..it joined perfectly on
>> the
>> first try.  Then about an hour later the whole problem came back again.
>>
>> All other machines on the LAN (around 100) have no problems at all like
>> this.
>>
>> Any ideas that I have not tried?
>>
>> --
>> Phillip Windell
>> www.wandtv.com
>>
>> The views expressed, are my own and not those of my employer, or
>> Microsoft,
>> or anyone else associated with me, including my cats.
>> -----------------------------------------------------
>>
>>
>>