HOW TO SETUP DNS PDC DUAL-HOMED - WIN2003

  • Thread starter Thread starter appdevman
  • Start date Start date
A

appdevman

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
(e-mail address removed)
(e-mail address removed)
 
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
 
Back
Top