Userenv errors on Clients

We replaced an NTServer DC with a Windows 2003 DC on a small network
(less than 5 PCs). We joined the XP PCs to the new Domain Controller
without any issues. The PCs set overnight and were "locked up" the
next morning...that is they could not navigate mapped drives.

We found the following error in each XP PC, occurring about every hour
throughout the night:

Userenv - Events 1054 & 1053. With description similar to (sorry, do
not have exact text handy) Windows cannot obtain domain controller
name....Group Poliy processing aborted.

Also, there are Auto Enrollment errors, Event 15.

We rebooted each PC and logged into the domain again and everything is
ok for now.

Any ideas?

On Jul 24, 9:21*am, compsos...@gmail.com wrote:
> We replaced an NTServer DC with a Windows 2003 DC on a small network
> (less than 5 PCs). We joined the XP PCs to the new Domain Controller
> without any issues. The PCs set overnight and were "locked up" the
> next morning...that is they could not navigate mapped drives.
>
> We found the following error in each XP PC, occurring about every hour
> throughout the night:
>
> Userenv - Events 1054 & 1053. With description similar to (sorry, do
> not have exact text handy) Windows cannot obtain domain controller
> name....Group Poliy processing aborted.
>
> Also, there are Auto Enrollment errors, Event 15.
>
> We rebooted each PC and logged into the domain again and everything is
> ok for now.
>
> Any ideas?

Additional Info:

We run the 2003 Server as a DC, File Server & DNS Server.
The Server & XP Clients have static IP addresses assigned.
The Primary DNS is left empty on the clients -- could this be the
issue?

for example, the TCP/IP properties look like this on a client:

IP: 192.168.1.x
SN: 255.255.255.0
DNS - empty
Gateway - empty

No computers use the Internet --including the server.

Hello (E-Mail Removed),

Answered to m.p.w.s.dns and please do not multipost, use crossposting.

Best regards

Meinolf Weber
Disclaimer: This posting is provided "AS IS" with no warranties, and confers
no rights.
** Please do NOT email, only reply to Newsgroups
** HELP us help YOU!!! http://www.blakjak.demon.co.uk/mul_crss.htm

> We replaced an NTServer DC with a Windows 2003 DC on a small network
> (less than 5 PCs). We joined the XP PCs to the new Domain Controller
> without any issues. The PCs set overnight and were "locked up" the
> next morning...that is they could not navigate mapped drives.
>
> We found the following error in each XP PC, occurring about every hour
> throughout the night:
>
> Userenv - Events 1054 & 1053. With description similar to (sorry, do
> not have exact text handy) Windows cannot obtain domain controller
> name....Group Poliy processing aborted.
>
> Also, there are Auto Enrollment errors, Event 15.
>
> We rebooted each PC and logged into the domain again and everything is
> ok for now.
>
> Any ideas?
>

On Jul 24, 10:31*am, Meinolf Weber <meiweb(nospam)@gmx.de> wrote:
> Hello compsos...@gmail.com,
>
> Answered to m.p.w.s.dns and please do not multipost, use crossposting.
>
> Best regards
>
> Meinolf Weber
> Disclaimer: This posting is provided "AS IS" with no warranties, and confers
> no rights.
> ** Please do NOT email, only reply to Newsgroups
> ** HELP us help YOU!!!http://www.blakjak.demon.co.uk/mul_crss.htm
>
>
>
> > We replaced an NTServer DC with a Windows 2003 DC on a small network
> > (less than 5 PCs). We joined the XP PCs to the new Domain Controller
> > without any issues. The PCs set overnight and were "locked up" the
> > next morning...that is they could not navigate mapped drives.
>
> > We found the following error in each XP PC, occurring about every hour
> > throughout the night:
>
> > Userenv - Events 1054 & 1053. With description similar to (sorry, do
> > not have exact text handy) Windows cannot obtain domain controller
> > name....Group Poliy processing aborted.
>
> > Also, there are Auto Enrollment errors, Event 15.
>
> > We rebooted each PC and logged into the domain again and everything is
> > ok for now.
>
> > Any ideas?- Hide quoted text -
>
> - Show quoted text -

Thank you for the replies...Adding the Primary DNS info solved it. I
thought that was what the DNS Server role on the DC provided to the
clients? Maybe if it is not a DHCP Server as well??

How does one crosspost?
Thanks

Hello (E-Mail Removed),

If you do setup fixed ip addresses, you have to set it by hand and if you
use a DHCP server you have to configure the scope options in the DHCP management
console with at least DNS server of the domain, if the machines need to access
another network or subnet for example Internet, you have also to set the
Default Gateway.

Crossposting you can do with a newsreader like Outlook express or some other
freeware readers. There you can choose all NG's you like and post the message
to all groups together. Advantage, anybody can read all replies from anybody
and has the full story, so that no double answeres exist in the different
NG's. Also easier for you to read the answers.

Best regards

Meinolf Weber
Disclaimer: This posting is provided "AS IS" with no warranties, and confers
no rights.
** Please do NOT email, only reply to Newsgroups
** HELP us help YOU!!! http://www.blakjak.demon.co.uk/mul_crss.htm

> On Jul 24, 10:31 am, Meinolf Weber <meiweb(nospam)@gmx.de> wrote:
>
>> Hello compsos...@gmail.com,
>>
>> Answered to m.p.w.s.dns and please do not multipost, use
>> crossposting.
>>
>> Best regards
>>
>> Meinolf Weber
>> Disclaimer: This posting is provided "AS IS" with no warranties, and
>> confers
>> no rights.
>> ** Please do NOT email, only reply to Newsgroups
>> ** HELP us help YOU!!!http://www.blakjak.demon.co.uk/mul_crss.htm
>>> We replaced an NTServer DC with a Windows 2003 DC on a small network
>>> (less than 5 PCs). We joined the XP PCs to the new Domain Controller
>>> without any issues. The PCs set overnight and were "locked up" the
>>> next morning...that is they could not navigate mapped drives.
>>>
>>> We found the following error in each XP PC, occurring about every
>>> hour throughout the night:
>>>
>>> Userenv - Events 1054 & 1053. With description similar to (sorry, do
>>> not have exact text handy) Windows cannot obtain domain controller
>>> name....Group Poliy processing aborted.
>>>
>>> Also, there are Auto Enrollment errors, Event 15.
>>>
>>> We rebooted each PC and logged into the domain again and everything
>>> is ok for now.
>>>
>>> Any ideas?- Hide quoted text -
>>>
>> - Show quoted text -
>>
> Thank you for the replies...Adding the Primary DNS info solved it. I
> thought that was what the DNS Server role on the DC provided to the
> clients? Maybe if it is not a DHCP Server as well??
>
> How does one crosspost?
> Thanks

Hi Meinolf,

I think the problem here was that the OP was coming from NT! He did not
realise how important DNS is, and that the clients use DNS to find the DC.
In NT they use the special Netbios name to find the logon server.

"Meinolf Weber" <meiweb(nospam)@gmx.de> wrote in message
news:(E-Mail Removed) .com...
> Hello (E-Mail Removed),
>
> If you do setup fixed ip addresses, you have to set it by hand and if you
> use a DHCP server you have to configure the scope options in the DHCP
> management console with at least DNS server of the domain, if the machines
> need to access another network or subnet for example Internet, you have
> also to set the Default Gateway.
>
> Crossposting you can do with a newsreader like Outlook express or some
> other freeware readers. There you can choose all NG's you like and post
> the message to all groups together. Advantage, anybody can read all
> replies from anybody and has the full story, so that no double answeres
> exist in the different NG's. Also easier for you to read the answers.
>
> Best regards
>
> Meinolf Weber
> Disclaimer: This posting is provided "AS IS" with no warranties, and
> confers no rights.
> ** Please do NOT email, only reply to Newsgroups
> ** HELP us help YOU!!! http://www.blakjak.demon.co.uk/mul_crss.htm
>
>> On Jul 24, 10:31 am, Meinolf Weber <meiweb(nospam)@gmx.de> wrote:
>>
>>> Hello compsos...@gmail.com,
>>>
>>> Answered to m.p.w.s.dns and please do not multipost, use
>>> crossposting.
>>>
>>> Best regards
>>>
>>> Meinolf Weber
>>> Disclaimer: This posting is provided "AS IS" with no warranties, and
>>> confers
>>> no rights.
>>> ** Please do NOT email, only reply to Newsgroups
>>> ** HELP us help YOU!!!http://www.blakjak.demon.co.uk/mul_crss.htm
>>>> We replaced an NTServer DC with a Windows 2003 DC on a small network
>>>> (less than 5 PCs). We joined the XP PCs to the new Domain Controller
>>>> without any issues. The PCs set overnight and were "locked up" the
>>>> next morning...that is they could not navigate mapped drives.
>>>>
>>>> We found the following error in each XP PC, occurring about every
>>>> hour throughout the night:
>>>>
>>>> Userenv - Events 1054 & 1053. With description similar to (sorry, do
>>>> not have exact text handy) Windows cannot obtain domain controller
>>>> name....Group Poliy processing aborted.
>>>>
>>>> Also, there are Auto Enrollment errors, Event 15.
>>>>
>>>> We rebooted each PC and logged into the domain again and everything
>>>> is ok for now.
>>>>
>>>> Any ideas?- Hide quoted text -
>>>>
>>> - Show quoted text -
>>>
>> Thank you for the replies...Adding the Primary DNS info solved it. I
>> thought that was what the DNS Server role on the DC provided to the
>> clients? Maybe if it is not a DHCP Server as well??
>>
>> How does one crosspost?
>> Thanks
>
>