"Deanna" <Dea***@discussions.microsoft.com> wrote in message
news:2A9BB072-DA7B-4CEA-9BA3-8DD564449C62@microsoft.com...
>I have a workstation that was just rebuilt with Windows XP SP2 that has
>been
> joined to the existing Windows 2003 domain.
>
> If a user that has a logon script designated in their AD properties on the
> Profile tab as well as a Home Directory specified on the same tab, there
> is a
> delay of about 15 minutes for the logon of that user to complete.  Any
> user
> (administraotr or non-administrator) that does not have those two items
> configured can log on successfully with no delay.  If the logon script is
> the
> only component configured on the Profile tab then the user can log on but
> the
> drives from the logon script are not mapped.  If the Home Directory is the
> only component configured on the Profile tab then the logon is delayed
> slightly (1-2 minutes), the directory is mapped and accessible, and event
> ids
> 1053, 40960, and 40961 are logged.
>
> The rest of the network is functioning correctly and the issues stated
> above
> seem to only affect new workstations on the domain.  Any help would be
> appreciated.
>
> Deanna

"Richard G. Harper" wrote:

> The most common cause of slow logins on AD is misconfigured DNS - all domain
> clients should use only a domain DNS server, domain DNS servers should
> resolve all external address requests via forwarding or root hint servers.
>
> --
> Richard G. Harper [MVP Shell/User]  rghar***@gmail.com
> * NEW! Catch my blog ... http://msmvps.com/blogs/rgharper/
> * PLEASE post all messages and replies in the newsgroups
> * The Website - http://rgharper.mvps.org/
> * HELP us help YOU ... http://www.dts-l.org/goodpost.htm
>
>
> "Deanna" <Dea***@discussions.microsoft.com> wrote in message
> news:2A9BB072-DA7B-4CEA-9BA3-8DD564449C62@microsoft.com...
> >I have a workstation that was just rebuilt with Windows XP SP2 that has
> >been
> > joined to the existing Windows 2003 domain.
> >
> > If a user that has a logon script designated in their AD properties on the
> > Profile tab as well as a Home Directory specified on the same tab, there
> > is a
> > delay of about 15 minutes for the logon of that user to complete.  Any
> > user
> > (administraotr or non-administrator) that does not have those two items
> > configured can log on successfully with no delay.  If the logon script is
> > the
> > only component configured on the Profile tab then the user can log on but
> > the
> > drives from the logon script are not mapped.  If the Home Directory is the
> > only component configured on the Profile tab then the logon is delayed
> > slightly (1-2 minutes), the directory is mapped and accessible, and event
> > ids
> > 1053, 40960, and 40961 are logged.
> >
> > The rest of the network is functioning correctly and the issues stated
> > above
> > seem to only affect new workstations on the domain.  Any help would be
> > appreciated.
> >
> > Deanna
>
>
>

"Robert L [MVP - Networking]" wrote:

> Try to delete the problem computer from DNS records and re-create it. Or this search result may help,
>
> Event ID TroubleshootingEvent ID 1053 - Userenv Event ID 1054 - Windows cannot obtain the domain ... Symptoms: your w2k/xp clients may receive this Event ID 1053 - Windows cannot ...
>       www.chicagotech.net/wineventid.htm
>
>
> Bob Lin, MS-MVP, MCSE & CNE
> Networking, Internet, Routing, VPN Troubleshooting on http://www.ChicagoTech.net
> How to Setup Windows, Network, VPN & Remote Access on http://www.HowToNetworking.com
>   "Deanna" <Dea***@discussions.microsoft.com> wrote in message news:2A9BB072-DA7B-4CEA-9BA3-8DD564449C62@microsoft.com...
>   I have a workstation that was just rebuilt with Windows XP SP2 that has been
>   joined to the existing Windows 2003 domain. 
>
>   If a user that has a logon script designated in their AD properties on the
>   Profile tab as well as a Home Directory specified on the same tab, there is a
>   delay of about 15 minutes for the logon of that user to complete.  Any user
>   (administraotr or non-administrator) that does not have those two items
>   configured can log on successfully with no delay.  If the logon script is the
>   only component configured on the Profile tab then the user can log on but the
>   drives from the logon script are not mapped.  If the Home Directory is the
>   only component configured on the Profile tab then the logon is delayed
>   slightly (1-2 minutes), the directory is mapped and accessible, and event ids
>   1053, 40960, and 40961 are logged.
>
>   The rest of the network is functioning correctly and the issues stated above
>   seem to only affect new workstations on the domain.  Any help would be
>   appreciated.
>
>   Deanna