Re: Clients unable to locate the DC
- From: "Rob Anderson" <jarhead_1899@xxxxxxxxxxx>
- Date: Tue, 16 Aug 2005 19:06:53 -0400
Dave,
I made some fatal DNS flaws.
Once I added at PTR, flushed the root and most of all only placed my DNS
server in the DNS network properties while placing my ISP DNS in the
Forwarders tab all became right with the world.
Thanks
Rob
"Dave Shaw [MVP]" <dhshaw@xxxxxxx> wrote in message
news:e$q8GqSoFHA.1204@xxxxxxxxxxxxxxxxxxxxxxx
> Check to see if there is a Host (A) record in your domain's DNS zone for
> the DC.
>
> -ds
>
> "Jarhead_1899" <Jarhead1899@xxxxxxxxxxxxxxxxxxxxxxxxx> wrote in message
> news:E770BA68-D8A1-4FF6-90AD-5774671ECE30@xxxxxxxxxxxxxxxx
>> Mr. Williams,
>>
>> This is an Active Directory problem that is a direct result of my lack of
>> knowledge of DNS. If I have posted in the wrong news group I apologize.
>>
>> I have built a test network and implemented Win2003svr with 2 clients.
>>
>> The DNS server is running and built as a default (I have not added
>> anything
>> special)
>>
>> When the clients are only pointed to this DNS server I get -
>> The query was for the SRV record for _ldap._tcp.dc._msdcs.domainname
>> can't
>> be found. -
>>
>> When the NSLookup is performed I recieve DNS request timed out ****can't
>> find server name for address 192XXX.
>>
>> I am behind a NAT device. I can only surf from the clients or server when
>> a
>> recursivedns server is used.
>>
>> My domain is registered and when I ping my domain name outside of the NAT
>> device it resolves.
>>
>> I have had to use a host file on clients in order to resolve the names
>> behind the NAT device.
>>
>> All firewalls are turned on the clients and server. Server is not running
>> DCHP only DNS. Wins server is enabled but I don't need it, turned off
>> Wins
>> and Netbios on the clients.
>>
>> Been fighting this for a while and am stymied.
>>
>> Is there something special I need to do to the DNS to get it solve this?
>>
>> Do I need to subscribe to a secondary DNS service (my ISP will not allow
>> forwarding requests from another DNS server)
>>
>> Thanks
>>
>> Rob
>>
>> "Paul Williams [MVP]" wrote:
>>
>>> Sounds like either you are pointing to the wrong DNS server, or the DNS
>>> server you are pointing to (assuming correct) is broken. You're going
>>> to
>>> have to do a little leg work on this one. First thing to do is verify
>>> the
>>> following:
>>>
>>> -- DNS Domain Name is the same as the AD DNS Domain Name (if it isn't
>>> have a
>>> look at the article on dis-joint DNS on my website).
>>> -- DNS zone is configured to accept dynamic updates.
>>> -- DHCP *Client* service is configured to start automatically and is
>>> running
>>> (on the DC)
>>> -- All domain members and DCs point to internal DNS servers (usually the
>>> DCs)
>>> -- The following test, when run from either a client or DC, succeeds and
>>> lists your DCs:
>>>
>>> nslookup -type=srv _ldap._tcp.dc._msdcs.domain-name.com
>>>
>>> Where domain-name.com is the DNS name of your domain.
>>>
>>> --
>>> Paul Williams
>>> Microsoft MVP - Windows Server - Directory Services
>>> http://www.msresource.net | http://forums.msresource.net
>>>
>>>
>>>
>
>
.
- Follow-Ups:
- Re: Clients unable to locate the DC
- From: Paul Williams [MVP]
- Re: Clients unable to locate the DC
- References:
- Re: Clients unable to locate the DC
- From: Jarhead_1899
- Re: Clients unable to locate the DC
- From: Dave Shaw [MVP]
- Re: Clients unable to locate the DC
- Prev by Date: Re: AD User Password Policies
- Next by Date: Re: legacy domains removed with metadata cleanup tool
- Previous by thread: Re: Clients unable to locate the DC
- Next by thread: Re: Clients unable to locate the DC
- Index(es):
Relevant Pages
|