Re: Clients unable to locate the DC

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
>>
>>
>>


.

Relevant Pages

  • RE: VPN Clients Not Registering in AD DNS
    ... via VPN, the DNS records of the VPN clients are unable to be registered. ... Windows 2003 server? ... please let me know whether the clients get the IP ...
    (microsoft.public.windows.server.sbs)
  • Re: Permissions across 2 Forrest
    ... Primary DNS server on 1.x and the 18.x network along with DHCP and WINS. ... For instance ForrestA DNS is now a secondary for Forrest B and vise versa. ... WINS clients must use the same "WINS Database"* ...
    (microsoft.public.windows.server.active_directory)
  • Re: Still strange not fully working DNS server
    ... On none of the computers (both DC and clients) no firewall software is ... For the rest nothing happens in the DNS forward lookup zone. ... Is the new server Global catalog? ... The config you mentioned was not configured so I have configured ...
    (microsoft.public.windows.server.dns)
  • Re: Client installation frustration.
    ... not, apparently, any DNS lookup issues on my network. ... connection's addresses in DNS" and "Use this connection's DNS suffix in DNS ... is a file and print server that we have at one of our secondary sites. ... Is there any way to cancel all current requests to install clients? ...
    (microsoft.public.sms.admin)
  • Re: problem with xp clients and windows 2003
    ... We now have the cross cable running from the room's switch ... >> policy but logs into the server. ... >> aware that this is a DNS issue but I have TRIPLE checked the DNS ... >> If I do NSlookup from the problematic clients, ...
    (microsoft.public.windows.server.networking)
Loading