Windows Server 2003 Event ID: 4321 - NetBT

[itxpert]

Dear All,
I hope to get my Problem resolved let me explain it first....
We have two Domains in our Environment, One is ANS.STUFF.COM having Windows 2000 Advanced Server (Server named ANSPDC acting as PDC).
The Second is ANS.COM.PK having Exchange Server 2003 (Server named EXCHANGE acting as PDC).
All Windows Users gets Authenticated from PDC (ANSPDC) of ANS.STUFF.COM Domain and access Mailboxes through POP3 Account in MS OUTLOOK from PDC (Exchange) of ANS.COM.PK.

We Decided to Migrate the Windows 2000 Advanced Server which was acting as PDC having 5 FSMO Roles of ANS.STUFF.COM to Windows Server 2003.
I made a new Windows Server 2003 extended the Schema of 2000 Server, Made it Additional domain of existing 2000 Server and Tranferred the roles from 2000 to new 2003 server.

Now we have new Windows Server 2003 acting as PDC having 5 FSMO Roles of ANS.STUFF.COM and Windows 2000 advanced server still acting as DC which will be demoted when everything goes fine.

The Problem iam getting is that if PDC (ANSPDC) of ANS.STUFF.COM which is Windows Server 2003 gets restarted then the PDC Exchange of 2nd Domain ANS.COM.PK shows as PDC of ANS.STUFF.COM as well.

I use the command netdom query pdc on ANSPDC which showed me \\EXCHANGE as PDC which is my Exchange Server.

Iam getting the following Errors in System Logs:

Event Source: NetBT

Event ID: 4321

Description: The name "ANSPDC" could not be registered on the Interface with IP address 172.17.1.4. The machine with the IP address 172.17.1.5 did not allow the name to be claimed by this machine.

Where 172.17.1.5 is the IP Address of my Exchange Server.

So far I have a Temporary Solution to encounter this problem.
I Stops Netlogon Service on Exchange
Restarts Netlogon Service on ANSPDC
Then Starts Nerlogon Service on Exchange

This Causes the ANSPDC to get the PDC role of ANS.STUFF.COM Domain.

I need Permanent Solution and for that I need expert advice, Please give your advice so everything gets on track.


Regards,

[Meinolf Weber [MVP-DS]]

ANS.STUFF.Com and ANS.COM.PK are different forests/domains, each with the
5 FSMO roles. So how did you realize the PDC listing? I assume both forests
have a trust so that you can access the mailserver?

Also post an unedited ipconfig /all from all DCs.

[itxpert]

results are posted:

Windows Server 2003 (Exchange) Acting as PDC of ANS.COM.PK having 5 FSMO Roles:

Windows IP Configuration

Host Name . . . . . . . . . . . . : exchange
Primary Dns Suffix . . . . . . . : ans.com.pk
Node Type . . . . . . . . . . . . : Unknown
IP Routing Enabled. . . . . . . . : No
WINS Proxy Enabled. . . . . . . . : No
DNS Suffix Search List. . . . . . : ans.com.pk
com.pk

The command completed successfully

Yes Both Domains use the same Netbios Name... I checked in ADUC and Right Clicked Domain where ANS is shown for both in Domain Name....
Is there any need to enable Netbios? Can i change NEtbios without any issues? Please guide me.....

Well thanks a lot for your time and Help... Is there any other solution than renaming one of the Domain's Netbios? What if i Disable Netbios over TCP/IP for one Domain? Is there any kind of Problem if we disable Netbios? Will it solve my Problem?

[Meinolf Weber [MVP-DS]]

Hello itxpert,

Have both domains the same NetBios name?

Best regards

[Meinolf Weber [MVP-DS]]

That's your problem. The NetBios domain name can be changed with domain rename
tool, when forest/domain functional level is windows server 2003 and exchagne
2003 is installed. Earlier versions doesn't allow domain rename. But you
should built a lab and test before going on the production domain.

See here about:
http://technet.microsoft.com/en-us/w.../bb405948.aspx

http://technet.microsoft.com/en-us/l...08(WS.10).aspx

http://blogs.dirteam.com/blogs/jorge...11/24/154.aspx

http://blogs.dirteam.com/blogs/jorge...5/24/1037.aspx

http://support.microsoft.com/kb/838623

http://www.microsoft.com/downloads/d...displaylang=en

[Meinolf Weber [MVP-DS]]

No other way is available to rename it. AD always requires a good planning
to avoid such kind of configurations.

If you disable NetBios over TCP/IP maybe your clients can not browse any
longer via network neighbourhood. Also i think this will not solve the problem.

[itxpert]

No other way is available to rename it. AD always requires a good planning
to avoid such kind of configurations.

If you disable NetBios over TCP/IP maybe your clients can not browse any
longer via network neighbourhood. Also i think this will not solve the problem.

Yeah this setup was established by the Network Admin before me and he didnt planned these things....
Thank you very much Meinolf :)

[Meinolf Weber [MVP-DS]]

Hello itxpert,

You're welcome.

Best regards

Meinolf Weber
Disclaimer: This posting is provided "AS IS" with no warranties, and confers
no rights.
** Please do NOT email, only reply to Newsgroups
** HELP us help YOU!!! http://www.blakjak.demon.co.uk/mul_crss.htm


> 'Meinolf Weber [MVP-DS Wrote:
>
>> ;4482854']No other way is available to rename it. AD always requires
>> a
>> good planning
>> to avoid such kind of configurations.
>> If you disable NetBios over TCP/IP maybe your clients can not browse
>> any
>> longer via network neighbourhood. Also i think this will not solve
>> the
>> problem.
> Yeah this setup was established by the Network Admin before me and he
> didnt planned these things....
> Thank you very much Meinolf :)
> http://forums.techarena.in
>