Windows Server

TechMedicNY · Guest

I recently migrated my domain from windows NT4 to windows 2003 Ad. I have
two 2003 DCs. The rest of the servers are 2000 member servers . Server 1 was
a Win NT 4 BDC that was promoted to PDC and then Upgraded as the first DC
in the 2003 AD domain. The second DC is a clean installation of Windows2003 .
DC1 ocassionally has an error message that another ramdom computer(client or
server) claims to be the master browser and holds another election.Hoiw do
I stop this?

DC2 has the same message appear every two minutes or so since it was
deployed:

Event Type: Error
Event Source: NetBT
Event Category: None
Event ID: 4321
Date: 1/31/2005
Time: 11:24:16 AM
User: N/A
Computer: %DC02
Description:
The name "DomainName :1d" could not be registered on the Interface with IP
address %.3(DC2). The machine with the IP address %.199(DC1) did not allow
the name to be claimed by this machine.

For more information, see Help and Support Center at
http://go.microsoft.com/fwlink/events.asp.
Data:
0000: 00 00 00 00 04 00 56 00 ......V.
0008: 00 00 00 00 e1 10 00 c0 ....á..À
0010: 01 01 00 00 01 00 00 c0 .......À
0018: 70 03 00 00 00 00 00 00 p.......
0020: 00 00 00 00 00 00 00 00 ........

What is causing this?How do I fix it? What are possible problems this can
cause on the network ?

TechMedicNY · Guest

one more thign . The two Dcs are in the same site and on the same subnet,
but the Licensing does not replicate between the two .

"Frances [MSFT]" wrote:

TechMedicNY · Guest

There are no Wins Servers on this network nor were there ever any. The DNS
Servers are Active Directory Integrated. There are no other DCs with that
Computer name on the network nor are there any PCs currently using that IP. A
few months ago, I removed a Unix Machine that was on that IP(different name)
but not a member of the old domain. The settings you suggest on the Networ
card were already in place.You said the network may be unstable. What cold
correct this ? .

"Frances [MSFT]" wrote:

Frances [MSFT] · Guest

Hello,

Good to hear from you.

According to your message, I understand that the two DCs both have some
errors. Probably, the master browser issue is related to the Event ID 4321.
I would like to know more information about your domain configuration.

Do you have Wins servers in the domain?

What is the DNS configuration, is it AD-integrated?

Please have a check in DC2.

1. In the TCP/IP properties, click the button "Advanced" in the general tab.

2. Click Wins tab, choose "Default" under NetBIOS setting.

Generally speaking, the problem DC1 has may be caused by an unsteady
network. When a client cannot contact the master browser, it will enforce
an election to select a master browser. So when the network is OK, clients
will find two or more master browsers and thus lead to conflicts.

I suggest that you use the following command to force the master browser
election.

NOTE: It is recommended you run this command on the machine you intend to
be a master browser, like DC1 in your case.

browstat elect Transport Domain [/help]

Parameters:

Transport
==============
Enter a network device name (case-insensitive) for a transport in one of
the following formats:

-\device\Transport_{MAC address} (for example, \device\Nbf_{elnk1601})
-\Transport_{MAC address}
-Transport

Domain:
============
Enter the domain in which the election will be forced.

For example, you can use "browstat elect transport win2k3dom" to force the
win2k3dom domain to re-elect the master browser. More detail can be found
from the article below:

BrowStat Syntax
http://www.microsoft.com/resources/documentation/WindowsServ/2003/all/techre
f/en-us/Default.asp?url=/Resources/Documentation/windowsserv/2003/all/techre
f/en-us/browstat_syntax.asp

As for DC2, the problem may be directly related to DNS. The event id shows
that the netbios name is duplicated. I suggest that you check the domain to
see whether there are other computers using the netbios name of DC2. If
there is a computer using the name, please rename it. The following article
has addressed this issue, it also applies to Windows 2003:

822659 "Duplicate Name Exists" Error Message When You Start a Windows XP
http://support.microsoft.com/?id=822659

More information about the event id 4321 is offered for your reference.

Event ID: 4321
http://www.eventid.net/display.asp?eventid=4321&eventno=1822&source=NetBT&ph
ase=1

This response contains a reference to a third-party World Wide Web site.
Microsoft is providing this information as a convenience to you. Microsoft
does not control these sites and has not tested any software or information
found on these sites; therefore, Microsoft cannot make any representations
regarding the quality, safety, or suitability of any software or
information found there. There are inherent dangers in the use of any
software found on the Internet, and Microsoft cautions you to make sure
that you completely understand the risk before retrieving any software from
the Internet.

Hope this helps. If you have any further questions don't hesitate to get in
touch!

Best regards,

Frances He

Microsoft Online Partner Support
Get Secure! - www.microsoft.com/security

=====================================================

When responding to posts, please "Reply to Group" via your newsreader so
that others may learn and benefit from your issue.

=====================================================
This posting is provided "AS IS" with no warranties, and confers no rights.

Frances [MSFT] · Guest

Hello,

According to your message, both errors persist. Is this correct?

As for DC1, please send the screen shot of the exact error message to
v-franhe@microsoft.com for research. In the meantime, please perform the
following steps.

1. Use "browstat status" command on DC1.

This command is used to display status about a domain. You can also add
"-v", for example, use "browstat status -v domain.com"
Please note: domain.com is your domain name.

You can refer to the article below for reference. Pay attention to the
example 2.

BrowStat Syntax
http://www.microsoft.com/resources/documentation/WindowsServ/2003/all/techre
f/en-us/Default.asp?url=/Resources/Documentation/windowsserv/2003/all/techre
f/en-us/browstat_syntax.asp

Please also send the result of the command to me.

2. Check the result to see if the master browser is DC1.

Since the unstable network may be caused by hardware issues, and it is hard
to troubleshoot, I suggest that we focus on the issue and solve it first.

As for DC2, the 4321 issue may be caused by a NetBIOS name conflict between
the workstation and either another workstation with the same NetBIOS name,
or a workgroup or domain with the same NetBIOS name as the workstation.
Please make sure the domain name should not be the same with DC2.

In Windows domain, computers and domain have their Netbios name, they are
registered to Master domain browser or Wins server. In your scenario,
although you have no Wins server on network, there is netbios name
registered to Master Domain Browser (DC1) by broadcast.

Since you suspect that the IP may result in the issue, I suggest that you
change the IP of DC2. Please use "nbtstat -n" on DC2 to make sure there is
no conflicting in the NetBios name.

Now, I offer you 2 options to resolve the problem.

Option 1:
======
1. Demote DC2 to a member server.

2. Rename DC2.

Refer to the following article for reference. It also applies to win2k3.

How To Use the Netdom.exe Utility to Rename a Computer in Windows XP
http://support.microsoft.com/kb/298593/EN-US/

3. Promote it to be a DC again.

Option 2:
=======
1. Setup Wins Server on DC1.

2. Let all the client computer register their netbios name to DC1.

3. Check if there is a netbios name duplication/conflicting in your network.

If the problems persist, please don't hesitate to get in touch!

Best regards,

Frances He

Microsoft Online Partner Support
Get Secure! - www.microsoft.com/security

=====================================================

When responding to posts, please "Reply to Group" via your newsreader so
that others may learn and benefit from your issue.

=====================================================
This posting is provided "AS IS" with no warranties, and confers no rights.

	Windows Server Forum Index -> Migration	All times are GMT
Page 1 of 1