Server 2000 to 2003 strategy / exceution. 2

[notShai]

i inherited a 2000 server which is a DNS/DHCP/AD/file server all in one. 1.the dns is very flaky (randomly cant find PCs/Servers on the network with their machine name, only IP address and vice versa) 2. the domain name is messed up - its called "company-domain" on the net login drop down, but when you ipconfig its called domain.company.com 3.no bdc/ replication of AD 4.other servers dont find the time service 5. its used as a dns for the router we have if it goes down - no http traffic (although MSN messenger does work) 6- example error from a utility server on that domain " The reason the system could not register these RRs was because the DNS server contacted refused the update request. The reasons for this might be (a) you are not allowed to update the specified DNS domain name, or (b) because the DNS server authoritative for this name does not support the DNS dynamic update protocol."

i would like your advice at migrating to 03 server - 1. how do i fix the DNS problem? 2. how do i migrate the AD?. i would like to do away with the old server and just wipe it. i would like to use the new 03 server as the pdc/AD/DNS and rebuild the old (existing) one as an 03 bdc etc.

i can also just change the domain name altogether and not migrate, but then how will i transfer all domain users local OUTLOOK PST files to their new domain name login?


any advice/ links/ name of practical book will be greatly appreciated!
more specific - A. a tutorial/how to of creating a secondary 2000/2003 server to take over the primary function of the dying server
B. creating a new 2003 server domain server and its secondary server

 

[wdoellefeld]

its used as a dns for the router we have if it goes down

That's more than likely the root of most your problems. Don't let your clients use an external DNS server. Point them all to internal DNS and setup forwarding on the server to the external DNS server(s).

more specific - A. a tutorial/how to of creating a secondary 2000/2003 server to take over the primary function of the dying server
B. creating a new 2003 server domain server and its secondary server

Once you get the DNS right and the forwarding setup. Build your new 2003 server and add it to the domain. Then run DCPROMO on the 2003 machine (it should prompt to run adprep and domainprep, run both), then STOP and wait an hour. Run DCPROMO again and make the 2003 machine a domain controller, then STOP and give it plenty of time to replicate (ie overnight). In the morning go into active directory sites and services, expand your site, expand your 2003 server, right click on NTDS settings and look at the properties, click the check box to make it a global catalog server. That's it, in a nutshell.


FRCP

http://www.frcp.net

(my side business)

 

[58sniper]

Answers to your problems:


1. that needs to be resolved. You don't want to upgrade a server (especially a DC) when DNS is problematic.

2. the IPConfig name is likely what's specified in the DNS properties of the IP configuration. A machine can also get this info from the DHCP pool.

3. Upgrading this server won't fix that.

4. configure time sync on this server, and make sure you're not trying to sync via login script.

5. It should be your sole source of DNS. What your router uses really doesn't matter. Make sure you have forwarders configured.

6. That's all in the DNS config, and we would need more info to further troubleshoot.

Upgrade this server before these are resolved and you're going to have far more problems. Resolve them first, and then, if you still have some business reason for it, we can provide more info on how to upgrade or migrate.


Pat Richard, MCSE(2) MCSA:Messaging, CNA(2)

 

[notShai]

FRCP: i wasnt clear. i am using an internal - the 2000 server DNS is pointing to the in house cisco router (ex: 172.16.1.1) and in turn all clients are pointing to the 2000 server for dns (ex:172.16.1.5).
i am not clear about the "forwarding" any links would be appreciated.
is the 2003 / 2000 dns setup / configuration similar?
thank you!

 

[58sniper]

The 2000 DNS is "pointing" to the Cisco box - what do you mean? In the IP configuration of the servers' NICs, you MUST configure the DNS to point to itself. AND ONLY ITSELF.

In the DNS server console, right click on the server, properties, forwarders. Add the IP address of two stable ISP provided DNS servers here.

Pat Richard, MCSE(2) MCSA:Messaging, CNA(2)