Event Code 4321 on DMZ

I have two servers on my DMZ (running Windows 2003). One is our web server and the other is our smtp server. Occasionally we are seeing the following message on our smtp server:

LogName=System
SourceName=NetBT
EventCode=4321
EventType=1
Type=Error
ComputerName=MYCOMP
Category=0
CategoryString=none
RecordNumber=54373
Message=The name "WORKGROUP         :1d" could not be registered on the Interface with IP address x.x.x.x.
The machine with the IP address x.x.x.y did not allow the name to be claimed by
this machine.

After researching this message I've looked and the subnet mask on both servers is correct, the netbios names are fine. The only thing that matches is the workgroup name. I've seen where people discuss disabling WINS or even the browser service.

What is this error? How can I get rid of it?

Thanks.
snowmizerAsked:
Who is Participating?

[Product update] Infrastructure Analysis Tool is now available with Business Accounts.Learn More

x
I wear a lot of hats...

"The solutions and answers provided on Experts Exchange have been extremely helpful to me over the last few years. I wear a lot of hats - Developer, Database Administrator, Help Desk, etc., so I know a lot of things but not a lot about one thing. Experts Exchange gives me answers from people who do know a lot about one thing, in a easy to use platform." -Todd S.

Wonko_the_SaneCommented:
In this situation you can safely ignore this since I doubt those machines use NetBIOS for anything. It is related to master browsers etc. Disabling the Browser service should indeed get rid of this, and it may not be a bad idea in a DMZ environment anyways. The less you run the better - unless you rely on the computer browser for anything, but for a web and mail server in a DMZ I strongly doubt it.
0

Experts Exchange Solution brought to you by

Your issues matter to us.

Facing a tech roadblock? Get the help and guidance you need from experienced professionals who care. Ask your question anytime, anywhere, with no hassle.

Start your 7-day free trial
Wonko_the_SaneCommented:
Or if you don't feel comfortable doing it make sure they are not in the same WORKGROUP, that should take care of it also. Disabling the service is better though (following the old rule to only run services you actually need, especially in "unsafe" networks like a DMZ)
0
snowmizerAuthor Commented:
Thanks for the solution options. This helps out to make sure that I wasn't missing something.
0
It's more than this solution.Get answers and train to solve all your tech problems - anytime, anywhere.Try it for free Edge Out The Competitionfor your dream job with proven skills and certifications.Get started today Stand Outas the employee with proven skills.Start learning today for free Move Your Career Forwardwith certification training in the latest technologies.Start your trial today
Windows Server 2003

From novice to tech pro — start learning today.