Re: Utility to identify DCs
- From: "Jorge Silva" <jorgesilva_pt@xxxxxxxxxxx>
- Date: Wed, 28 Jun 2006 20:39:08 +0100
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!
.
- Follow-Ups:
- Re: Utility to identify DCs
- From: Japhy
- Re: Utility to identify DCs
- References:
- Utility to identify DCs
- From: Japhy
- Utility to identify DCs
- Prev by Date: Re: Internal & External Networks with Active Directory
- Next by Date: Re: repadmin issues
- Previous by thread: Re: Utility to identify DCs
- Next by thread: Re: Utility to identify DCs
- Index(es):
Relevant Pages
|
Loading