Netdiag throwing up odd errors

Hi there,

I have a curious set of netdiag errors on each DC.
Basically, I am working with 6DCs in 3 different offices, in the same domain.
Everything is working well, but I just wanted to check the DNS records for
my DCs (all Windows Server 2003 x64.)
Each DC, in its NIC, has each DNS server configured in the domain, starting
with the geographically closest ones.
DCdiag for each DC is clean, and on the surface all DNS records are present
in the domain zone on each DNS server.

However, upon running netdiag on a DC, it generally shows errors like this:
[WARNING] The DNS entries for this DC are not registered correctly on
DNS se
rver ‘0.0.0.0’. Please wait for 30 minutes for DNS server replication.

and:
[WARNING] Cannot find a primary authoritative DNS server for the name
'servername.my.domain.name.x.'.
Obviously I have replaced my server and domain name there, but the FQDN is
in 5 sections, as the FQDN of the domain is in 4 parts.

Running netdiag /fix I get:

[FATAL] Fix Failed: netdiag failed to re-register missing DNS entries for
this DC on DNS server '0.0.0.0'.

and in some cases:
[FATAL] No DNS servers have the DNS records for this DC registered.

It is worth mentioning that these DCs also have the IPv6 protocol bound, and
all other NICs on the servers are disabled.

Thanks!

"johnny_mango" <> wrote in message news:B209C18D-3016-4B77-9D9E-...
> Hi there,
>
> I have a curious set of netdiag errors on each DC.
> Basically, I am working with 6DCs in 3 different offices, in the same domain.
> Everything is working well, but I just wanted to check the DNS records for
> my DCs (all Windows Server 2003 x64.)
> Each DC, in its NIC, has each DNS server configured in the domain, starting
> with the geographically closest ones.
> DCdiag for each DC is clean, and on the surface all DNS records are present
> in the domain zone on each DNS server.
>
> However, upon running netdiag on a DC, it generally shows errors like this:
> [WARNING] The DNS entries for this DC are not registered correctly on
> DNS se
> rver ‘0.0.0.0’. Please wait for 30 minutes for DNS server replication.
>
> and:
> [WARNING] Cannot find a primary authoritative DNS server for the name
> 'servername.my.domain.name.x.'.
> Obviously I have replaced my server and domain name there, but the FQDN is
> in 5 sections, as the FQDN of the domain is in 4 parts.
>
> Running netdiag /fix I get:
>
> [FATAL] Fix Failed: netdiag failed to re-register missing DNS entries for
> this DC on DNS server '0.0.0.0'.
>
> and in some cases:
> [FATAL] No DNS servers have the DNS records for this DC registered.
>
> It is worth mentioning that these DCs also have the IPv6 protocol bound, and
> all other NICs on the servers are disabled.
>
> Thanks!



Hello Johnny,

Curious, are you using IPv6 for any reason? I've seen that to be a cause with network communications and other things.

Or it could be something simple as using an older version of netdiag.

Download and install the Windows Server 2003 Service Pack 2 32-bit Support Tools
http://www.microsoft.com/downloads/d...ng=en#filelist

Re-run it with the downloaded version, and see if that changes things.


--
Ace

This posting is provided "AS-IS" with no warranties or guarantees and
confers no rights.

Ace Fekay, MCSE 2003 & 2000, MCSA 2003 & 2000, MCSA Messaging, MCT
Microsoft Certified Trainer


For urgent issues, you may want to contact Microsoft PSS directly. Please
check http://support.microsoft.com for regional support phone numbers.

"Efficiency is doing things right; effectiveness is doing the right things." - Peter F. Drucker
http://twitter.com/acefekay

Hi Ace, thanks for the reply.

We are using IPv6 in some of the DCs, as this is how the client has been
working. I tried unbinding the protocol in the properties of the NIC, but it
made no difference - is it possible to uninstall it and reinstall it if
necessary?

We did previosuly have even more errors when using netdiag x32 edition, the
errors shown previously were produced in the x64 edition.

Thanks

"Ace Fekay [Microsoft Certified Trainer]" wrote:

> "johnny_mango" <> wrote in message news:B209C18D-3016-4B77-9D9E-...
> > Hi there,
> >
> > I have a curious set of netdiag errors on each DC.
> > Basically, I am working with 6DCs in 3 different offices, in the same domain.
> > Everything is working well, but I just wanted to check the DNS records for
> > my DCs (all Windows Server 2003 x64.)
> > Each DC, in its NIC, has each DNS server configured in the domain, starting
> > with the geographically closest ones.
> > DCdiag for each DC is clean, and on the surface all DNS records are present
> > in the domain zone on each DNS server.
> >
> > However, upon running netdiag on a DC, it generally shows errors like this:
> > [WARNING] The DNS entries for this DC are not registered correctly on
> > DNS se
> > rver ‘0.0.0.0’. Please wait for 30 minutes for DNS server replication.
> >
> > and:
> > [WARNING] Cannot find a primary authoritative DNS server for the name
> > 'servername.my.domain.name.x.'.
> > Obviously I have replaced my server and domain name there, but the FQDN is
> > in 5 sections, as the FQDN of the domain is in 4 parts.
> >
> > Running netdiag /fix I get:
> >
> > [FATAL] Fix Failed: netdiag failed to re-register missing DNS entries for
> > this DC on DNS server '0.0.0.0'.
> >
> > and in some cases:
> > [FATAL] No DNS servers have the DNS records for this DC registered.
> >
> > It is worth mentioning that these DCs also have the IPv6 protocol bound, and
> > all other NICs on the servers are disabled.
> >
> > Thanks!
>
>
>
> Hello Johnny,
>
> Curious, are you using IPv6 for any reason? I've seen that to be a cause with network communications and other things.
>
> Or it could be something simple as using an older version of netdiag.
>
> Download and install the Windows Server 2003 Service Pack 2 32-bit Support Tools
> http://www.microsoft.com/downloads/d...ng=en#filelist
>
> Re-run it with the downloaded version, and see if that changes things.
>
>
> --
> Ace
>
> This posting is provided "AS-IS" with no warranties or guarantees and
> confers no rights.
>
> Ace Fekay, MCSE 2003 & 2000, MCSA 2003 & 2000, MCSA Messaging, MCT
> Microsoft Certified Trainer
>
>
> For urgent issues, you may want to contact Microsoft PSS directly. Please
> check http://support.microsoft.com for regional support phone numbers.
>
> "Efficiency is doing things right; effectiveness is doing the right things." - Peter F. Drucker
> http://twitter.com/acefekay
>
>
>

"johnny_mango" <> wrote in message news:F391ED8A-52F1-4CD2-B2C1-...
> Hi Ace, thanks for the reply.
>
> We are using IPv6 in some of the DCs, as this is how the client has been
> working. I tried unbinding the protocol in the properties of the NIC, but it
> made no difference - is it possible to uninstall it and reinstall it if
> necessary?
>
> We did previosuly have even more errors when using netdiag x32 edition, the
> errors shown previously were produced in the x64 edition.
>
> Thanks

With 2003, you would need to uninstall IPv6 and restart the machine. I don;t think unbinding it will do the trick. If not all DCs are using IPv6, then it would revert to IPv4 when communicating among each other, so if they do not all have IPv6, and the routers don't support it, and not all of the clients have it, then I don't see any advantage.

As for netdiag, I don't believe there is an x64 version, just the x86 version that works on both. The link I provided is an updated version of the support tools. Download it and compare the file date stamps.

Ace

The client has been using IPv6 as an experiment, and say that have seen much
faster logon times using it.

I never had the opportunity to try what you suggested about uninstalling it
as the project finished yesterday. How would I go about uninstalling it, the
uninstall button is ghosted?

As for netdiag,the 64 bit version comes within the Support Tools in the
Server 2003 x64 media.

"Ace Fekay [Microsoft Certified Trainer]" wrote:

> "johnny_mango" <> wrote in message news:F391ED8A-52F1-4CD2-B2C1-...
> > Hi Ace, thanks for the reply.
> >
> > We are using IPv6 in some of the DCs, as this is how the client has been
> > working. I tried unbinding the protocol in the properties of the NIC, but it
> > made no difference - is it possible to uninstall it and reinstall it if
> > necessary?
> >
> > We did previosuly have even more errors when using netdiag x32 edition, the
> > errors shown previously were produced in the x64 edition.
> >
> > Thanks
>
> With 2003, you would need to uninstall IPv6 and restart the machine. I don;t think unbinding it will do the trick. If not all DCs are using IPv6, then it would revert to IPv4 when communicating among each other, so if they do not all have IPv6, and the routers don't support it, and not all of the clients have it, then I don't see any advantage.
>
> As for netdiag, I don't believe there is an x64 version, just the x86 version that works on both. The link I provided is an updated version of the support tools. Download it and compare the file date stamps.
>
> Ace
>
>

"johnny_mango" <> wrote in message news:732A951B-0788-46D0-B34A-...
> The client has been using IPv6 as an experiment, and say that have seen much
> faster logon times using it.
>
> I never had the opportunity to try what you suggested about uninstalling it
> as the project finished yesterday. How would I go about uninstalling it, the
> uninstall button is ghosted?
>
> As for netdiag,the 64 bit version comes within the Support Tools in the
> Server 2003 x64 media.

You know, I never checked if netdiag is a 64 bit even if it is on the x64 media. At least we'll assume you have the latest.

For IPv6 on 2003 machines, to uninstall, in a cmd prompt:
ipv6 uninstall

Then restart.

Ace

Thanks Ace - I never got the chance to try that, but thanks for the tip!

"Ace Fekay [Microsoft Certified Trainer]" wrote:

> "johnny_mango" <> wrote in message news:732A951B-0788-46D0-B34A-...
> > The client has been using IPv6 as an experiment, and say that have seen much
> > faster logon times using it.
> >
> > I never had the opportunity to try what you suggested about uninstalling it
> > as the project finished yesterday. How would I go about uninstalling it, the
> > uninstall button is ghosted?
> >
> > As for netdiag,the 64 bit version comes within the Support Tools in the
> > Server 2003 x64 media.
>
> You know, I never checked if netdiag is a 64 bit even if it is on the x64 media. At least we'll assume you have the latest.
>
> For IPv6 on 2003 machines, to uninstall, in a cmd prompt:
> ipv6 uninstall
>
> Then restart.
>
> Ace
>
>
>
>
>
>

"johnny_mango" <> wrote in message
news:77867CDD-DF48-423A-A014-...
> Thanks Ace - I never got the chance to try that, but thanks for the tip!

My pleasure.

Cheers!

Ace