• Status: Solved
  • Priority: Medium
  • Security: Public
  • Views: 5489
  • Last Modified:

NetBT Error 4321

I am receiving the following NetBT error 4321 on all of my computers in one of my domains:

The name"PAG   :0" could not be registered on the interface with IP address . The computer with the IP address did not allow the name to be claimed by this computer. is the statically assigned IP address on a Netgear WNDAP350 Access point with DHCP disabled.  All of my workstations are wired.  If I unplug the access point and reboot several of the systems, the error is gone.  Plug the access point back in, reboot and the error returns.  This is a small domain that I manage and I know without a doubt I don't have any duplicate machine names or IP's on the network. I've found evidence that WINS was configured at one time on a file server but I can't find any evidence of it running now.  If I run nbtstat -n on a random selection of computers they all return similar to below:

U:\>nbtstat -n

Local Area Connection:
Node IpAddress: [] Scope Id: []

                NetBIOS Local Name Table

       Name               Type         Status
    W-PAG-001      <00>  UNIQUE      Registered
    W-PAG-001      <20>  UNIQUE      Registered

Other than the occasional "duplicate name on network" popup, this error doesn't cause any access or performance issues.  My users can access their mapped drives on the domain, they can access email, surf the internet, etc.  However, its driving me crazy because I can't figure out what is causing it.  I don't believe errors are benign and eventually this might come back and cause problems.

My DC, old file ('WINS) server, Terminal Server, and mail server are all Windows 2003 32 bit.  I deployed a new file server in November which is Windows 2008, R2, however I can trace the Net BT 4321 error to the Friday night that I deployed the Netgear device.

Any input to keep me from the rubber room would be appreciated!
  • 2
1 Solution
Matt DaviesCommented:
LadyTech00Author Commented:
Thanks for the input.  I resolved the problem. The IP address of the wireless router was in the pool of leases in the DCHP scope.  To fix the problem, I reconfigured the router with an address outside of the scope.  When I replaced the ancient Linksys routers I kept the same IP's without giving any thought to the fact that I had just recently increased the DCHP scope.  That's what I get for working late on Fridays!
LadyTech00Author Commented:
The problem was due to sloppy administration (my fault).  When I realized what was causing the issue I resolved it.

The problem was caused by assigning a static IP address to a router that was part of the DHCP scope.  Since DHCP was disabled on the router, the server was sending out error messages.

Featured Post

Evaluating UTMs? Here's what you need to know!

Evaluating a UTM appliance and vendor can prove to be an overwhelming exercise.  How can you make sure that you're getting the security that your organization needs without breaking the bank? Check out our UTM Buyer's Guide for more information on what you should be looking for!

  • 2
Tackle projects and never again get stuck behind a technical roadblock.
Join Now