I see a lot of the same issues here in the forums but nobody seems to have an
answer. I just wanted to know if one was found before I burn $250 and call
MS.

Here is the issue...

About a month ago I started getting calls from my users stating that when
they login to the cached domain account it is taking any where from 4 to 7
minutes to get to the desktop after logging in.

I finally got my hands on a computer and they are right. The process is as
follows:
Laptop boots to ctrl-alt-delete login screen just fine and fast.
ctrl-alt-del and password is provided. Splash screen disappears immediately
after credentials are provided. Desktop background and mouse appear and this
is where it hangs. After about 7 minutes the laptop finally completes the
boot process and the user is able to control the laptop. It's almost as if
something in the OS is waiting for an extended amount of time for a domain
response then times out. Here are some facts and troubleshooting that I have
done:

Only happens when the domain cannot be found. If connected to domain
everything runs smooth.

It is account specific. If I login to the same computer with my account it
logs in fine on the domain and off the domain.

Deleteing and re-creating the profile does not work.

Only happens from a cold boot. Logging off then back on once the login
process has completed is fine.

Uninstalling all but the bare minimum of applications (IE virus prot,
office, adobe, etc) required to run does not fix the problem.

Imaging a brand new computer with the same image and same hardware produces
the same results with the same account (rules out hardware issues).

There is nothing fishy or bad going on in the event logs (only this one that
keeps popping up letting us know that the domain could not be found...duhhh).

Deleting all the files in the preload does not fix the problem.

Disconnecting all referencences to mapped drives does not fix the issue.

Virus scans and mal / ad ware sweepers come up clean.

There is no difference in AD as far as the accounts are concerned other than
mine is a domain admin (the users domain account is a local admin)

While creating a local profile fixes this, upper management will not allow
us to change the policy company wide (keep in mind I support upwards of 500
remote users).

Disabling the "Netlogon" service fixes the problem but domain resources
can't be found or used after this is disabled...obviously.

That is all I can think of off the top of my head. I have been banging on
this issue for 3 weeks now and it's coming to the point where my boss wants
me to fix or else heads are going to roll...namely mine. Does ANYONE have an
answer for this? It only started a few weeks ago, up until then everyone was
fine.

Any help would be appreciated...

"Daniel G." <DanielG@discussions.microsoft.com> wrote in message
news:67F302C2-397F-4DA3-9704-3CEFE944C85E@microsoft.com...
> I see a lot of the same issues here in the forums but nobody seems to have
an
> answer. I just wanted to know if one was found before I burn $250 and
call
> MS.
>
> Here is the issue...
>
> About a month ago I started getting calls from my users stating that when
> they login to the cached domain account it is taking any where from 4 to 7
> minutes to get to the desktop after logging in.
>
> I finally got my hands on a computer and they are right. The process is
as
> follows:
> Laptop boots to ctrl-alt-delete login screen just fine and fast.
> ctrl-alt-del and password is provided. Splash screen disappears
immediately
> after credentials are provided. Desktop background and mouse appear and
this
> is where it hangs. After about 7 minutes the laptop finally completes the
> boot process and the user is able to control the laptop. It's almost as
if
> something in the OS is waiting for an extended amount of time for a domain
> response then times out. Here are some facts and troubleshooting that I
have
> done:
>
> Only happens when the domain cannot be found. If connected to domain
> everything runs smooth.
>
> It is account specific. If I login to the same computer with my account
it
> logs in fine on the domain and off the domain.
>
> Deleteing and re-creating the profile does not work.
>
> Only happens from a cold boot. Logging off then back on once the login
> process has completed is fine.
>
> Uninstalling all but the bare minimum of applications (IE virus prot,
> office, adobe, etc) required to run does not fix the problem.
>
> Imaging a brand new computer with the same image and same hardware
produces
> the same results with the same account (rules out hardware issues).
>
> There is nothing fishy or bad going on in the event logs (only this one
that
> keeps popping up letting us know that the domain could not be
found...duhhh).
>
> Deleting all the files in the preload does not fix the problem.
>
> Disconnecting all referencences to mapped drives does not fix the issue.
>
> Virus scans and mal / ad ware sweepers come up clean.
>
> There is no difference in AD as far as the accounts are concerned other
than
> mine is a domain admin (the users domain account is a local admin)
>
> While creating a local profile fixes this, upper management will not allow
> us to change the policy company wide (keep in mind I support upwards of
500
> remote users).
>
> Disabling the "Netlogon" service fixes the problem but domain resources
> can't be found or used after this is disabled...obviously.
>
> That is all I can think of off the top of my head. I have been banging on
> this issue for 3 weeks now and it's coming to the point where my boss
wants
> me to fix or else heads are going to roll...namely mine. Does ANYONE have
an
> answer for this? It only started a few weeks ago, up until then everyone
was
> fine.
>
> Any help would be appreciated...

In most cases this problem is caused by inappropriate DNS settings
which cause the workstation to range far and wide on the Internet
for the location of the validating domain controller.