Problem naming FQDN when creating a forest for Active Directory

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
Anthony LuciaAsked:
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.

becraigCommented:
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
DeleteCommented:
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
Anthony LuciaAuthor Commented:
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
becraigCommented:
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

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
Microsoft Legacy OS

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.