1054 error - Windows cannot obtain the domain controller name for your computer

  • Thread starter Thread starter Chris
  • Start date Start date
C

Chris

I have noticed this error on a number of XP machines
recently. Client machines (in particular Dell GX270) are
not processing group policy properly, and seem to run very
slowly.

I am able to disconnect from the domain and rejoin, but
still get the message in event viewer. I have tried
updating the NIC driver (no resolution), and following the
steps outlined in Q326152 and Q239924, to no avail.

I see that a number of other people have reported this
problem on the Dell support forum, as well as it being
reported to Microsoft, but there is still no resolution.
One chap says that installing a second NIC in the machine
cures the problem, but we cant possibly do this on 100+
machines.

A resolution (not a workaround like the 2nd NIC idea)
would be very much appreciated.

CHRIS
 
Hi Chris,

I checked some internal information for you on this issue. It was indicated
that there was some problem on the Intel Pro 10/100/1000 NIC used on Dell
GX270. Windows XP has no problems.

These gigabits adapters fail to load the GPO from Windows 2000 DC to
Windows XP and give an event ID 1054. The Windows XP machines are also
experiencing intermittent network connectivity on the LAN since these
adapters have some problem in name resolution. After you successfully log
on you will normally be able to download policy by using GPUpdate.

According to our record, Dell has been engaged in this issue and has been
able to repro it. They along with Intel are working on an updated Driver
for the NIC card. I suggest you check with them to see if there is an
updated driver for your workstations.

Also, after reading the internal record, some customers resolved this issue
by update the driver from Dell. Thus, I suggest you try to download the
driver as well and contact Dell if this does not work.

Please let me know if this solves this issue or if you need further
assistance. I look forward to hearing from you.

Regards,

Eric Shen
Product Support Services
Microsoft Corporation

This posting is provided "AS IS" with no warranties, and confers no rights.

Get Secure! - www.microsoft.com/security

--------------------
| Content-Class: urn:content-classes:message
| From: "Chris" <[email protected]>
| Sender: "Chris" <[email protected]>
| Subject: 1054 error - Windows cannot obtain the domain controller name
for your computer
| Date: Fri, 7 Nov 2003 05:16:34 -0800
| Lines: 21
| Message-ID: <[email protected]>
| MIME-Version: 1.0
| Content-Type: text/plain;
| charset="iso-8859-1"
| Content-Transfer-Encoding: 7bit
| X-Newsreader: Microsoft CDO for Windows 2000
| Thread-Index: AcOlMV3/B05lpEddQNqRX8q1qncBIg==
| X-MimeOLE: Produced By Microsoft MimeOLE V5.50.4910.0300
| Newsgroups: microsoft.public.win2000.networking
| Path: cpmsftngxa06.phx.gbl
| Xref: cpmsftngxa06.phx.gbl microsoft.public.win2000.networking:44288
| NNTP-Posting-Host: TK2MSFTNGXA08 10.40.1.160
| X-Tomcat-NG: microsoft.public.win2000.networking
|
| I have noticed this error on a number of XP machines
| recently. Client machines (in particular Dell GX270) are
| not processing group policy properly, and seem to run very
| slowly.
|
| I am able to disconnect from the domain and rejoin, but
| still get the message in event viewer. I have tried
| updating the NIC driver (no resolution), and following the
| steps outlined in Q326152 and Q239924, to no avail.
|
| I see that a number of other people have reported this
| problem on the Dell support forum, as well as it being
| reported to Microsoft, but there is still no resolution.
| One chap says that installing a second NIC in the machine
| cures the problem, but we cant possibly do this on 100+
| machines.
|
| A resolution (not a workaround like the 2nd NIC idea)
| would be very much appreciated.
|
| CHRIS
|
 
Back
Top