slow logon

How can I shorten the amount of time it takes for my XP
workstations to log on to my 2003 server? These same
workstations can log on to an NT 4 server in less than 30
seconds while it takes over 2 minutes with the 2003 server

quoted from http://www.ChicagoTech.net
Why is XP running slower while logon 1

When I login into a Windows 2000 active directory from a new xp pro machine
the login in is extremely slow. After logged on, everything works fine. But
other windows versions don't have this problem.
A: This is almost like name resolution issue. Comparing with previous
versions, XP is heavily dependent on DNS to find DC. If the DNS is
configured incorrectly, XP will take longer time waiting for it to timeout
before it tries using NetBIOS. Make sure
1) The DNS setup correct and have the server information.
2) XP clients can find the DNS server.
3) XP machine's DNS server is pointed to your internal DNS server rather
than your ISP's DNS server.
4) Make sure no errors on logon scripts or GPO's that could be causing
the delay.
5) Check any errors on event viewer.
6) Disable NetBIOS on the interfaces that client will not use.

--
For more and other information, go to http://www.ChicagoTech.net

Don't send e-mail or reply to me except you need consulting services.
Posting on MS newsgroup will benefit all readers and you may get more help.

Robert Lin, MS-MVP, MCSE & CNE
Networking, Internet, Routing, VPN, Anti-Virus, Tips & Troubleshooting on
http://www.ChicagoTech.net
This posting is provided "AS IS" with no warranties.

"Todd" <(E-Mail Removed)> wrote in message
news:22af01c49a92$e4e43400$(E-Mail Removed)...
> How can I shorten the amount of time it takes for my XP
> workstations to log on to my 2003 server? These same
> workstations can log on to an NT 4 server in less than 30
> seconds while it takes over 2 minutes with the 2003 server

>-----Originalnachricht-----
>quoted from http://www.ChicagoTech.net
>Why is XP running slower while logon 1
>
>When I login into a Windows 2000 active directory from a
new xp pro machine
>the login in is extremely slow. After logged on,
everything works fine. But
>other windows versions don't have this problem.
>A: This is almost like name resolution issue. Comparing
with previous
>versions, XP is heavily dependent on DNS to find DC. If
the DNS is
>configured incorrectly, XP will take longer time waiting
for it to timeout
>before it tries using NetBIOS. Make sure
>1) The DNS setup correct and have the server information.
>2) XP clients can find the DNS server.
>3) XP machine's DNS server is pointed to your internal
DNS server rather
>than your ISP's DNS server.
>4) Make sure no errors on logon scripts or GPO's
that could be causing
>the delay.
>5) Check any errors on event viewer.
>6) Disable NetBIOS on the interfaces that client will not
use.

Hi!

I don't think that's the problem. I have the same problem
here. I have a W2K3 server and many many XP clients
(Virtual Machines). Every machine will be used only
_once_! You guess my problem: For this machines it is
always the first login. It takes up to 60 seconds. The
second login takes only 5.

If one of the things above would match, I would have the
long login time _every_ login and not only the first one.

So the question is:
What does WinXP do when a user logs in the first time? And
how can I disable these things?

Bye the way:
I have the same long login time when logging in from a
W2K3 server.

- Dani

I have similar problem. If I redirect "My Documents" to a network share, it
takes longer for first logon, about 20 seconds. So I enable the fdeploy debug
log. It seems fdeploy uses about 20 seconds to update "My Pictures" shortcut.

------ fdeploay.log -------
15:06:45:930 Successfully redirected folder Application Data. The folder as
redirected from ....
15:07:06:188 Successfully updated the shortcut to My Pictures in ...
-----------------------------

I'm still looking for a solution.

Jack

"Dani" wrote:

> >-----Originalnachricht-----
> >quoted from http://www.ChicagoTech.net
> >Why is XP running slower while logon 1
> >
> >When I login into a Windows 2000 active directory from a
> new xp pro machine
> >the login in is extremely slow. After logged on,
> everything works fine. But
> >other windows versions don't have this problem.
> >A: This is almost like name resolution issue. Comparing
> with previous
> >versions, XP is heavily dependent on DNS to find DC. If
> the DNS is
> >configured incorrectly, XP will take longer time waiting
> for it to timeout
> >before it tries using NetBIOS. Make sure
> >1) The DNS setup correct and have the server information.
> >2) XP clients can find the DNS server.
> >3) XP machine's DNS server is pointed to your internal
> DNS server rather
> >than your ISP's DNS server.
> >4) Make sure no errors on logon scripts or GPO's
> that could be causing
> >the delay.
> >5) Check any errors on event viewer.
> >6) Disable NetBIOS on the interfaces that client will not
> use.
>
> Hi!
>
> I don't think that's the problem. I have the same problem
> here. I have a W2K3 server and many many XP clients
> (Virtual Machines). Every machine will be used only
> _once_! You guess my problem: For this machines it is
> always the first login. It takes up to 60 seconds. The
> second login takes only 5.
>
> If one of the things above would match, I would have the
> long login time _every_ login and not only the first one.
>
> So the question is:
> What does WinXP do when a user logs in the first time? And
> how can I disable these things?
>
> Bye the way:
> I have the same long login time when logging in from a
> W2K3 server.
>
> - Dani
>

Hi,

I seem to be having the same problem. Except *every* logon takes longer
when the folder redirection policy is being applied. (Maybe because
group policy is set to clear cached profiles?)

Going through the debug log I've noticed the 20 seconds myself.. and
thought it was something to do with 'My Pictures' folder. But I also
redirect the desktop and application data. I tried with different sets
of redirected folders and its always the second entry that shows the 20
second delay. (It just happened to be My Pictures the first time).

One thing to note is that if the group policy is disabled or unlinked
but the option to keep redirection after it is removed is set, the
folders will still redirect and the logon will be faster. (The problem
with that is that new accounts will need to have this policy applied at
least the first time they logon for fdeploy to create and move these
folders to the redirected location. Same applies to users that have
their profiles cleared).

If anyone has come accross this and has any hints or solutions.... your
help would be greatly appreciated.

Jimmy

After further testing I'm quite certain that redirecting 'My Documents'
is the cause of the delay.

Note: We are using Windows Server 2003 and the workstations are XP Pro
SP1 ( I also tested it with SP2, same problem).

Jimmy

(E-Mail Removed) wrote:
> Hi,
>
> I seem to be having the same problem. Except *every* logon takes
longer
> when the folder redirection policy is being applied. (Maybe because
> group policy is set to clear cached profiles?)
>
> Going through the debug log I've noticed the 20 seconds myself.. and
> thought it was something to do with 'My Pictures' folder. But I also
> redirect the desktop and application data. I tried with different
sets
> of redirected folders and its always the second entry that shows the
20
> second delay. (It just happened to be My Pictures the first time).
>
> One thing to note is that if the group policy is disabled or unlinked
> but the option to keep redirection after it is removed is set, the
> folders will still redirect and the logon will be faster. (The
problem
> with that is that new accounts will need to have this policy applied
at
> least the first time they logon for fdeploy to create and move these
> folders to the redirected location. Same applies to users that have
> their profiles cleared).
>
> If anyone has come accross this and has any hints or solutions....
your
> help would be greatly appreciated.
>
> Jimmy