slow login "applying personal settings", can't find domain controller?
We have one computer on the network (windows xp pro) which is logging users on very slowly.
The computer hangs at the "Applying Personal Settings" stage. After about two minutes it goes through.
I think there's some problem in talkign with the domain controller, and it is timing out. Event log has sone interesting items in it.
What can I do to fix this?
Event log below:
Userenv:
Windows cannot determine the user or computer name. (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.
Userenv:
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.
Autoenrollment:
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.
The computer hangs at the "Applying Personal Settings" stage. After about two minutes it goes through.
I think there's some problem in talkign with the domain controller, and it is timing out. Event log has sone interesting items in it.
What can I do to fix this?
Event log below:
Userenv:
Windows cannot determine the user or computer name. (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.
Userenv:
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.
Autoenrollment:
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.
ASKER CERTIFIED SOLUTION
membership
This solution is only available to members.
To access this solution, you must be a member of Experts Exchange.
rjdennis
Question: Does this machine have APC PowerChute software on it? I very recently had this issue and it was related to APC PowerChute. I had to install an update to PowerChute to resolve it.
SOLUTION
membership
This solution is only available to members.
To access this solution, you must be a member of Experts Exchange.
ASKER
The only strange software on this machine is Symantec Endpoint, pcAnywhere, and Microsoft Dynamics. The rest is the usual stuff - office, msn, etc.
overcld9 - the dns server is set the same as the gateway, which is 192.168.2.1. However, I suspect this might actually be the router, not the domain controller. I suspect the router is also our dhcp server. Should the DC also be a dns server which forwards to 192.168.2.1?
rjdennis - we do actually have an APC UPS. The powerchute software is not on this client, but it might be on the domain controller or fileserver, I would need to check.
tsun4mi7 - I'll try that. One question though, once I leave the domain, can I just join back to it or is there something special I'll have to do on the DC first to "allow" the computer to join? Or would it work if I just specified the admin password for the DC?
overcld9 - the dns server is set the same as the gateway, which is 192.168.2.1. However, I suspect this might actually be the router, not the domain controller. I suspect the router is also our dhcp server. Should the DC also be a dns server which forwards to 192.168.2.1?
rjdennis - we do actually have an APC UPS. The powerchute software is not on this client, but it might be on the domain controller or fileserver, I would need to check.
tsun4mi7 - I'll try that. One question though, once I leave the domain, can I just join back to it or is there something special I'll have to do on the DC first to "allow" the computer to join? Or would it work if I just specified the admin password for the DC?
SOLUTION
membership
This solution is only available to members.
To access this solution, you must be a member of Experts Exchange.
I had this issue with a few PCs today. It appeared that a large amount of data was being copied to the computer via the network.
What I did was type in the login credentials, then unplug the network cable, so that the PC would login straight away.
Just before the user went home, I asked them to log off, and then log on again, so that the computer would have all night to do whatever it's trying to do.
What I did was type in the login credentials, then unplug the network cable, so that the PC would login straight away.
Just before the user went home, I asked them to log off, and then log on again, so that the computer would have all night to do whatever it's trying to do.
I wonder if it was also slow when you opened programs such as ADUC and/or any other domain specific MMCs that may cause a bit of lag whilst propogating...