Re: XP domain login prompt ready before network

From: Stephen (paybak_at_charter.net)
Date: 04/29/04 

Date: Thu, 29 Apr 2004 10:05:00 +1000

Try forcing the NIC speed, check the Windows bindings, set the dns to the
server IP, fixed IP addresses, current patches (and remove faulty ones -
April last year), see kb321098.
All this info available on http://www.smallbizserver.net/ under SBS2000

If all this doesn't work, give us more information (SP revs etc, Server O/S
type & specs)

Stephen

"KammRUDE" <jtkammerud@charter.net> wrote in message
news:730e51b6.0404281319.4e0b68be@posting.google.com...
> 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: NT Domain to AD migration
    ... Windows 2000/XP always prefer Kerberos authentication, ... Server 2003 Active Directory service, ensure that you have designed a DNS ...
    (microsoft.public.windows.server.active_directory)
  • Re: Find AD hostname from Linux command line
    ... The Windows XP workstation gets an IP ... "Register this connection's addresses in DNS" turned ON. ... If I am on a Linux server and do "ping lancelot.ad.mydomain.com", ...
    (microsoft.public.win2000.dns)
  • Re: How to enable communication between Two different lans (subnets)/ domains 2003 server based? Ass
    ... You will also almost certainly have DNS problems running a domain behind ... server domain, with a DHCP server running on one of the 2003 boxes. ... the "inner" subnet can see the original subnet and the Internet, ... The .227 machines can see the machines on the 192.168.1.0 subnet and the ...
    (microsoft.public.windows.server.networking)
  • Re: Two Win2k3 questions ... Roaming Profiles & Access Privileges ...
    ... >DHCP, DNS, Print Server, and File Server responsibilities. ... lookup zone on Windows NT" ... http://support.microsoft.com?kbid=229873 "Delegate Control Wizard Cannot Be Used ...
    (microsoft.public.win2000.advanced_server)
  • RE: Dynamic Update of A&PTR Records - Best Practice?
    ... The DNS server does not support the DNS dynamic update protocol; ... For Windows Server 2003-based computers, the primary full computer name is ... When one of these events triggers a DNS update, the DHCP Client service, ...
    (microsoft.public.windows.server.dns)