Solved

Problem naming FQDN when creating a forest for Active Directory

Posted on 2014-09-05
4
129 Views
Last Modified: 2014-09-16
I have a WIndows machine without a Forest or a Domain, just a name and a Workgroup.

Name:        Field
Workgroup:   abc

Open in new window

                                 
So now I want to add a Forest and a Domain to the machine, such that its FQDN will be field.yyy.xxx.zzz.com

So I start by creating a Forest following these instructions:

http://technet.microsoft.com/en-us/library/cc755059%28v=WS.10%29.aspx

I get as far as task 11 (Put in a FQDN for the Forest), I put in the desired name, as opposed to the name and workgroup:

field.yyy.xxx.zzz.com

Open in new window

                                 

I hit return and the system says the following:

The default NetBIOS Domain name "field0" was selected due to name conflicts on the network
                                 
So apparently Windows AD thinks there is some sort of IP resolution conflict.  After repeated attempts to resolve the issue, I come to a potential solution:  I remove the DNS and the Gateway.

My thinking is that if there is no DNS, it can not find a name conflict.  So I delete the DNS and Default Gateway, and I reboot the machine to hopefully flush any IPTABLES entires

So I try adding a forest again, and give the following FQDN:

field.yyy.xxx.zzz.com

Open in new window

                               

After I I hit return and the system reports:

The default NetBIOS Domain name "field0" was selected due to name conflicts on the network

Same thing as before even though there is no DNS.

Any idea of what I should do from this point ?

Thanks
0
Comment
Question by:Anthony Lucia
  • 2
4 Comments
 
LVL 28

Expert Comment

by:becraig
Comment Utility
Simply create your domain as such
or field1.local
You will have issues later with your testing which I would suggest you avoid at this point.
0
 
LVL 7

Expert Comment

by:Delete
Comment Utility
NetBIOS will also broadcast for responses so simply removing DNS will not allow you to bypass the fact that there already exists a machine with the same NetBIOS name.

So you really have three options:
1. Change the NetBIOS name of the machine you are trying to promote to a Domain Controller
2. Change the NetBIOS name of the conflicting machine
3. Change the subnet of the Domain Controller

Another option I forgot:
4. Disable NetBIOS over TCP/IP on the Domain Controller's NIC
Go to the properties of the NIC -> Select Internet Protocol Version 4 (TCP/IPv4) -> Select Properties -> Advanced -> WINS tab -> Select Disable NetBIOS over TCP/IP
0
 

Author Comment

by:Anthony Lucia
Comment Utility
Previously when I put in a FQDN, the install process would take about 30 seconds, and then produce the following error:

The default NetBIOS Domain name "field0" was selected due to name conflicts on the network 

Open in new window


This time I followed the instructions given, as follows

Disable NetBIOS over TCP/IP on the Domain Controller's NIC
Go to the properties of the NIC -> Select Internet Protocol Version 4 (TCP/IPv4) -> Select Properties -> Advanced -> WINS tab -> Select Disable NetBIOS over TCP/IP 

Open in new window


Then I rebooted the machine

Then I entered the FQDN again, but instead of taking 30 seconds, it took no time at all, and displayed the following warning:

The default NetBIOS Domain name "field0" was selected due to name conflicts on the network 

Open in new window


So the NETBios is not finding a conflict, because it can not broadcast, as evidenced by the fact taht it takes 0 seconds to tell me there is a conflict instead of the usual 30 seconds when the NETBios is enabled for the NIC

I though that IPTABLES would not be an issue since I rebooted

How can I proceed to eliminate this error / warning ?

Thanks
0
 
LVL 28

Accepted Solution

by:
becraig earned 500 total points
Comment Utility
Ok maybe you should give my simple idea a try

1) Ensure the server is configured with it's own primary address as the dns server
2) Ensure the dns server service is running with no issues
3) Simply enter your fqdn for your domain (field.local) or whatever you plan to use.

II would suggest trying something unique that you have not tried to this point (as far as a name) since something else may be happening here that we are not aware of.


you should also be able to verify dns is working by simply running nslookup at a prompt and see what comes back.
0

Featured Post

IT, Stop Being Called Into Every Meeting

Highfive is so simple that setting up every meeting room takes just minutes and every employee will be able to start or join a call from any room with ease. Never be called into a meeting just to get it started again. This is how video conferencing should work!

Join & Write a Comment

This article describes how to set permissions to allow a limited-permissions user to start and stop a particular System Service.   It is always best to give users only the permissions that they need to perform their job, so tweaking particular permi…
The way I use Experts Exchange to assist me in analyzing and diagnosing a problem is I first enter a Verbose Question at Experts Exchange like: Office 2007 will hang when opening and saving files I then launch WordPad (any text editor will do) an…
This video Micro Tutorial explains how to clone a hard drive using a commercial software product for Windows systems called Casper from Future Systems Solutions (FSS). Cloning makes an exact, complete copy of one hard disk drive (HDD) onto another d…
Windows 8 came with a dramatically different user interface known as Metro. Notably missing from that interface was a Start button and Start Menu. Microsoft responded to negative user feedback of the Metro interface, bringing back the Start button a…

772 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

Need Help in Real-Time?

Connect with top rated Experts

15 Experts available now in Live!

Get 1:1 Help Now