Re: Troubleshoot or reinstall Server 2000?

Hi

I have a domain at Windows 2000 native funtional level. For the sake
of this discussion there are two DCs, 2000 and 2003. I transfered most
functionality to the newer 2003 DC including FSMO roles, global
catalog, important apps and services.

Although you have only 1 Domain, and according with your description you
shouldn't have the IM on GC, unless all DCs on your site are also GCs. If
you want to have only one GC per site then you should place the IM on a DC
tha isn't a GC.

FSMO placement and optimization on Active Directory domain controllers
http://support.microsoft.com/default.aspx?scid=kb;en-us;223346



I left the old server running with only two jobs, replicate the active
directory and provide DNS if needed. Things ran fine for several
months.

Are both DCs DNS server?

I'm not sure why, but now the 2003 DC can't replicate with the 2000 DC.
Also, the DNS console in 2003 fails to connect to the 2000 DNS. It's
not a basic TCP/IP connectivity issue. It seems to be something more.


Are the servers resolving eachother by fqdn?
Did you run Dcdiag - <Dcdiag /c /v /d> ?
Did you run Netdiag /debug?
Can you place here the results for ipconfig /all
Did you checked the Sysvol folder?
Troubleshooting missing SYSVOL and NETLOGON shares on Windows 2000 domain
controllers
http://support.microsoft.com/?kbid=257338
Do you have any Fw preventing replication between the servers?
Service overview and network port requirements for the Windows Server system

http://support.microsoft.com/default.aspx?scid=kb;en-us;832017


--
I hope that the information above helps you

Good Luck
Jorge Silva
MCSA
Systems Administrator

"Tom Penharston" <thinkpersuasion@xxxxxxxxxxxx> wrote in message
news:1149717805.475458.321740@xxxxxxxxxxxxxxxxxxxxxxxxxxxxxxx
I have a domain at Windows 2000 native funtional level. For the sake
of this discussion there are two DCs, 2000 and 2003. I transfered most
functionality to the newer 2003 DC including FSMO roles, global
catalog, important apps and services.

I left the old server running with only two jobs, replicate the active
directory and provide DNS if needed. Things ran fine for several
months.

I'm not sure why, but now the 2003 DC can't replicate with the 2000 DC.
Also, the DNS console in 2003 fails to connect to the 2000 DNS. It's
not a basic TCP/IP connectivity issue. It seems to be something more.

Is it important to trace all of the errors and fix the problems, or can
I just remove the bad DC from active directory and reinstall server
2000?

Very thorough administrators might want to know exactly what happened,
but there's another argument that you can't always know what happened,
just make it work and don't worry about it.



.

Relevant Pages

  • Re: AD and DNS moving
    ... Let me start by saying that the PDC and BDC concept doesn't exist on Active Directory, in AD all DCs are peers and all DCs have a REad/Writable AD Database. ... Not knowing everything about your environment and assuming that you only have 1 Domain/Forest and All DCs are in same physical LAN, and that you've DNS Active Directory Integrated (Careful if you have more than one Domain, you should pay attention about how you place the FSMO roles, especially the Infrastructure Master), you can install the DNS service (note: initially you should point the primary DNS server in the new server to an existing DNS server, this will allow you to replicate DNS, AD, etc... ...
    (microsoft.public.windows.server.active_directory)
  • Re: DNS not syncing between PDC and BDC
    ... all DCs should be of the same SP level due to variances. ... But first, just an FYI, there is no such thing as a PDC or BDC in Active ... The FSMO roles can be transferred dynamically between DCs. ... you may have a possible DNS misconfiguration. ...
    (microsoft.public.win2000.dns)
  • Re: Migrate to new server
    ... You have 5 FSMO roles, so you can see that 002 is schema owner and Domain owner and the other roles are at 001. ... I will be migrating the server tomorrow, ... For this tools you have to install the support\tools\suptools.msi ... For DNS make your live easy and use AD integrated zones on the ...
    (microsoft.public.windows.server.dns)
  • Re: AD and DNS moving
    ... in AD all DCs are peers and all DCs have a ... you've DNS Active Directory Integrated (Careful if you have more than one ... server to an existing DNS server, this will allow you to replicate DNS, ... FSMO roles to the new server, make all DCs Global Catalogs, make sure ...
    (microsoft.public.windows.server.active_directory)
  • Re: 2003 Domain Controller Question
    ... > forest with two 2003 DCs the first one as the FSMO roles AND the GC right? ... Operations Masters and is a Global Catalog server. ...
    (microsoft.public.win2000.active_directory)
Loading