Can a guru tell me what this means, and what do i do to get this corrected?
Thanx
Aze
below is the DCDIAG:

Domain Controller Diagnosis

Performing initial setup:
Done gathering initial info.

Doing initial required tests

Testing server: Default-First-Site-Name\BDC
Starting test: Connectivity
BDC's server GUID DNS name could not be resolved to an
IP address. Check the DNS server, DHCP, server name, etc
Although the Guid DNS name

(b2b1a235-a813-4691-b5b1-12d99cd079de._msdcs.CONSARCDG) couldn't be

resolved, the server name (bdc.CONSARCDG) resolved to the IP
address

(192.0.0.6) and was pingable. Check that the IP address is
registered

correctly with the DNS server.
......................... BDC failed test Connectivity

Doing primary tests

Testing server: Default-First-Site-Name\BDC
Skipping all tests, because server BDC is
not responding to directory service requests

Running enterprise tests on : CONSARCDG
Starting test: Intersite
......................... CONSARCDG passed test Intersite
Starting test: FsmoCheck
......................... CONSARCDG passed test FsmoCheck

--

Your DCs will attempt to register various records automatically
in DNS -- including some records based on their "GUID" or
Globably Unique Identifier -- it's a big long number that uniquely
identifies each DC (in this context but GUIDs are used in many
other places too, like COM+)

This may fail if they cannot reach the right DNS server which
is also able to accept DYNAMIC registrations.

Check to make sure the DC is a CLIENT of the correct DNS
(set) and that these DNS servers support and enable dynamic
updates.

If you must change either setting, stop and start the NetLogon
Service:

Net Stop NetLogon
Net Start NetLogon

(Starting the NetLogon server re-registers these records.)

Herb,
Hi I'm afraid this is over my head.

The BDC have this GUID problem, whilst the Server-2 doesn't. The main DNS is
on Server-2 (DC). All other clients points to this server. Both BDC and
server-2 are set to receive dynamic updates.

When you say check the DC is a client, how do you mean ? The DNS is also
running on BDC and has been ever and replicating fine until service pack 4
was installed.

As I said previously Herb, this is going to be panic time, as the main
server is not looking that good, and if there is no replication, ......
should I be worried here ?

--

"Herb Martin" <(E-Mail Removed)> wrote in message
news:%(E-Mail Removed)...
> Your DCs will attempt to register various records automatically
> in DNS -- including some records based on their "GUID" or
> Globably Unique Identifier -- it's a big long number that uniquely
> identifies each DC (in this context but GUIDs are used in many
> other places too, like COM+)
>
> This may fail if they cannot reach the right DNS server which
> is also able to accept DYNAMIC registrations.
>
> Check to make sure the DC is a CLIENT of the correct DNS
> (set) and that these DNS servers support and enable dynamic
> updates.
>
> If you must change either setting, stop and start the NetLogon
> Service:
>
> Net Stop NetLogon
> Net Start NetLogon
>
> (Starting the NetLogon server re-registers these records.)
>
>
>
>

"Azz" <(E-Mail Removed)> wrote in message
news:%(E-Mail Removed)...
> Herb,
> Hi I'm afraid this is over my head.
>
> The BDC have this GUID problem, whilst the Server-2 doesn't. The main DNS
is
> on Server-2 (DC). All other clients points to this server. Both BDC and
> server-2 are set to receive dynamic updates.

There are no Win2000+ BDCs -- only DCs. If you have true BDCs
then they are running NT and don't use the GUIDs in DNS but since
you also say, "set to receive Dynamic updates" this strongly suggests
that they are Win2000 as NT DNS doesn't support dynamic updates.

> When you say check the DC is a client, how do you mean ? The DNS is also
> running on BDC and has been ever and replicating fine until service pack 4
> was installed.

Check the DC's own CLIENT NIC/IP properties to make sure it points
at (one of) those DYNAMIC DNS servers -- if it doesn't register OR they
are not accepting dynamic registrations you will not get these records
automatically. (Also make sure your DHCP client is running -- some people
turn that off on the theory that they aren't using DHCP but this client is
the
one that DOES the client's dynamic registration and you need it even for
static IP address machines IF they need to be registered automatically.)

>
> As I said previously Herb, this is going to be panic time, as the main
> server is not looking that good, and if there is no replication, ......
> should I be worried here ?

Sure -- if you don't have replication then your AD isn't going to work
the way you hope.

The DCs need those records to find and replicate with each other.

ALL DCs must be DNS clients of your dynamic zone (NIC/IP
property setting.)

Hi, thanx,

The BDC is only a name allocated to the second DC. It could have been called
DC2 or anything. So they are not NT machines upgraded.
They were all windows 2000. The BDC (a DC) is SP4, and server-2 is on SP3.

The server-2 has DNS installed and pointing to itself.
The BDC (DC) has DNS installed and pointing to DNS on server-2.
BDC and server-2 have DHCP on them and running. All other clients are
pointing to DNS on server-2 as well.
All addresses are static.

So what's there I have overlooked ?

"Herb Martin" <(E-Mail Removed)> wrote in message
news:%(E-Mail Removed)...
> "Azz" <(E-Mail Removed)> wrote in message
> news:%(E-Mail Removed)...
> > Herb,
> > Hi I'm afraid this is over my head.
> >
> > The BDC have this GUID problem, whilst the Server-2 doesn't. The main
DNS
> is
> > on Server-2 (DC). All other clients points to this server. Both BDC and
> > server-2 are set to receive dynamic updates.
>
> There are no Win2000+ BDCs -- only DCs. If you have true BDCs
> then they are running NT and don't use the GUIDs in DNS but since
> you also say, "set to receive Dynamic updates" this strongly suggests
> that they are Win2000 as NT DNS doesn't support dynamic updates.
>
> > When you say check the DC is a client, how do you mean ? The DNS is also
> > running on BDC and has been ever and replicating fine until service pack
4
> > was installed.
>
> Check the DC's own CLIENT NIC/IP properties to make sure it points
> at (one of) those DYNAMIC DNS servers -- if it doesn't register OR they
> are not accepting dynamic registrations you will not get these records
> automatically. (Also make sure your DHCP client is running -- some people
> turn that off on the theory that they aren't using DHCP but this client is
> the
> one that DOES the client's dynamic registration and you need it even for
> static IP address machines IF they need to be registered automatically.)
>
> >
> > As I said previously Herb, this is going to be panic time, as the main
> > server is not looking that good, and if there is no replication, ......
> > should I be worried here ?
>
> Sure -- if you don't have replication then your AD isn't going to work
> the way you hope.
>
> The DCs need those records to find and replicate with each other.
>
> ALL DCs must be DNS clients of your dynamic zone (NIC/IP
> property setting.)
>
>
>

> The BDC is only a name allocated to the second DC. It could have been
called
> DC2 or anything. So they are not NT machines upgraded.
> They were all windows 2000. The BDC (a DC) is SP4, and server-2 is on SP3.

To avoid confusion, don't call it "THE BDC" (a title) but
rather identify it or call it, the DC "BDC", or just "BDC"
to avoid confusion as much as practical.

> The server-2 has DNS installed and pointing to itself.
> The BDC (DC) has DNS installed and pointing to DNS on server-2.
> BDC and server-2 have DHCP on them and running. All other clients are
> pointing to DNS on server-2 as well.
> All addresses are static.
>
> So what's there I have overlooked ?

You NEED Dynamic updates on the Primary DNS server,
and you need to make sure the DCs can easily reach that
DNS server (probably best to point their client properties
to the DYNAMIC Primary.)

It is not pratical to have DNS which supports a Win2000
Domain use "All static addresses".

Those GUID records are a prime examples of dynamic
records that WILL be registered if you set your DNS
to allow dynamic updates and RESTART the NetLogon
service.

In news:(E-Mail Removed),
Herb Martin <(E-Mail Removed)> posted his concerns then I replied down
below:
>> The BDC is only a name allocated to the second DC. It could have
>> been called DC2 or anything. So they are not NT machines upgraded.
>> They were all windows 2000. The BDC (a DC) is SP4, and server-2 is
>> on SP3.
>
> To avoid confusion, don't call it "THE BDC" (a title) but
> rather identify it or call it, the DC "BDC", or just "BDC"
> to avoid confusion as much as practical.
>
>> The server-2 has DNS installed and pointing to itself.
>> The BDC (DC) has DNS installed and pointing to DNS on server-2.
>> BDC and server-2 have DHCP on them and running. All other clients are
>> pointing to DNS on server-2 as well.
>> All addresses are static.
>>
>> So what's there I have overlooked ?
>
> You NEED Dynamic updates on the Primary DNS server,
> and you need to make sure the DCs can easily reach that
> DNS server (probably best to point their client properties
> to the DYNAMIC Primary.)
>
> It is not pratical to have DNS which supports a Win2000
> Domain use "All static addresses".
>
> Those GUID records are a prime examples of dynamic
> records that WILL be registered if you set your DNS
> to allow dynamic updates and RESTART the NetLogon
> service.

Herb, don;t know if you saw Azz's earlier post, but this stems back to a
single label name domain and is what's causing the problems. Now after
reading this thread, I see he doesn't have an NT4 BDC, but just in "name",
which confused me in the earlier post because I suggested to dump the W2k
box, and go back, promote the NT4 BDC to PDC, and reinstall it as an NT4
BDC, etc. But now I see that this won't work because of his two W2k DCs.

I agree the use of names such as BDC can be confusing since that is a legacy
term from NT4.

If he could export his users with CSVDE, make some modifications for the
domain name and get rid of some of the unnecessary speicif attributes, then
reinstall the W2k box, and re-import the users, Ass will be better off,
otherwise he can bandaid it with that reg entry to force DNS to allow single
label names and possibly keep getting these errors for time to come.


--
Regards,
Ace

Please direct all replies to the newsgroup so all can benefit.

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

In news:(E-Mail Removed),
Herb Martin <(E-Mail Removed)> posted his concerns then I replied down
below:
> I agree --what's in a name? A rose by any other name....
>
> Er, he might object to you renaming HIM as "Ass" though. <grin>

NO rename intended there! BIG Typo. I apologize for that!

>
> [Before anyone takes this serious, I am SURE it was a TYPO -- I
> make those all the time too.]


Yes, I dearly apologize, it was a typo. S and Z are right near each other
and I must have fat fingered the keys or something. But that's no excuse.

Azz, once again, I dearly apologize!

--
Regards,
Ace

Please direct all replies to the newsgroup so all can benefit.

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

I know you well enough to know it was a mistake--
he probably does too.

But I couldn't resist pointing it out -- since it was a
"rename" issue.

In news:(E-Mail Removed),
Herb Martin <(E-Mail Removed)> posted his concerns then I replied down
below:
> I know you well enough to know it was a mistake--
> he probably does too.
>
> But I couldn't resist pointing it out -- since it was a
> "rename" issue.

:-)

--
Regards,
Ace

Please direct all replies to the newsgroup so all can benefit.

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