Re: XP pro takes a long time to boot on Win 2K network

Tech Tip: Click here to run a free scan for Windows Errors and optimize PC performance

Ensure that you have good DNS name resolution in your environment.
All Windows XP clients should point to an internal DNS server that is
authoritative for the domain.

If that is OK, then you might want to enable UserEnv logging
and take a network trace to see where the delay is:

How to Enable User Environment Debug Logging in Retail Builds of Windows
http://support.microsoft.com/D­efault.aspx?id=221833

Description of the Windows XP Professional Fast Logon Optimization Feature
http://support.microsoft.com/default.aspx?scid=kb;en-us;305293&Product=winxp

Logon Optimization
http://msdn.microsoft.com/library/default.asp?url=/library/en-us/policy/policy/logon_optimization.asp

Slow logon to domain in XP Pro
http://www.tweakxp.com/article139785.aspx

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

Get Windows XP Service Pack 2 with Advanced Security Technologies:
http://www.microsoft.com/athome/security/protect/windowsxp/choose.mspx

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

"BMN" wrote:

| I have deployed 3 new XP Pro machines on a W2K network and they all
| hang up for about 2 minutes at "applying personal settings".
|
| I am using our ISP's DNS servers and statically assigned IP addresses
| on the workstations (that's the way I inherited this network) and it
| is a mix of 98 and XP units now. The network doesn't use profiles so
| it isn't the machine downloading the users profile from the server on
| bootup.
|
| Once the machine boots up it operates fine. These are new machines
| with just the basic in-house applications so spyware and apps running
| in the background are not an issue. I am wondering if it has something
| to do with security policies or the DNS server not being internal to
| the network or something to do with the AD not being setup properly?
|
| All suggestions are welcome!
| TIA

.

Relevant Pages

  • Re: Windows XP; Windows 98 & Windows NT 4.0 compatability
    ... >3) ICF is DISABLED on the XP Machines ... >4) I'm not quite sure what you mean on file sharing. ... >obviously I can see the XP machines on the 98 Network ... Windows XP is the latest attempt to merge the Windows 9x product line ...
    (microsoft.public.windowsxp.network_web)
  • Re: Is a Windows 98se computer more, or less, of a security threat with IE 5.5 (unused) & Firefo
    ... We aren't using any Windows ME machines at all. ... That might be a better solution, however Windows 98 does not support ... He's very knowledgable about network security, ...
    (microsoft.public.windowsupdate)
  • Re: File sharing fails.
    ... Still no working network is obvious.. ... Problems sharing files between computers on a network are generally caused by 1) a misconfigured firewall; or 2) inadvertently running two firewalls such as the built-in Windows Firewall and a third-party firewall; and/or 3) not having identical user accounts and passwords on all Workgroup machines; 4) trying to create shares where the operating system does not permit it. ...
    (microsoft.public.windowsxp.basics)
  • Re: paging all socket geniuses
    ... Windows, my laptop, or me or all three are... ... about the absence of a network... ... Ping was a nice courtesy of a tamer Internet of the past. ... machines and firewalls are configured to block all ICMP traffic (which ...
    (comp.lang.lisp)
  • Re: File sharing fails.
    ... I have Windows XP professional on each of two machines in my study. ... Still no working network is obvious.. ... caused by 1) a misconfigured firewall; ...
    (microsoft.public.windowsxp.basics)