Solved

The name "DoaminName  :1b" could not be registered on the interface with Ip Address x.x.x.1. The Computer with the IP Address x.x.x.1 did not allow the name to be claimed by this Computer

Posted on 2009-07-09
3
1,496 Views
Last Modified: 2012-05-07
Getting a strange error on a 2k8 Domain Controller. This Domain Controller is host the PDC and RelativeID Roles and is a GC. This Server also hosts WINS and is repolicating to another DC with WINS.

WINS is running as we have a Exchange 2003 Server still

Error seems to have appeared as of Yesterday

Any experience with this

The name "DoaminName  :1b" could not be registered on the interface with Ip Address x.x.x.1. The Computer with the IP Address x.x.x.1 did not allow the name to be claimed by this Computer



NetBT.jpg
0
Comment
Question by:skyjumperdude
[X]
Welcome to Experts Exchange

Add your voice to the tech community where 5M+ people just like you are talking about what matters.

  • Help others & share knowledge
  • Earn cash & points
  • Learn & ask questions
  • 2
3 Comments
 
LVL 10

Expert Comment

by:JaredJ1
ID: 24814343
You might need to clear out the entries for this server from both WINS servers, then restart the DC's.
0
 
LVL 1

Author Comment

by:skyjumperdude
ID: 24814951
Thanks. I did that but it appeared again after reboot. This error should be very concerning?
0
 
LVL 10

Accepted Solution

by:
JaredJ1 earned 500 total points
ID: 24815019
I wouldn't be that concerned. I've seen it lots of places. I bet as of right now you arent experiencing any issues with Exchange right?

You may also want to check your reverse DNS zone. Sometimes that can be incorrect and cause this.
0

Featured Post

NEW Veeam Agent for Microsoft Windows

Backup and recover physical and cloud-based servers and workstations, as well as endpoint devices that belong to remote users. Avoid downtime and data loss quickly and easily for Windows-based physical or public cloud-based workloads!

Question has a verified solution.

If you are experiencing a similar issue, please ask a related question

Always backup Domain, SYSVOL etc.using processes according to Microsoft Best Practices. This is meant as a disaster recovery process for small environments that did not implement backup processes and did not run a secondary domain controller that ne…
Recently, Microsoft released a best-practice guide for securing Active Directory. It's a whopping 300+ pages long. Those of us tasked with securing our company’s databases and systems would, ideally, have time to devote to learning the ins and outs…
This tutorial will walk an individual through locating and launching the BEUtility application to properly change the service account username and\or password in situation where it may be necessary or where the password has been inadvertently change…
Sometimes it takes a new vantage point, apart from our everyday security practices, to truly see our Active Directory (AD) vulnerabilities. We get used to implementing the same techniques and checking the same areas for a breach. This pattern can re…

626 members asked questions and received personalized solutions in the past 7 days.

Join the community of 500,000 technology professionals and ask your questions.

Join & Ask a Question