Re: DNS/Netbios Name



The name confusion is on the human side, the machines all use numbers
(GUID's and SID's, etc...).

Although ugly it will work. You may want to consider building a new forest
and domain and use Active Directory Migration Toolkit (ADMT). It is a free
tool from Microsoft to move from one domain to another.

--


Paul Bergson MCT, MCSE, MCSA, CNE, CNA, CCA

This posting is provided "AS IS" with no warranties, and confers no rights.


"Fredrik" <internal@xxxxxxxxxxxx> wrote in message
news:uomfhQKAGHA.3864@xxxxxxxxxxxxxxxxxxxxxxx
>I have a customer whos domain is "badly" named.
> Root domain named, ab.local who's netbios name is Root_AB
> Child domain named, corp.ab.local netbios name is Corp_AB
>
> I know that this isn't "best practise" and so do my customer. I need to
> provide him with information about what will not work correctly when
> things are named this way and what possible issues are there with this
> configuration in the future. All I can find is recommendations about
> keeping the netbios name uniform with the first part of the domain name,
> but I can't find any information listing possible issues about this. So is
> this just a recommendation or can (will) there be problems using this
> configuration?
>
> Here is the info:
> "Assigning DNS Names to Create a Domain Hierarchy"
> Computers that are not running Windows 2000 Server and Windows 2000
> software will display and accept NetBIOS names, whereas computers running
> Windows 2000 Server and Windows 2000 software will display and accept DNS
> names. This can lead to confusion on the part of your users and
> administrators. You should only use unmatched NetBIOS and DNS names if:
> . You want to migrate to a new naming convention on your network.
> . You are upgrading a NetBIOS name that contains non-standard characters
> but you want the DNS name to have all standard characters.
>
>


.



Relevant Pages

  • RE: Migration NT4->W23 with same WINS/DNS Namespace
    ... perform an in-place upgrade as you have mentioned.We call this issue as ... "Perioded Windows NT Domain Name" issue. ... NETBIOS domain name for Windows NT, you may encounter the following problem ... Upgrade using a new DNS domain name. ...
    (microsoft.public.windows.server.migration)
  • RE: In place upgrade nt 4.0 to windows 2000 AD. Different name question.
    ... it seems that you just want to use a new DNS ... name and keep the original NETBIOS domain name. ... The Domain Name System is the Active Directory locator in the Windows ... Windows Server 2003 domain does not require WINS if it only uses TCP/IP. ...
    (microsoft.public.windows.server.migration)
  • RE: DNS/Netbios Name
    ... I would suggest that "confusion" is the key word here. ... ab.local who's netbios name is Root_AB ... > will display and accept NetBIOS names, whereas computers running Windows ... > 2000 Server and Windows 2000 software will display and accept DNS names. ...
    (microsoft.public.windows.server.active_directory)
  • Re: unable to join to the domain with netbios name
    ... If I ping the server's netbios name form its console, ... From the server itself, if you ping the server's NetBIOS name, what FQDN does it return? ... domain.com as the DNS suffix for all dhcp clients on the network. ... Windows IP Configuration ...
    (microsoft.public.windows.server.general)
  • Re: unable to join to the domain with netbios name
    ... I still don't understand why Vista can not resolve the netbios name of the domain if Netbios over TCP/IP is enabled. ... Then change the primary DNS suffix in your DHCP scope to addomain.domain.com. ... From the server itself, if you ping the server's NetBIOS name, what ... Windows IP Configuration ...
    (microsoft.public.windows.server.general)