[x]
Posted via EE Mobile

Search, ask, and monitor your questions on the go with EE Mobile. Visit Experts Exchange from your mobile device and never be out of touch again.

09/30/2008 at 07:25AM PDT, ID: 23774695
[x]
Attachment Details
[x]
The Solution Rating System

With so many solutions, how can you tell which solutions are most likely to help you and which ones are not? To provide you with a tool to use, we rate our solutions based on various elements that most accurately determine if a solution is a quality solution. To explain what factors affect the solution rating, here are the elements we take into consideration when formulating our solution rating.

  • The Grade of the Solution
  • The Zone Rank of the Expert Providing the Solution
  • The Number of Author and Expert Comments
  • The Number of Experts Contributing
  • The Feedback of the Community

Your Input Matters
Because of the way the system is set up, the most important variable in this equation is you. As a member of Experts Exchange, you are able to cast your vote on the quality of the solutions in regard to how complete, accurate, helpful and easy to understand each solution is. When you provide your feedback, each rating is adjusted accordingly. So, if you see a solution that has a poor rating that you think is a good solution, let us know by rating it. As you do, the rating will be adjusted and will become more accurate for other members of our site.

If you have any suggestions that you would like to make for our rating system, please ask a question in the Suggestions Zone of Community Support.

Thank you!

7.3

The name "<DOMAIN>   :1d" could not be registered on the Interface with IP address

Asked by T-cko in WINS, Net BIOS and NetBEUI, TCP/IP

Tags: The name "<DOMAIN> :1d" could not be registered on the Interface with IP address 2.250.7.151. The machine with the IP address 2.250.7.144 did not allow the name to be claimed by this machine.

Hello guys
I have a problem with 4 servers displaying an error message:
The name "<DOMAIN>  :1d" could not be registered on the Interface with IP address x.x.x.151. The machine with the IP address x.x.x.144 did not allow the name to be claimed by this machine.

It is strange situation for me becouse each server's error msg of this type points one to another, still within a range of these 4 servers.

All 4 servers have 3 NICs, each server has one NIC setup with dns, gateway and wins ip settings
This error message appears (in all 4 cases) on NIC that do not have configured wins ip settings.
Servers are 2003 server enterprise, all of them are in domain. Netbios over tcp/ip is alreday enabled.

Can somebody make an overview what is happening behind this error message? I mean exactly what is going on by this error message. Why is interface that do not have wins ip setup trying to register any netbt name? Why is the name of domain registered as netbios name?
How can i resolve this error message if i do not have access to wins server?

Thank you guys
[+][-]10/18/08 02:00 PM, ID: 22749772

At Experts Exchange, members can ask their questions to thousands of technology professionals, also known as Experts. Experts compete and collaborate to answer those questions by leaving comments like this one.

Start your 30-day free trial to view this Expert Comment or ask the Experts your question.

 
[+][-]11/26/08 08:40 PM, ID: 23047702

View this solution now by starting your 30-day free trial. Setting up your free trial is quick, easy, and secure. We will return you to this solution, unlocked, when you're done.

 

About this solution

Zones: WINS, Net BIOS and NetBEUI, TCP/IP
Tags: The name &quot;&lt;DOMAIN&gt; :1d&quot; could not be registered on the Interface with IP address 2.250.7.151. The machine with the IP address 2.250.7.144 did not allow the name to be claimed by this machine.
Sign Up Now!
Solution Provided By: tenaj-207
Participating Experts: 2
Solution Grade: A
 
 
 
Loading Advertisement...
20091111-EE-VQP-91 - Hierarchy / EE_QW_2_20070628