Wins Event ID 4193

WINS could not create the notification socket. Make sure the TCP/IP driver is  installed and running properly.

This event has suddenly appeared on my windows 2003 server nothings strange on the server everything else looks fine except and NBT error 4321

The name "TEREX-AU       :1d" could not be registered on the Interface with IP address 192.168.5.12. The machine with the IP address 192.168.1.10 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.

stephanjennerAsked:
Who is Participating?
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.

rhandelsCommented:
Do you have multiple machinesnames within the domain?? What kind of a machine is the 192.168.1.10
0
rhandelsCommented:
0
stephanjennerAuthor Commented:
Machine 192.168.1.10 is a domain controller there are 3 dc in the network 192.168.1.12, 192.168.1.10 and 192.168.5.12 the one with the issue. Multiple machine names?? all dc's have only one name
0
Cloud Class® Course: Python 3 Fundamentals

This course will teach participants about installing and configuring Python, syntax, importing, statements, types, strings, booleans, files, lists, tuples, comprehensions, functions, and classes.

stephanjennerAuthor Commented:
thand rhandels tried that the services file is fine and the wins tcp and udp are there
0
rhandelsCommented:
>> Multiple machine names?? all dc's have only one name<<

Maybe some machines within the network have the sme machine names  and you canniot have m,ukltiple machines names within one domain.. Maybe the WINS server allready has this name configured to another machine,..
0
stephanjennerAuthor Commented:
no definitely not all machines have different names and the server is very unique
0
rhandelsCommented:
Do you experience any problem with name resolutions???
0
stephanjennerAuthor Commented:
no dns is handlin g it fine and the secondary wins at 192.168.1.12 is working fine
0
rhandelsCommented:
Hi,

Here's the exact same error your experiencing, it's a Microsoft KB article. Does seem like you have  a multiple NetBios name in your network...

http://support.microsoft.com/default.aspx?scid=kb;en-us;822659
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
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.

Question has a verified solution.

Are you are experiencing a similar issue? Get a personalized answer when you ask a related question.

Have a better answer? Share it in a comment.