Netdiag error

  • Thread starter Thread starter Brenda
  • Start date Start date
B

Brenda

I am receiving the following error when running
netdiag /test:dns

DNS test . . . . . . . . . . . . . : Failed
[FATAL]: The DNS registration
for 'RUSTON01.ruston.org' is incorrect on all DNS servers.
PASS - All the DNS entries for DC are registered on
DNS server '10.192.73.2' and other DCs also have some of
the names registered.
PASS - All the DNS entries for DC are registered on
DNS server '10.192.73.3' and other DCs also have some of
the names registered.
PASS - All the DNS entries for DC are registered on
DNS server '127.0.0.1' and other DCs also have some of the
names registered.

This is my main 2K DC and Primary DNS server. I have tried
to re-register it. Any thoughts?
 
Look at the configuration of the Nic card on the DNS
server is it set to point to itself for DNS and is it set
to register itself in DNS. Try that first.
 
It is set to point to itself first, then the secondary. It
is also set to register itself.
-----Original Message-----
Look at the configuration of the Nic card on the DNS
server is it set to point to itself for DNS and is it set
to register itself in DNS. Try that first.
-----Original Message-----
I am receiving the following error when running
netdiag /test:dns

DNS test . . . . . . . . . . . . . : Failed
[FATAL]: The DNS registration
for 'RUSTON01.ruston.org' is incorrect on all DNS servers.
PASS - All the DNS entries for DC are registered on
DNS server '10.192.73.2' and other DCs also have some of
the names registered.
PASS - All the DNS entries for DC are registered on
DNS server '10.192.73.3' and other DCs also have some of
the names registered.
PASS - All the DNS entries for DC are registered on
DNS server '127.0.0.1' and other DCs also have some of the
names registered.

This is my main 2K DC and Primary DNS server. I have tried
to re-register it. Any thoughts?
.
Click to expand...
.
Click to expand...
 
In
Brenda said:
It is set to point to itself first, then the secondary. It
is also set to register itself.
Click to expand...

First thing I would do is remove that 127.0.0.1 entry and replace it with
the actual IP of the server. The loopback (127.0.0.1) causes some issues.
Obviously that was placed there by DCPROMO when you promoted this machine.

You have two DNS servers? One of them hosts a secondary zone of the first?

If you only have one DNS server, make sure that it is the only address in
your IP properties. If you have two (both AD Integrated only), point the
first entry to itself, the second to the other one, and vice-versa on the
other one. If the second is a Secondary zone, then on the first server, just
point to itself.

Do not use your ISP DNS (on any internal AD DC or client). That's a cardinal
rule. Recommended to use a forwarder for efficient INternet name resolution.

Once all that is done, you can perform these steps to clean it up and ensure
registration:
Delete the system32\config\netlogon.dns and netlogon.dnb files.
At a CMD prompt:
ipconfig /registerdns
net stop netlogon
net start netlogon

Then you can run:
netdiag /fix
Then rerun your dcdiag.

Hope that helps.

--
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
 
The only place I see 127.0.0.1 is in my RAS setup. I can't
find a way to change anything but the static IP.
 
In
The only place I see 127.0.0.1 is in my RAS setup. I can't
find a way to change anything but the static IP.
Click to expand...

You mean in the RAS console? That's the internal interface, unless you're
saying that it shows up on a RAS client?

In a previous post, you posted the dcdiag, which reported this:
PASS - All the DNS entries for DC are registered on
DNS server '127.0.0.1' and other DCs also have some of the
names registered.
Click to expand...

Which means that one of your interfaces are using the loopback as a DNS
entry.

Tell you what, if you can paste an unedited ipconfig /all from this machine,
that would help a bit.

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
 
In Ace Fekay [MVP] <PleaseSubstituteMyActualFirstName&[email protected]>
posted a question
Then Kevin replied below:
In (e-mail address removed)
Click to expand...

Chances are the RAS interface is the culprit, I've had a couple of poster
with the same problem, according to them all they did was disable and
reconfigured RRAS and it supposedly fixed it.
 
Here it is:

Windows 2000 IP Configuration

Host Name . . . . . . . . . . . . : RUSTON01
Primary DNS Suffix . . . . . . . : ruston.org
Node Type . . . . . . . . . . . . : Hybrid
IP Routing Enabled. . . . . . . . : Yes
WINS Proxy Enabled. . . . . . . . : No
DNS Suffix Search List. . . . . . : ruston.org

Ethernet adapter Local Area Connection 2:

Connection-specific DNS Suffix . : ruston.org
Description . . . . . . . . . . . : Intel 8255x-
based PCI Ethernet Adapter (10/100)
Physical Address. . . . . . . . . : 00-06-5B-1A-4A-
D6
DHCP Enabled. . . . . . . . . . . : No
IP Address. . . . . . . . . . . . : 10.192.73.45
Subnet Mask . . . . . . . . . . . : 255.255.252.0
IP Address. . . . . . . . . . . . : 10.192.73.44
Subnet Mask . . . . . . . . . . . : 255.255.252.0
IP Address. . . . . . . . . . . . : 10.192.73.43
Subnet Mask . . . . . . . . . . . : 255.255.252.0
IP Address. . . . . . . . . . . . : 10.192.73.42
Subnet Mask . . . . . . . . . . . : 255.255.252.0
IP Address. . . . . . . . . . . . : 10.192.73.41
Subnet Mask . . . . . . . . . . . : 255.255.252.0
IP Address. . . . . . . . . . . . : 198.3.92.83
Subnet Mask . . . . . . . . . . . : 255.255.255.240
IP Address. . . . . . . . . . . . : 10.192.73.2
Subnet Mask . . . . . . . . . . . : 255.255.252.0
Default Gateway . . . . . . . . . : 198.3.92.81
DNS Servers . . . . . . . . . . . : 10.192.73.2
10.192.73.3

Ethernet adapter VPN:

Connection-specific DNS Suffix . :
Description . . . . . . . . . . . : SMC EZ Card
10/100 (SMC1211TX)
Physical Address. . . . . . . . . : 00-E0-29-69-9B-
CA
DHCP Enabled. . . . . . . . . . . : No
IP Address. . . . . . . . . . . . : 198.3.92.82
Subnet Mask . . . . . . . . . . . : 255.255.255.240
Default Gateway . . . . . . . . . :
DNS Servers . . . . . . . . . . . : 10.192.73.2
 
In
Brenda said:
Here it is:

Windows 2000 IP Configuration

Host Name . . . . . . . . . . . . : RUSTON01
Primary DNS Suffix . . . . . . . : ruston.org
Node Type . . . . . . . . . . . . : Hybrid
IP Routing Enabled. . . . . . . . : Yes
WINS Proxy Enabled. . . . . . . . : No
DNS Suffix Search List. . . . . . : ruston.org

Ethernet adapter Local Area Connection 2:

Connection-specific DNS Suffix . : ruston.org
Description . . . . . . . . . . . : Intel 8255x-
based PCI Ethernet Adapter (10/100)
Physical Address. . . . . . . . . : 00-06-5B-1A-4A-
D6
DHCP Enabled. . . . . . . . . . . : No
IP Address. . . . . . . . . . . . : 10.192.73.45
Subnet Mask . . . . . . . . . . . : 255.255.252.0
IP Address. . . . . . . . . . . . : 10.192.73.44
Subnet Mask . . . . . . . . . . . : 255.255.252.0
IP Address. . . . . . . . . . . . : 10.192.73.43
Subnet Mask . . . . . . . . . . . : 255.255.252.0
IP Address. . . . . . . . . . . . : 10.192.73.42
Subnet Mask . . . . . . . . . . . : 255.255.252.0
IP Address. . . . . . . . . . . . : 10.192.73.41
Subnet Mask . . . . . . . . . . . : 255.255.252.0
IP Address. . . . . . . . . . . . : 198.3.92.83
Subnet Mask . . . . . . . . . . . : 255.255.255.240
IP Address. . . . . . . . . . . . : 10.192.73.2
Subnet Mask . . . . . . . . . . . : 255.255.252.0
Default Gateway . . . . . . . . . : 198.3.92.81
DNS Servers . . . . . . . . . . . : 10.192.73.2
10.192.73.3

Ethernet adapter VPN:

Connection-specific DNS Suffix . :
Description . . . . . . . . . . . : SMC EZ Card
10/100 (SMC1211TX)
Physical Address. . . . . . . . . : 00-E0-29-69-9B-
CA
DHCP Enabled. . . . . . . . . . . : No
IP Address. . . . . . . . . . . . : 198.3.92.82
Subnet Mask . . . . . . . . . . . : 255.255.255.240
Default Gateway . . . . . . . . . :
DNS Servers . . . . . . . . . . . : 10.192.73.2
Click to expand...

Thanks for posting it. It actually looks ok, unless I missed something. Try
what Kevin suggested and see if that works.
--
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
 
In
Brenda said:
Here it is:

Windows 2000 IP Configuration

Host Name . . . . . . . . . . . . : RUSTON01
Primary DNS Suffix . . . . . . . : ruston.org
Node Type . . . . . . . . . . . . : Hybrid
IP Routing Enabled. . . . . . . . : Yes
WINS Proxy Enabled. . . . . . . . : No
DNS Suffix Search List. . . . . . : ruston.org

Ethernet adapter Local Area Connection 2:

Connection-specific DNS Suffix . : ruston.org
Description . . . . . . . . . . . : Intel 8255x-
based PCI Ethernet Adapter (10/100)
Physical Address. . . . . . . . . : 00-06-5B-1A-4A-
D6
DHCP Enabled. . . . . . . . . . . : No
IP Address. . . . . . . . . . . . : 10.192.73.45
Subnet Mask . . . . . . . . . . . : 255.255.252.0
IP Address. . . . . . . . . . . . : 10.192.73.44
Subnet Mask . . . . . . . . . . . : 255.255.252.0
IP Address. . . . . . . . . . . . : 10.192.73.43
Subnet Mask . . . . . . . . . . . : 255.255.252.0
IP Address. . . . . . . . . . . . : 10.192.73.42
Subnet Mask . . . . . . . . . . . : 255.255.252.0
IP Address. . . . . . . . . . . . : 10.192.73.41
Subnet Mask . . . . . . . . . . . : 255.255.252.0
IP Address. . . . . . . . . . . . : 198.3.92.83
Subnet Mask . . . . . . . . . . . : 255.255.255.240
IP Address. . . . . . . . . . . . : 10.192.73.2
Subnet Mask . . . . . . . . . . . : 255.255.252.0
Default Gateway . . . . . . . . . : 198.3.92.81
DNS Servers . . . . . . . . . . . : 10.192.73.2
10.192.73.3

Ethernet adapter VPN:

Connection-specific DNS Suffix . :
Description . . . . . . . . . . . : SMC EZ Card
10/100 (SMC1211TX)
Physical Address. . . . . . . . . : 00-E0-29-69-9B-
CA
DHCP Enabled. . . . . . . . . . . : No
IP Address. . . . . . . . . . . . : 198.3.92.82
Subnet Mask . . . . . . . . . . . : 255.255.255.240
Default Gateway . . . . . . . . . :
DNS Servers . . . . . . . . . . . : 10.192.73.2
Click to expand...
This is quite an interesting setup, putting this many addresses on a DC can
cause many problems, especially since it is a DNS server.
You have private and public addresses on the same NIC, the default gateway
is a public address. I'm not sure what you are trying to accomplish but you
really need to separate the subnet. Normally you would put the public
address and its gateway on its own NIC if it is not connected to a router.
If it is connected to a router then it should have the router as its
gateway.
A DC should only have one IP per interface, it is hard to make a suggestion
without knowing the network layout.
I would bet that a netdiag /v output will show a lot of problems here.

I really think you should reconsider your network and your goals, sit down
and draw out a plan for your network. I only have a partial picture here but
what I see does not make much sense. Maybe, if I had the whole picture I
could give input, but I don't want to make a suggestion with such a small
piece of the puzzle.
 
In
Kevin D. Goodknecht said:
In
This is quite an interesting setup, putting this many addresses on a
DC can cause many problems, especially since it is a DNS server.
You have private and public addresses on the same NIC, the default
gateway is a public address. I'm not sure what you are trying to
accomplish but you really need to separate the subnet. Normally you
would put the public address and its gateway on its own NIC if it is
not connected to a router. If it is connected to a router then it
should have the router as its gateway.
A DC should only have one IP per interface, it is hard to make a
suggestion without knowing the network layout.
I would bet that a netdiag /v output will show a lot of problems here.

I really think you should reconsider your network and your goals, sit
down and draw out a plan for your network. I only have a partial
picture here but what I see does not make much sense. Maybe, if I had
the whole picture I could give input, but I don't want to make a
suggestion with such a small piece of the puzzle.
Click to expand...


You know, I didn't see the gateway on the wrong interface. That will
definitely cause problems.

Kevin, darn, didn't even think about this with my previous post. Yes, I
completely agree that a DC or for a DNS server for that matter too, should
not have multiple IPs. Matter of fact, if more than 15 IPs, things stop
working, (there's actually an article on that) and I've actually seen it go
south with alot less.

--
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
 
Okay, I've gotten things cleaned up a bit and it has
solved a few issues that I was having, however I am still
getting the same fatal error posted earlier (netdiag DNS
error). Here is my ipconfig now.

Windows 2000 IP Configuration

Host Name . . . . . . . . . . . . : RUSTON01
Primary DNS Suffix . . . . . . . : ruston.org
Node Type . . . . . . . . . . . . : Hybrid
IP Routing Enabled. . . . . . . . : Yes
WINS Proxy Enabled. . . . . . . . : No
DNS Suffix Search List. . . . . . : ruston.org

Ethernet adapter Local Area Connection 2:

Connection-specific DNS Suffix . : ruston.org
Description . . . . . . . . . . . : Intel 8255x-
based PCI Ethernet Adapter (10/100)
Physical Address. . . . . . . . . : 00-06-5B-1A-4A-
D6
DHCP Enabled. . . . . . . . . . . : No
IP Address. . . . . . . . . . . . : 10.192.73.2
Subnet Mask . . . . . . . . . . . : 255.255.252.0
Default Gateway . . . . . . . . . : 10.192.73.1
DNS Servers . . . . . . . . . . . : 10.192.73.2
10.192.73.3
Ethernet adapter VPN:

Connection-specific DNS Suffix . :
Description . . . . . . . . . . . : SMC EZ Card
10/100 (SMC1211TX)
Physical Address. . . . . . . . . : 00-E0-29-69-9B-
CA
DHCP Enabled. . . . . . . . . . . : No
IP Address. . . . . . . . . . . . : 198.3.92.82
Subnet Mask . . . . . . . . . . . : 255.255.255.240
Default Gateway . . . . . . . . . :
DNS Servers . . . . . . . . . . . : 10.192.73.2
10.192.73.3
 
I see you have two NICs in the machine. Which NIC is on the internal network
where AD exists?

Whichever one that is, move that to the top of the BINDING order in Network
& Dialup COnnections/Advanced/Advanced Settings. Then in DNS, tell it to
only listen to the internal NIC.

Usually the gateway would be in the NIC properties of the interface on the
bottom of the binding order, assuming the internal one is set correctly to
show as the top in the binding order. I see your gateway is on the bottom
NIC of the binding order, which seems to be in reverse.

Is this machine offering NAT? Is one of these networks on the Internet or
are they offering access to two segments that both are populated with AD
members?

--
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
 
In
Brenda said:
Okay, I've gotten things cleaned up a bit and it has
solved a few issues that I was having, however I am still
getting the same fatal error posted earlier (netdiag DNS
error). Here is my ipconfig now.

Windows 2000 IP Configuration

Host Name . . . . . . . . . . . . : RUSTON01
Primary DNS Suffix . . . . . . . : ruston.org
Node Type . . . . . . . . . . . . : Hybrid
IP Routing Enabled. . . . . . . . : Yes
WINS Proxy Enabled. . . . . . . . : No
DNS Suffix Search List. . . . . . : ruston.org

Ethernet adapter Local Area Connection 2:

Connection-specific DNS Suffix . : ruston.org
Description . . . . . . . . . . . : Intel 8255x-
based PCI Ethernet Adapter (10/100)
Physical Address. . . . . . . . . : 00-06-5B-1A-4A-
D6
DHCP Enabled. . . . . . . . . . . : No
IP Address. . . . . . . . . . . . : 10.192.73.2
Subnet Mask . . . . . . . . . . . : 255.255.252.0
Default Gateway . . . . . . . . . : 10.192.73.1
DNS Servers . . . . . . . . . . . : 10.192.73.2
10.192.73.3
Ethernet adapter VPN:

Connection-specific DNS Suffix . :
Description . . . . . . . . . . . : SMC EZ Card
10/100 (SMC1211TX)
Physical Address. . . . . . . . . : 00-E0-29-69-9B-
CA
DHCP Enabled. . . . . . . . . . . : No
IP Address. . . . . . . . . . . . : 198.3.92.82
Subnet Mask . . . . . . . . . . . : 255.255.255.240
Default Gateway . . . . . . . . . :
DNS Servers . . . . . . . . . . . : 10.192.73.2
10.192.73.3
Click to expand...

The internal NIC looks a lot better, now you should set the listener IP on
your DNS server on the interfaces tab to listen only on the 10.192.73.2 IP
address.
In the network and dial up connections control panel, Advanced Menu,
Advanced settings make sure that the LAN card is at the top of the
Connections list.

I would like to see the netdiag /v output but it might be too large to post
here since they have enacted a 100 kb limit on posts because of the swen
worm.
 
Back
Top