Re: Windows cannot connect to the domain

First verify that the domain controller is running and functioning normally.
Look to see if it shows any errors/warnings in the event logs that can be
seen via Event Viewer. Make sure you can ping the domain controller via name
and IP address from your domain computers. If all computers are having a
problem then try rebooting the domain controller. Read the link below on
Active Directory DNS and make sure you follow it's recommendations as DNS
problems are a major reason of problems like your with using ISP DNS server
as a preferred DNS server being on top of the list. Domain workstations must
point only to domain controllers as their preferred DNS servers as shown via
the command ipconfig /all. You can also use the support tool netdiag on any
domain computer to check for domain/networking problems and dcdiag and
gpotool on domain controllers. When you use nslookup on any domain computer
and enter your domain name [mydomain.com] it should resolve to the IP
addresses of your domain controllers. That should get you started. ---
Steve

http://support.microsoft.com/default.aspx?scid=kb%3Ben-us%3B291382

"Vincent Low" <VincentLow@xxxxxxxxxxxxxxxxxxxxxxxxx> wrote in message
news:10106C74-7F03-4C49-AC9F-EC5604DBB3A2@xxxxxxxxxxxxxxxx
> Hi,
> I need help. Currently I am using Windows XP Pro (SP2) and my server are
> Windows 2003 Server (SP1) and I am connect to the Domain. I always get
> this
> error message when I turn on my computer:
>
> "Windows cannot connect to the domain, either because the domain
> controller
> is down or otherwise unaviailable, or because your computer account was
> not
> found. Please try again later. If this message continues to appear,
> contact
> your system administrator for assistance."
>
> Anyone could help me on this. Many Thanks.
>
> Regards,
> Low.


.

Relevant Pages

  • Re: Cannot logo to Win 2003 Enterprise 32-bit
    ... maybe it is misconfigured or it can not find the domain controller. ... domain computer must point to a domain controller running dns with the ... Active Directory domain in it's tcp/ip properties as preferred dns server ... you should be able to logon to the local computer [computer's name ...
    (microsoft.public.windows.server.networking)
  • Re: Can not access web directory in Win2k3 with anonymous access d
    ... I can NOW get to the protected web site from a ... domain computer when I am signed into the domain BUT when IE accesses the web ... I have a domain controller and a member server. ... I can open this file from the domain controller running IE. ...
    (microsoft.public.inetserver.iis)
  • Re: Local Console Password & Network Passwords Different
    ... > From any domain controller you can run the support tool dcdiag to find out ... From any domain computer you can run ... Anyhow you do not need to logon to the PDC fsmo to change any ... >> In addition a blank domain Admin password is ridiculously insecure. ...
    (microsoft.public.security)
  • Re: GPO not applied to clients
    ... I would also run dcdiag and gpotool on the domain controller and netdiag on ... a domain computer that is having the problem receiving the Group Policy. ... their preferred dns server in tcp/ip properties and as shown with ipconfig ...
    (microsoft.public.windows.group_policy)
  • Re: scheduled jobs not logging on
    ... If this is a domain computer using domain credentials to run these tasks ... make sure that the computer has good connectivity to the domain controller ...
    (microsoft.public.win2000.security)
Loading