Local Domain XP logon Errors

January 2nd, 2002

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** · January 2nd, 2002

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

January 2nd, 2002

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.

January 2nd, 2002

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.

January 2nd, 2002

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.

January 2nd, 2002

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** · January 2nd, 2002

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

http://support.microsoft.com/default...;EN-US;Q274320

Oops! here you go:

http://support.microsoft.com/default...;EN-US;Q310461

January 2nd, 2002

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/directo...;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

January 2nd, 2002	Top \| #1
MeanGene Unregistered Posts: n/a	Local Domain XP logon Errors 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.

Similar Threads
Thread	Thread Starter	Forum	Replies	Last Post
Internet Use Issue - Workgoup Vs .local domain	melfordgurl	Windows Desktop Systems	3	January 14th, 2008 5:31pm
DSL--WAP/Router--Win 2003 Server--WAP/Switch--local domain--and wireless laptops/desk	SDIAZ911	General Hardware	0	April 20th, 2005 5:10pm
Domain Logon Error	Datadave	Windows Desktop Systems	1	January 24th, 2003 6:12am
Domain Logon Screen Customize?	jhawks2266	Windows Desktop Systems	2	March 19th, 2002 11:08pm
Logon Errors	nicks	Windows Desktop Systems	5	February 25th, 2002 9:40pm

Latest News Posts

Latest Forum Posts

Latest Member Blogs

January 2nd, 2002	Top \| #2
JJB6486 Retired Mod Joined: December 2001 Location: West Lafayette, IN, USA Posts: 1,207 Reputation: 0 Power: 140	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

January 2nd, 2002	Top \| #3
chooch Unregistered Posts: n/a	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.

January 2nd, 2002	Top \| #4
MeanGene Unregistered Posts: n/a	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.

January 2nd, 2002	Top \| #5
chooch Unregistered Posts: n/a	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.

January 2nd, 2002	Top \| #6
MeanGene Unregistered Posts: n/a	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.

January 2nd, 2002	Top \| #7
Lonman Bleh! Joined: December 2001 Posts: 2,642 Reputation: 60 Power: 154	Here's an article about the error code you gave: http://support.microsoft.com/default...;EN-US;Q274320 Oops! here you go: http://support.microsoft.com/default...;EN-US;Q310461

January 2nd, 2002	Top \| #8
Lactic.Acid Unregistered Posts: n/a	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/directo...;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