Here's an odd one...

I'm running a Windows 2000 SBS Server. It has 3 segments and 4 NICs in the
server (3 internal and 1 external)

Internal 192.168.0.100
Internal 192.168.1.100
Internal 192.168.2.100
External xxx.xxx.xxx.xxx

I recently decided to reinstall Windows XP on a users PC which was running
very slowly, taking ages to log in and occasionally crashing.

It could was also getting the following errors:

Event Type: Error
Event Source: AutoEnrollment
Event Category: None
Event ID: 15
Date: 31/07/2003
Time: 14:57:55
User: N/A
Computer: SEAN04
Description:
Automatic certificate enrollment for local system failed to contact the
active directory (0x8007054b). The specified domain either does not exist
or could not be contacted.
Enrollment will not be performed.

For more information, see Help and Support Center at
http://go.microsoft.com/fwlink/events.asp.

Event Type: Error
Event Source: Userenv
Event Category: None
Event ID: 1054
Date: 31/07/2003
Time: 14:56:49
User: NT AUTHORITY\SYSTEM
Computer: SEAN04
Description:
Windows cannot obtain the domain controller name for your computer network.
(The specified domain either does not exist or could not be contacted. ).
Group Policy processing aborted.

For more information, see Help and Support Center at
http://go.microsoft.com/fwlink/events.asp.

The users machine was on segment 2 (192.168.2.100), but I brought it back to
my office on segment 0 (192.168.0.100) to reinstall the o/s and software.
It worked perfectly and was much faster on startup, so I returned the
machine to segment 2 only to start it up and get the same errors again! it
does seem to be running ok though in general - just wondered if anyone could
shed any light on why this might be happening. The only advice I've
received so far was to throttle back the NIC in the PC to 100Mbs Half Duplex
rather than auto detect, but this made no difference.

Thanks in advance
Jason

Re: Auto Enrollment Error by Les

Les
Tue Aug 05 09:25:26 CDT 2003

Hi Jonny,

If you could do an ipconfig /all at both the SBS and the client, and post
the results, that may shed some light on the problem and lead to possible
solutions.

--
Les Connor
------------------
[SBS MVP]



"Jonny Yen" <NOSPAM@NOSPAM.com> wrote in message
news:#D$ETN3VDHA.2104@TK2MSFTNGP10.phx.gbl...
> Here's an odd one...
>
> I'm running a Windows 2000 SBS Server. It has 3 segments and 4 NICs in
the
> server (3 internal and 1 external)
>
> Internal 192.168.0.100
> Internal 192.168.1.100
> Internal 192.168.2.100
> External xxx.xxx.xxx.xxx
>
> I recently decided to reinstall Windows XP on a users PC which was running
> very slowly, taking ages to log in and occasionally crashing.
>
> It could was also getting the following errors:
>
> Event Type: Error
> Event Source: AutoEnrollment
> Event Category: None
> Event ID: 15
> Date: 31/07/2003
> Time: 14:57:55
> User: N/A
> Computer: SEAN04
> Description:
> Automatic certificate enrollment for local system failed to contact the
> active directory (0x8007054b). The specified domain either does not exist
> or could not be contacted.
> Enrollment will not be performed.
>
> For more information, see Help and Support Center at
> http://go.microsoft.com/fwlink/events.asp.
>
> Event Type: Error
> Event Source: Userenv
> Event Category: None
> Event ID: 1054
> Date: 31/07/2003
> Time: 14:56:49
> User: NT AUTHORITY\SYSTEM
> Computer: SEAN04
> Description:
> Windows cannot obtain the domain controller name for your computer
network.
> (The specified domain either does not exist or could not be contacted. ).
> Group Policy processing aborted.
>
> For more information, see Help and Support Center at
> http://go.microsoft.com/fwlink/events.asp.
>
> The users machine was on segment 2 (192.168.2.100), but I brought it back
to
> my office on segment 0 (192.168.0.100) to reinstall the o/s and software.
> It worked perfectly and was much faster on startup, so I returned the
> machine to segment 2 only to start it up and get the same errors again!
it
> does seem to be running ok though in general - just wondered if anyone
could
> shed any light on why this might be happening. The only advice I've
> received so far was to throttle back the NIC in the PC to 100Mbs Half
Duplex
> rather than auto detect, but this made no difference.
>
> Thanks in advance
> Jason
>
>