Re: HOW TO SETUP DNS PDC DUAL-HOMED - WIN2003

Tech-Archive recommends: Speed Up your PC by fixing your registry

From: LEW (leweb_at_earthlink.net)
Date: 07/25/04


Date: Sun, 25 Jul 2004 13:04:21 -0500

On the internal NIC tcp/ip properties/advanced/dns, make sure the domain is
listed in the dns suffix for this connection box and that register this
connection and use this connection's suffix in registration are checked.
This tells the Domain controller what zone to register its services in so
other units on the net can find them. Clear these settings on the external
NIC. Verify that the domain controller is pointing to a valid dns server
holding either a primary or Active directory integrated zone for the
internet domain it belongs to. Verify that dynamic dns is enabled. Make
sure units on the network have computer accounts in Active directory.
Delete and recreate the computer accounts in Active directory if they still
do not connect after verifying the configuration. Make sure client units
have correct dns addresses.

Post again and let me know if that solves it.

Lee

"appdevman" <appdevman@hotmail.com> wrote in message
news:u4lAqbhcEHA.2352@TK2MSFTNGP09.phx.gbl...
> I have (2) win svr 2003 Ent. Ed boxes
>
> BOTTOM LINE PROBLEM:
> Can't get computer from "internal" network to see the active directory of
> the PDC box 100%. I get network connectivity; such as sharing files,
> etc....heck, I can ping the crap out of it, nslookup no probs..
> but when it comes time to dealing with active directory,
> I always get errors indicating that it can't contact active directory on
the
> PDC, due to DNS.
>
> so the question is:
> HOW DO YOU SETUP DNS ON THE PDC SO A SERVER ON THE INTERNAL NETWORK CAN
SEE
> THE ACTIVE DIRECTORY ON THE PDC, AND JOIN...AND MAKE THIS COMMUN. SOLID.
>
> -------
> The PDC has:
> (2) NIC's:
> 1 - has static IP to public domain on internet
> 1 - I assigned static non-public IP for internal network
>
> (should they both be on same subnet????
> obviously only the external NIC has a gateway)...
>
>
> for years I have been trying to get DNS set right so this will work.
> It appears to be harder to get to work on Svr2003 than it was on Svr2000.
>
> although it is 'standard', I have yet to find a book that expalins how to
> make the right DNS settings, so I can add active directory-enabled
machines
> to the internal network.
>
> I have tried everything, and have gotten close, but I still can't get an
> internal computer to see the active directory, CONSISTENTLY.
> The DNS settings are always changing on their own, it seems impossible to
do
> this setup that is supposedly so widely used in small to larger sized
> companies.
>
> ANY HELP WOULD BE GREATLY APPRECIATED,
> i can help out, I am a professional application engineer, programmer.
>
> thanks,
> Klaus Heim
> appdevman@hotmail.com
> kheim@hottopic.com
>
>



Relevant Pages

  • Re: Windows Server 2003 DNS & Active Directory Installation?
    ... Sorry I don’t have an experience in DNS & Active Directory configuration ... These features I should be needed for my organization in our server which is ... DNS (I really couldn’t understand why need DNS? ... transfer/share file over the internet through secured way. ...
    (microsoft.public.windows.server.general)
  • Re: Urgent! New router and big disaster
    ... Both NICs should point to his internal IP for DNS. ... forward ports to it reliably in the router. ... I should have been more clear about internet connection.. ...
    (microsoft.public.windows.server.sbs)
  • Re: Urgent! New router and big disaster
    ... Both NICs should point to his internal IP for DNS. ... You should give your SBS a fixed external address so you can forward ports to it reliably in the router. ... I should have been more clear about internet connection.. ...
    (microsoft.public.windows.server.sbs)
  • Re: Active Directory setup
    ... MS recommends that you register your Active Directory domain solely to ... provide dynamic DNS, and it must point to itself for primary DNS. ... The conventional way to provide Internet ... IP address of your ISP's DNS server and click Add. ...
    (microsoft.public.windows.server.setup)
  • Re: How do my server 2003 (DNS) know the Internet?
    ... The Multihomed function is not for Internet access. ... has an ip of 156.40.10.10 for that network. ... It is due to a number of reasons, mainly DNS registration of both NICs, whereas you do not want that. ... It's highly recommended to single home all DCs and use a non-DC for the multihoming purposes. ...
    (microsoft.public.windows.server.dns)