Re: W2000Server DNS config wrong, how to fix or replace?

From: dmorgan-with-suffixed-\ (no email)
Date: 03/26/04 

Date: Thu, 25 Mar 2004 21:16:49 -0800

This worked. Thank you. Now I have a side-effect problem.

Demoting then re-promoting the machine as a domain controller
destroyed the old "administrator" account, and created a new one. The
user profile settings of the old one (which I want) is left behind in
the C:\Documents and Settings\Administrator folder.

Is there some way I can create a new account, but have it adopt the
profile in that subfolder instead of creating a new default set of
settings?? And also have it able to log in locally?

On Wed, 24 Mar 2004 22:14:50 -0600, "Herb Martin"
<news@LearnQuick.com> wrote:

><dmorgan-with-suffixed-"1"-ATdslextreme.com> wrote in message
>news:j5j4601sl9tfltb9423dmr4m2e2q15864h@4ax.com...
>> DNS is wrong on a Win2000Server and I want to figure out how to make
>> it right.
>>
>> It's Windows2000 Advanced Server in a small, non-critical test
>> network. For experiment I configured DNS on it one day, using
>> "windows.bogus" for a fictitious DNS domain name. A week later I
>> dcpromo'd so the machine became a domain controller. The
>> domain name is ACME. The server's IP is 192.168.3.3 and hostname is
>> EMACH2.
>
>This domain is unrelated to the windows.bogus Zone. You need a zone
>corresponding to ACME -- and since single tag domain names are a
>very bad idea and this is a test domain, I would suggest you first DCPromo,
>destroy the domain, set the machine name to a full DNS name and the
>re-perform the DCPromo to create a (new) domain.
>
>> I became aware DNS is wrong when a Win2000Pro machine (192.168.3.11)
>> couldn't join the domain. Here's that attempt, in a packet capture
>> taken at the server while the 2000Pro tried to join:
>
>You need a Dynamic DNS zone corresponding to the Windows Domain
>name -- the domain really should be TWO or more tags, e.g., domain.com
>or domain.bogus but not just "domainname".
>
>All clients of the domain -- including DCs -- must configure ONLY the
>internal DNS server (set) in their NIC\IP properties.

Relevant Pages

  • Windows cannot connect to the domain & Event ID 3210 5722 - Lots of Details!
    ... domain controller for domain DOMAIN, ... This inability to authenticate might be caused by ... password for this computer account is not recognized. ... DNS addresses and there is only one network card in the computer. ...
    (microsoft.public.windows.server.active_directory)
  • Re: Windows 2003 Password Expiration
    ... that checks out OK with no failed tests/errors/warnings particularly for dns, dclist, ... and domain membership then run netdiag on a couple of your workstations. ... problems [domain controller must point to itself and workstations to the DC as ... > you have it set to never in the user account properties. ...
    (microsoft.public.win2000.security)
  • Re: server 2003 standard domain user local rights
    ... Your Server Wizard to add the Domain Controller role, ... The following error occurred when DNS was queried for the service location ... server 2003 on the 2nd server, i want to have a domain user account on the ...
    (microsoft.public.windows.server.sbs)
  • What the heck is Account Unknown doing in my DC?
    ... There is "Account Unknown" profile listed on my DC under ... This box has always been a domain controller. ... There is no local account on it. ... First it was a Win NT 4.0 Server PDC with DNS, ...
    (microsoft.public.win2000.security)
  • Remote Branch DC wont Replicate With Corporate DC
    ... Active Directory could not resolve the following DNS host name of the source ... domain controller to an IP address. ... 'Event' is not recognized as an internal or external command, ... operable program or batch file. ...
    (microsoft.public.windows.server.dns)