Go Premium for a chance to win a PS4. Enter to Win

x
  • Status: Solved
  • Priority: Medium
  • Security: Public
  • Views: 210
  • Last Modified:

Problem with FQDN when creating Forest

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



When I perform  a Linux Host command on its IP I get the following address:

# host 10.14.2.5
field.yyy.xxx.zzz.com

Open in new window


So the Linux DNS thinks that is his FQDN, but the Windows machine does not know about that name.  He thinks his name is:

field.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 

Open in new window


So how do I get my desired FQDN on the machine ?  I cant used just the name and the workgroup.

Should I try something like getting the field.yyy.xxx.zzz.com removed from the external DNS or something like that?

Or are there any other ways of handling this

Thanks
0
Anthony Lucia
Asked:
Anthony Lucia
  • 2
1 Solution
 
Miguel Angel Perez MuñozCommented:
You can still using your FQDN, simply any other computer is using field0 as netbios workgroup or domain name. Simply change it during active directory setup and it´s done.
0
 
Anthony LuciaAuthor Commented:
I am confused.  During the Active Directory setup, I did put in the following name (step 11) for the forest.   And I need the following name for the Forest:

field.yyy.xxx.zzz.com

However, that is when it comes back and says it is going to use field0 instead
0
 
Miguel Angel Perez MuñozCommented:
This is because your domain has 2 domain names: one on DNS that is field.yyy.xxx.zzz.com and another on NETBios (old Microsoft network proprietary). Your conflict is based on second, some computer on the net has field0 as netbios name or workgroup and during dcpromo your server discover this and fails. Simply change your domain netbios name during dcpromo and thats enough.
On this tutorial (http://www.ahmedgroup.co.uk/articles/44/1/How-to-install-Active-Directory-on-Windows-2008/Page1.html) you can see as netbios name pilot, when you reach this point, change to another.
0

Featured Post

Independent Software Vendors: We Want Your Opinion

We value your feedback.

Take our survey and automatically be enter to win anyone of the following:
Yeti Cooler, Amazon eGift Card, and Movie eGift Card!

  • 2
Tackle projects and never again get stuck behind a technical roadblock.
Join Now