Re: Creating and AD domain

"Carl Daniel [VC++ MVP]" <cpdaniel_remove_this_and_nospam@xxxxxxxxxxxxxxx>
wrote in message news:OIR8eNhRFHA.356@xxxxxxxxxxxxxxxxxxxxxxx
> OK, I must be missing something simple - or at least I hope I am.
>
> Here's what I've got: 3 brand new servers with fresh installs of 2K3
> Standard with SP1.
>
> Here's what I want: Those 3 machines in a new domain, one of them acting
> as the domain controller, the others as members.
>
> None of these machines are reachable from the internet, nor will they ever
> be (they're behind a firewall), so I do NOT want the domain to be
> foo.bar.baz.com - I just want plain Foo. All of these machines need to
> access the internet, using existing DHCP and DNS servers.
>
> How should I proceed? Going through the Manage your server wizard gripes
> that a single-named domain cannot be created, and with a dotted name
> insists on wanting to update the zone records on the parent domain
> controller, something that's simply not going to work.
>
> As of now, I've got a domain created, the domain controller is up and has
> access to the internet. Attempting to log in on one of the member
> machines results in the machine being stuck at "Updating your personal
> settings" for a very long time (over 15 minutes now - I have my doubts
> it'll ever move on).
>
> Surely this can't be too hard...
>
> If someone can point me to step by step instructions (that work) for
> creating a simple domain that's not part of any other domain (as was so
> stunningly easy with Windows 2000), I'd appreciate it.
>
> -cd
>

Do not use a single label DNS/AD forest name.
Do not use the .local extension.
The recommendation is to take a sub zone of one of your already registered
DNS names for your company (or a subzone of a new regsitered DNS name that
you own).
It is that simple.

--

Regards,

Mike
--
Mike Brannigan [Microsoft]

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

Please note I cannot respond to e-mailed questions, please use these
newsgroups

"Carl Daniel [VC++ MVP]" <cpdaniel_remove_this_and_nospam@xxxxxxxxxxxxxxx>
wrote in message news:OIR8eNhRFHA.356@xxxxxxxxxxxxxxxxxxxxxxx
> OK, I must be missing something simple - or at least I hope I am.
>
> Here's what I've got: 3 brand new servers with fresh installs of 2K3
> Standard with SP1.
>
> Here's what I want: Those 3 machines in a new domain, one of them acting
> as the domain controller, the others as members.
>
> None of these machines are reachable from the internet, nor will they ever
> be (they're behind a firewall), so I do NOT want the domain to be
> foo.bar.baz.com - I just want plain Foo. All of these machines need to
> access the internet, using existing DHCP and DNS servers.
>
> How should I proceed? Going through the Manage your server wizard gripes
> that a single-named domain cannot be created, and with a dotted name
> insists on wanting to update the zone records on the parent domain
> controller, something that's simply not going to work.
>
> As of now, I've got a domain created, the domain controller is up and has
> access to the internet. Attempting to log in on one of the member
> machines results in the machine being stuck at "Updating your personal
> settings" for a very long time (over 15 minutes now - I have my doubts
> it'll ever move on).
>
> Surely this can't be too hard...
>
> If someone can point me to step by step instructions (that work) for
> creating a simple domain that's not part of any other domain (as was so
> stunningly easy with Windows 2000), I'd appreciate it.
>
> -cd
>
>


.