XP domain login prompt ready before network

From: KammRUDE (jtkammerud_at_charter.net)
Date: 04/28/04 

Date: 28 Apr 2004 14:19:37 -0700

I am having problems getting Windows XP Pro machines to accept network
logins immediately after booting up.

My network environment consists of say 30 Windows 98 machines and 20
Windows XP machines all logging into a Windows 2000 domain. I have
never had a problem with the Win98 machines only XP. Ever since I've
started implementing the XP machines into this environment I've been
impressed with their 20-30 sec. bootup time compared to the 98's >60
sec.; however it almost seems like the XP stations are booted up and
ready to go before the network connection is there. Immediately after
trying to login an error is returned: Login error "Domain ______ not
available". Because of its quickness in returning the message, I'm
lead to believe that it is not a DNS issue. Users will try multiple
times before it finally successfully logs them in to the domain, or
they will try once, come and get me and by the time I get there it
works just fine. So it really just seems to be a timing thing of only
about 30-45 sec.

I've tried several things like adjusting options in the Group Policy
including, but not limited to: "Always wait for the network at
computer startup and login" in the gpedit.msc, which really sounds
like it would do it for me, but alas it does not. It is now an on
going joke that if you can't login to XP, "Just wait longer!"

I've seen a few posts with similar problems, but not identical

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: RDC Failing from home to work???
    ... Jeffrey Randow (Windows Networking & Smart Display MVP) ... >> login screen but after I put in my username and password ... >> login...after I attempt to login I see the connection ... >> the same network from home. ...
    (microsoft.public.windowsxp.work_remotely)
  • 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: Account Logon Time Restriction
    ... attempt to see what all it can access via network shares. ... workstation from which the login originates. ... this recognizable as one of your machines? ... account's likely logged-into workstation, check if ...
    (microsoft.public.win2000.security)