General discussion

Locked

Windows 2000 and XP Pro network issue

By CountyIT ·
I have 5 servers and over 60 workstations on my network....2 days ago 5
machines could not access resources from 1 server...all 5 workstations had
the same messages in their error logs....see below. None of the servers
showed any errors. I have checked the the net and links below with no
solutions. Thanks in advance.

Event Type: Error
Event Source: Userenv
Event Category: None
Event I 1053
Date: 1/20/2005
Time: 12:06:52 PM
User: NT AUTHORITY\SYSTEM
Computer: GISER
Description:
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.


Event Type: Error
Event Source: AutoEnrollment
Event Category: None
Event I 15
Date: 1/20/2005
Time: 10:32:50 AM
User: N/A
Computer: GISER
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 I 1054
Date: 1/20/2005
Time: 10:31:50 AM
User: NT AUTHORITY\SYSTEM
Computer: GISER
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.

This conversation is currently closed to new comments.

6 total posts (Page 1 of 1)  
| Thread display: Collapse - | Expand +

All Comments

Collapse -

by p.j.hutchison In reply to Windows 2000 and XP Pro n ...

The computer account may have been deleted, renamed or reset. Remove the PCS from the domain and re-add them again to fix it.

Collapse -

by XSive In reply to Windows 2000 and XP Pro n ...

My first port of call here would be to check the DNS settings on the server and clients to make sure they are pointing to the authoritative server for the domain.
If this is correct then the problem may be with the network card drivers on the server. try updating the driver.
Windows can sometimes unbind protocols from adapters if it thinks the link state is not 'up' which would cause the symptoms you describe, you can prevent this by disabling media sense on the tcp/ip protocol (see http://support.microsoft.com/kb/239924)

Hope this helps and good luck.
Xs

Collapse -

by Blackcurrant In reply to Windows 2000 and XP Pro n ...

Hi

Also check your hardware. We use two switches, one of which is used just for three machines - all three machines could not connect to the network - the switch needed to be turned off then turned on again.

Good luck

Collapse -

by NetTek In reply to Windows 2000 and XP Pro n ...

I have seen antivirus software on the server cause this problem.

Stop your antivirus services on your server and see if that resolves the issue. It is does, check with your av provider for a patch.

Collapse -

by ewgny In reply to Windows 2000 and XP Pro n ...

Do these workstations have gigabit ethernet cards ? Are they connected to a switch or a hub ?
what are the brand PC's, NIC cards and type of switc/hub ? Some Gig NIC cards have trouble when connected to a switch, particularly a problem when the switch has spanning tree protocol enabled. This trouble can start with the NIC causing the switch to delay making the port available in time for windows to recognize that it is connected to a network thus the errors. Answer my questions, and I may be able to give you more specific info regarding your problem

Collapse -

by Doc598 In reply to Windows 2000 and XP Pro n ...

I would agree with p.j.hutchison's suggestion. It appears that the computer accounts have been deleted from AD. To fix it I would would remove the computer from Active Directory by joining them to a workgroup. Then look in AD Users and Computers and make sure the computers do not appear in there any longer. Then rejoin them to the domain and this will create new accounts and should connect without any problems.

Back to Windows Forum
6 total posts (Page 1 of 1)  

Related Discussions

Related Forums