Re: Utility to identify DCs



Hi

Logon problems are usually BAD DNS configuration, or comunication problems:
check:
- Make sure that every domain controller has its DNS properties under NIC
configuration pointing to itself. (If DC IP Address is 10.0.0.1 then Dns
should be 10.0.0.1).



- Make sure that every DNS server can resolve all domains in the forest.
(Use Forwarding, Stub Zones or Secondary Zones).



- Make sure that all clients Only uses the local(s) Dns Server.



How Domain Controllers Are Located in Windows

http://support.microsoft.com/kb/247811/





--
I hope that the information above helps you

Good Luck
Jorge Silva
MCSA
Systems Administrator

"Japhy" <japhyrider2005@xxxxxxxxx> wrote in message
news:1151467601.345475.7530@xxxxxxxxxxxxxxxxxxxxxxxxxxxxxxx
Hello,
I have a problem with new users setup in AD unable to logon to the
domain.
Users accounts setup in the past can logon. I have read some posts and
am speculating that from the workstations where I can't logon, the DC
is
unavailable and I am logging into the domain with cached information.
Does that make sense?
Is there a utility that I can run on the workstation that will show me
that the DC is currently available or not?
thanks in advance!



.



Relevant Pages

  • Re: Domain unavailable for some logons
    ... You probably have a dns problem and the computer that you can not logon to ... with the domain account can not find the domain controller. ... > couple logon accounts for most of the 25 PC's. ...
    (microsoft.public.win2000.security)
  • Re: Domain unavailable for some logons
    ... Logon to that computer with a domain account that you can and run the ... Also run netdiag on the domain controller. ... > My client hosts' preferred DNS server settings already point to my two DNS ... run the support tool netdiag on that domain computer ...
    (microsoft.public.win2000.security)
  • Re: Domain name at logon differs from the name of the domain
    ... In DNS manager right click on the zone, and look at "Allow Dynamic Updates" ... > but attempting to logon to it brings the error "no domain ... >>NetBIOS domain name, as this is part of SAM logon name. ... >>Microsoft MVP Windows Server - Active Directory ...
    (microsoft.public.win2000.active_directory)
  • Re: 2min or more delay longing on to domain with XP Pro SP2
    ... When you say that things changed with the fast logon optimization disabled, ... Certainly not DNS, ... >> As for logging, do you simply mean EVENT Viewer logging or ...
    (microsoft.public.win2000.active_directory)
  • Re: Please wait while the domain list is created
    ... Delayed logons are often a dns issue in that the computer is having a ... that W2K/XP Pro domain computers point ONLY to domain controllers running ... netdiag and dcdiag should be helpful to you. ... policy that can cause very long logon times and/or logon failures. ...
    (microsoft.public.windows.server.networking)

Loading