Re: New Windows Server 2003 R2 DC problems

Tech-Archive recommends: Fix windows errors by optimizing your registry

Yes, the new server is pointing to itself for DNS. Also verified old server
(since it is still in the environment) is pointing to the new server, and the
DHCP scope has DNS and WINS IP address for new server.

"Danny Sanders" wrote:

Did you set the new Win 2k3 server to point to itself for DNS after you
moved DNS to it?

hth
DDS
"Jason" <Jason@xxxxxxxxxxxxxxxxxxxxxxxxx> wrote in message
news:88705BB4-136C-41A1-8475-51177FAF84E3@xxxxxxxxxxxxxxxx
Hello all,

Accept my apologies for beign so long winded here, but I want to give all
information possible in hopes someone can help me in this situation.

I recently had a Windows 2000 Domain controller (single DC/single site)
running Exchange 5.5. All Service Packs and updates were applied. Many
problems with this server forced me to migrate to a new server. Problems
included hard disk corruption, do not believe it was hardware related, but
rather file system corruption.

Purchased a new server, Windows Server 2003 R2 and joined it to the domain
as a member server. Ran appropriate adpreps for R2 and rebooted both
servers. Ran DCPromo successfully. Allowed new server to replicate, no
errors in any logs at this point.

Next day I decided my promo was successful and so began moving Exchange,
this was the most flawless ADC/5.5-2003 migration I have ever performed.
Still no errors. Installed Blackberry Enterprise Server version 3.6, got
it
working properly and still no errors.

Moved DHCP, DNS, WINS, Print queues, data, etc. to new server, remapped
users, etc. EVERYTHING is working on the new server without issue for 2
days.

I then rebooted the server for giggles (I suppose for no other reason than
because I could) and the server hung on Applying Computer Settings. In
order
to get the server back to a functional state, I had to hard boot, Safe
Mode,
disable DHCP, DNS, WINS, All Exchange Services and reboot. Server comes
up
fine and then I manually start each of these services.

I've now increased logging on Exchange and am receiving no relevant errors
that I can tell in the Application Log. I am however beginning to receive
some other errors. Here are a few to note:

Event 2088 NTDS Replication: Could not use DNS to resolve the IP address
of
the source domain controller (original W2K DC)

Event 1168 NTDS General: An Active Directory error has occurred... Error
value 1053

Event 13508 and 13509 repeated times in the NTFRS log

Other errors include 1010 DHCPServer: An error occurred while accessing
the
DHCP database, events 2087 for NTDS replication.

If anyone could give me a bit of advice on this issue it would be greatly
appreciated. I attempted to make this as informative as possible,
hopefully
it is not too informative. Please advise!!!



.

Relevant Pages

  • Re: DHCP IP lease renewal ok, but a new PC can not obtain an IP ("An e
    ... I guess the problem seen with DHCP from PC's is a symptom of another ... Note that both robert and tina are blade servers within the save blade ... Connection-specific DNS Suffix. ... I.e. DNS servers has their own IP as the first DNS server and another as ...
    (microsoft.public.windows.server.networking)
  • Re: Exchange 2003 installation
    ... Configured on the NIC of the server. ... "Meinolf Weber" wrote: ... Is the ISP's DNS ... Old exchange removed - I don't know the ...
    (microsoft.public.win2000.active_directory)
  • Re: Domain controllers
    ... other DNS was still on the zones transferred to the new domain controller. ... Both DHCP and WINS databases CAN be move -- there are KB ... from one server to another -- search Googgle against Microsoft ...
    (microsoft.public.win2000.active_directory)
  • RE: Exchange Fails to start after a reboot.
    ... this problem appears to be caused by DNS ... please try the steps below on Exchange server. ... Microsoft Online Partner Support ...
    (microsoft.public.exchange.admin)
  • Re: where is the outlook 2003 product key on the SBS2003 R2 DVD
    ... tracking is easier from the server. ... All you need to do is make sure there are no other DHCP servers running on ... The only time I have seen the connectcomputer error you mentioned about DNS ... I couldn't get the client to ...
    (microsoft.public.windows.server.sbs)