still can't find pdc

  • Thread starter Thread starter Tony
  • Start date Start date
T

Tony

The PDC and the DNS server are on the same machine and
I've configured it to accept Dynamic DNS. I've
configured forward and reverse lookup. How do I check to
see if the machines are pointing to the DNS server as the
primary and to see if it's pointing to itself? If not,
what steps do I need to do this?

Thanks

Most likely a DNS issue. Are ALL the machines on your
network pointing to
the Windows 2000 DNS server as their Primary? Is it
pointing to itself also?
This is how it must be setup and then you use DNS
forwarders to resolve
Internet address from your internal DNS server. Most
issues of network
browsing are caused by DNS in windows2k

--
Scott Harding
MCSE, MCSA, A+, Network+
Microsoft MVP - Windows NT Server

Tony said:
I've upgraded my NT 4.0 PDC to Windows 2000 server and
installed Active Directory, I can only access the active
directory users and computer from Administrative Tools on
the newly upgraded server. When I tried to access it from
a different machine, it displays an error message that it
cannot find the Primary domain controller. This is also
causing other machines to not validate the service
accounts from the PDC which causes other jobs not to run.
Click to expand...


..
 
In
Tony said:
The PDC and the DNS server are on the same machine and
I've configured it to accept Dynamic DNS. I've
configured forward and reverse lookup. How do I check to
see if the machines are pointing to the DNS server as the
primary and to see if it's pointing to itself? If not,
what steps do I need to do this?
Click to expand...

Umm, easily by an ipconfig /all. If you can post that result, we can confirm
it for you and point out any other errors that we can find in your config.
If you are using your ISP's DNS, that can cause major issues.

btw- As far as your terminology, I would just like to point out that there
is no such thing as a "PDC" in W2k, and I'm assuming you're talking about
W2k here. A "PDC" is a legacy term from the NT4 days and is no longer
referenced as such. There's a PDC Emulator FSMO role, which performs
functions to support legacy NT4 BDC and other functions in a W2k/W2k3
domain, but the DC is not called a "PDC" but just rather a "DC". Mutliple
DCs are just replica DCs, but do hold differnet Roles for functionality.

Also, refering back to your original post (whereever it was posted), this
part here raises a question:
When I tried to access it from
a different machine, it displays an error message that it
cannot find the Primary domain controller. This is also
causing other machines to not validate the service
accounts from the PDC which causes other jobs not to run.
Click to expand...

How are you trying to access it? Did you install the adminpak tools on
another machine to try to access it thru ADUC on that machine? If so, then
I'm starting to think that you are using your ISP's DNS in all of your
machines' IP properties, which is a HUGE no-no. Only use your own DNS.
That's it. Otherwise, you will experience sleepless nights, headaches,
stress, etc, all because AD is not functioning correctly....

Let's see an ipconfig /all from your DC and from one of your client machines
please. Try not to edit the names or the IP addresses, it makes it easier
for us that way.

Thanks.


--
Regards,
Ace

Please direct all replies to the newsgroup so all can benefit.
This posting is provided "AS IS" with no warranties.

Ace Fekay, MCSE 2000, MCSE+I, MCSA, MCT, MVP
Microsoft Windows MVP - Active Directory
 
Set up forwarders in your AD-integrated DNS server to point to several
public DNS servers (you may need to remove the * -- root zone -- first).

Then make sure that all servers & workstations specify *only* the internal
DNS server's IP address in their TCP/IP settings - do not specify any
Internet DNS servers there.
 
In
host name: BTS1
primary DNS suffix: beststafftech.com
DNS suffix search list: beststafftech.com

when I ran ipconfig

the machine which is the DNS server ans DC are called BTS1
I typed the ip address of the ISP DNS server in the TCP
properties of the network.

is that correct? It seems like the DNS server is not
resolving itself to the network.
Click to expand...

I was hoping to see the ipconfig, and more information about your
configuration, but to answer your question: NO, that is INCORRECT.

As I previously stated, NEVER EVER use an ISP's DNS server or you'll get a
multitude of errors, such as what you're getting.

Is "beststafftech.com" your AD DNS domain name?
If not, then we have another problem since the Primary DNS Suffix MUST MATCH
your AD DNS Domain name.

Follow Lanwench's suggestions, they are "best practices" in making this work
correctly.

If you need anymore info, or how-to's, please post back.


--
Regards,
Ace

Please direct all replies to the newsgroup so all can benefit.
This posting is provided "AS IS" with no warranties.

Ace Fekay, MCSE 2000, MCSE+I, MCSA, MCT, MVP
Microsoft Windows MVP - Active Directory
 
Back
Top