Local Domain XP logon Errors

[MeanGene]

Windows cannot determine the user or computer name. (The specified domain either does not exist or could not be contacted. ). Group Policy processing aborted.


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.

I find these errors in the Event Viewer Application section. I also take a long time to login. I have a Windows 2000 server runing AD and DNS is running but DHCP comes from the Asante router via Pacbell.

 

[JJB6486]

Are you sure the domain is spelled correctly, and that the user account on the domain controller you are using has the correct rights?

JJB6486

 

[chooch]

Is the workstation pointing to the right DNS Server or is the DHCP Server giving it the proper IP for your DNS? Try pinging the host name of your DC, if you get a reply then scartch the above, if not then your workstation is not pointing to the proper DNS. Also try pinging anything make sure you have connectivity, just my two cents.

 

[MeanGene]

Yes it should be correct, I added the XP machine to the domain through the seup Wizard. When I go in to AD on the server (throght Terminal Server). The machine is there and all user accounts are there. I am a Domain Admin.

I have turned DHCP back on and am going to see if that helps. I am sure that I am not the only one doing this. What is the best way to set up a local domain?

I mean, It isn't a problem until you have a Server, a router and a DSL modem that are all trying to do DHCP. I have truned it off in the modem and run it form the router. This is done because the server is not always on and I want to make sure the network can always get to the internt without having to turn another computer on. But I want to have AD running for access to additional resources when available.

 

[chooch]

Do you have Dynamic DNS enable on your server (I'm assuming the server is also a DHCP client) this would ensure that DNS has the proper IP for the server, not really recommended, the best way, in addition to what you already have which is fine, would be to give the server a static IP and leave it on at all times.

 

[MeanGene]

Do you mean DDNS?

Everything works find once it gets booted. Complete connectivity. It just takes a couple of minutes to logon, and the error messages in the event viewer. I would like to figure out how to get around this.

 

[Lonman]

Here's an article about the error code you gave:

http://support.microsoft.com/default.aspx?scid=kb;EN-US;Q274320

Oops! here you go:

http://support.microsoft.com/default.aspx?scid=kb;EN-US;Q310461

 

[Lactic.Acid]

I had this problem with my domain controller as well. First, make sure you have the Netlogon service running, as well as Server and Workstation services. You can check this page ( http://support.microsoft.com/directory/article.asp?ID=KB;EN-US;Q269375 ) for info on this issue. After fixing this, removing trailing spaces in the registry entry, and rebooting, my DC sped right back up.
/L.A