dnsapi 11183, then netbt 4319 error

[Guest]

I'm in a W2K domain, with 2 DC's each hosting DNS, AD and DHCP. My computer
has lately been receiving first the DNSAI error 11183 "the system failed to
remove and update registration for adapter..." then later a NETBT 4319 error
stating that a "duplicate name has been detected on the TCPIP network".

I'm seeing this as my IP address lease is up, I get a new IP, but the DNS
update fails.

Any ideas on this?

I am also concerned that each of the DNS servers lists itself as the primary
server in the SOA tab for the forward and reverse lookup zones in the domain.
Is this correct?

Thanks for anything!!

 

[Ace Fekay [MVP]]

In

I'm in a W2K domain, with 2 DC's each hosting DNS, AD and DHCP. My
computer has lately been receiving first the DNSAI error 11183 "the
system failed to remove and update registration for adapter..." then
later a NETBT 4319 error stating that a "duplicate name has been
detected on the TCPIP network".

I'm seeing this as my IP address lease is up, I get a new IP, but the
DNS update fails.

Any ideas on this?

I am also concerned that each of the DNS servers lists itself as the
primary server in the SOA tab for the forward and reverse lookup
zones in the domain. Is this correct?

Thanks for anything!!

The 11183 error can be attributed to a possible external DNS address in the
machine's IP properties. Keep in mind with AD, it MUST only use the internal
DNS, nothing else. Pretty much means no ISP's or any other DNS server that
do not have access to the AD zone name. If not sure what I mean, please post
an ipconfig /all, and one of us will point it out.

As for the NetBT error, does this machine have more than one NIC?

As for SOA, with AD INtegrated zones, each DC/DNS server is an SOA for the
zone due to the multimaster feature of AD Integrated zones. It's default.

--
Regards,
Ace

Please direct all replies ONLY to the Microsoft public newsgroups
so all can benefit.

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

Ace Fekay, MCSE 2003 & 2000, MCSA 2003 & 2000, MCSE+I, MCT, MVP
Microsoft Windows MVP - Windows Server - Directory Services
Infinite Diversities in Infinite Combinations.
=================================

 

[Guest]

Ace:
The client has a single NIC.
DNS1 server has 2 NICs, one is disabled.
DNS2 server has a single NIC.
The 11183 error reported " DNS server list : 192.168.1.50, 192.168.1.58 Sent
update to server : 192.168.1.50" where .50 is DNS2 server.

This first started a week ago. I read various KB articles, some pointing to
the problem with dual NICs and to Routing and Remote Access service. I
thought I solved the problem by disabling Routing and Remote Access on DNS1
(w/2 NICs) which we no longer needed. The problem went away for a few days
and then came back two days ago.

At the moment, I have not had the NetBT error since yesterday, but I have a
different DNSAPI error 11151 which seems related in that it "failed to
register the network adapter..."

Here is my IP config:
Windows 2000 IP Configuration

Host Name . . . . . . . . . . . . : bluebird
Primary DNS Suffix . . . . . . . : GZ.com
Node Type . . . . . . . . . . . . : Hybrid
IP Routing Enabled. . . . . . . . : Yes
WINS Proxy Enabled. . . . . . . . : No
DNS Suffix Search List. . . . . . : GZ.com
GZLab

Ethernet adapter Local Area Connection:

Connection-specific DNS Suffix . : GZ.com
Description . . . . . . . . . . . : 3Com 3C918 Integrated Fast
Ethernet
Controller (3C905B-TX Compatible)
Physical Address. . . . . . . . . : 00-C0-4F-1D-0C-1A
DHCP Enabled. . . . . . . . . . . : Yes
Autoconfiguration Enabled . . . . : Yes
IP Address. . . . . . . . . . . . : 192.168.1.105
Subnet Mask . . . . . . . . . . . : 255.255.255.0
Default Gateway . . . . . . . . . : 192.168.1.254
DHCP Server . . . . . . . . . . . : 192.168.1.53
DNS Servers . . . . . . . . . . . : 192.168.1.58
192.168.1.50
Lease Obtained. . . . . . . . . . : Tuesday, August 23, 2005
10:28:25 AM

Lease Expires . . . . . . . . . . : Wednesday, August 31, 2005
10:28:25 AM

Thank you for your help.
Gina

 

[Kevin D. Goodknecht Sr. [MVP]]

Ace:
The client has a single NIC.
DNS1 server has 2 NICs, one is disabled.
DNS2 server has a single NIC.
The 11183 error reported " DNS server list : 192.168.1.50,
192.168.1.58 Sent update to server : 192.168.1.50" where .50 is DNS2
server.

It appears you are using Standard Primary on 192.168.1.50 and Secondary zone
on 192.1698.1.58 . the reason you get this 11183 message is the secondary
server sends the updates to the master name server (MName record) on the SOA
tab.
This is why AD integrated zones list themselves as masters, so they can
accept dynamic updates.

Delete the secondary zone and change the primary back to AD integrated so
both servers will accept updates to the zone.

 

[Guest]

Kevin, I am sorry but I am not exactly sure what you are asking me to do.
If you would not mind explaning how to "delete the secondary zone" and what
that zone is that would be helpful. Also, let me note that both servers, as
I said, are listed as primary for the forward/reverse zones, and they both
are set to be AD integrated.

I confess I do not know enough about DNS to understand your instructions, I
hope you can be more explicit. Thanks --Gina

 

[Kevin D. Goodknecht Sr. [MVP]]

Kevin, I am sorry but I am not exactly sure what you are asking me
to do. If you would not mind explaining how to "delete the secondary
zone" and what that zone is that would be helpful. Also, let me note
that both servers, as I said, are listed as primary for the
forward/reverse zones, and they both are set to be AD integrated.

I confess I do not know enough about DNS to understand your
instructions, I hope you can be more explicit. Thanks --Gina

According to this:
192.168.1.58 Sent update to server : 192.168.1.50" where .50 is DNS2

192.168.1.58 is showing 192.168.1.50 in the SOA primary master, this means
the 1.158 would have to have a secondary zone if it shows the 1.50 as its
master.

AD integrated zones are all masters and do not send updates to other
servers. That is why they always show them selves on the SOA record as the
primary master (MName record)

If the 192.168.1.50 is AD integrated you should only need to delete the
secondary zone, if it is a secondary.
If you have AD integrated zones on one DC, you cannot have a secondary for
the same domain on the other DC. The AD integrated will replicate to all DCs
in the domain.

The reason I assume this is your concern here: