Event ID 1054 Error

[tofuTnT]

Hi,
I am getting this error on all of WINXP computers on my network.

Event ID: 1054
Source: Userenv
Type: Error
Category: None

Description:
The description for Event ID ( 1054 ) in Source ( Userenv ) could not be found. It contains the following insertion string(s): The specified domain either does not exist or could not be contacted. .

When a user turns on his computer in the morning, Z: drive wasn't mapped to his Home Folder on a win2k server. He needs to log off then log on again. It is anonying.....
btw, his computer has other drives mapped on the shared folder on the server with a logon script, and that works fine.

Any idea why Z: drive wasn't mapped and why the event is logged? any way to solve it? I have tried everything I could find. no luck yet.

Thanks in advance,

Song

 

[bcastner]

Is this a brand new error that started suddenly, or a persistent issue with XP as client?

If the latter, you need to adjust the logon process to avoid issues with the default of asynchronous processing of the logon.

See the last paragraph of faq779-4017

 

[linney]

Any clues here?

http://www.eventid.net/display.asp?eventid=1054&source=userenv

 

[tofuTnT]

This problem is persistent issue with all the XP computers on the network.

The last paragraph of FAQ779-4017 has something similar to Microsoft Q305293. I made the change, it is now give me 1054 error event and none of the network drives is mapped.
The event says:

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.

I can ping my domain from the XP computer. ....


SOng

 

[linney]

Does this help?

298656 - Event ID 1054 Is Logged in the Application Event Log

http://support.microsoft.com/default.aspx?scid=kb;EN-US;298656&FR=1

 

[bcastner]

. Service Pack 1 installed, all clients?
. Netbios over TCP/IP enabled, all clients in TCP/IP Properties, Advanced, DNS tab?
. Your first message indicates a DNS error. The second a Netbios one. Make sure you follow paragraph #2 in faq779-4017 and have a single DNS entry for your local DNS server.