Time to log onto Server 2K

How can I decrease Time to log onto Server 2K:

It happens when I upgraded my workstation Win2K with WinXP.
I formatted my Hard disk and installed again WinXP Pro to
solve the problem,
But failed.


Loading your personal settings
Applying your personal settings
Applying computer settings

Description of the Windows XP Professional Fast Logon Optimization Feature
http://support.microsoft.com/default...&Product=winxp

Logon Optimization
http://msdn.microsoft.com/library/de...timization.asp


--
Carey Frisch
Microsoft MVP
Windows XP - Shell/User

------------------------------------------------------------------------------

"Mehmood" <mehmoood@hotmail.com> wrote in message:
news:0a5101c38e4c$c6737560$a401280a@phx.gbl...

| How can I decrease Time to log onto Server 2K:
|
| It happens when I upgraded my workstation Win2K with WinXP.
| I formatted my Hard disk and installed again WinXP Pro to
| solve the problem,
| But failed.
|
|
| Loading your personal settings
| Applying your personal settings
| Applying computer settings
|

"Mehmood" <mehmoood@hotmail.com> wrote in message
news:0a5101c38e4c$c6737560$a401280a@phx.gbl...

> How can I decrease Time to log onto Server 2K:
>
> It happens when I upgraded my workstation Win2K with WinXP.
> I formatted my Hard disk and installed again WinXP Pro to
> solve the problem,
> But failed.
>
>
> Loading your personal settings
> Applying your personal settings
> Applying computer settings
>

Slow logons to a win2k domain usually indicate a DNS problem.

XP differs from previous versions of windows in that it uses
DNS as it's primary name resolution method for finding domain
controllers:

How Domain Controllers Are Located in Windows XP
http://support.microsoft.com/default...b;en-us;314861

If DNS is misconfigured, XP will spend a lot of time waiting for it to
timeout before it tries using legacy NT4 sytle NetBIOS.
( Which may or may not work. )

1) Ensure that the XP clients are all configured to point to the local
DNS server which hosts the AD domain. That will probably be the
win2k server itself.
They should NOT be pointing an an ISP's DNS server.
An 'ipconfig /all' on the XP box should reveal ONLY the domain's
DNS server.

( you should use the DHCP server to push out the local DNS server
address. )

2) Ensure DNS server on win2k is configured to permit dynamic updates.

3) Ensure the win2k server points to itself as a DNS server.

4) For external ( internet ) name resolution, specify your ISP's DNS server
not on the clients, but in the 'forwarders' tab of the local win2k DNS
server.

On the DNS server, if you cannot access the 'Forwarders' and 'Root Hints'
tabs because they are greyed out, that is because there is a root zone (".")
present on the DNS server. You MUST delete this root zone to permit the
server to forward unresolved queries to yout ISP or the root servers.
Accept any nags etc, and let it delete any corresponding reverse lookuop
zones if it asks.


The following articles may assist you in setting up DNS correctly:

Setting Up the Domain Name System for Active Directory
http://support.microsoft.com/default...b;en-us;237675
HOW TO: Configure DNS for Internet Access in Windows 2000
http://support.microsoft.com/default...b;en-us;300202
DNS and AD FAQs:
http://support.microsoft.com/?id=291382


--
Best Regards
Ron Lowe
MVP - Windows Networking