Urgent : twin server problems

[Leozack]

Hi all - I spent 9-6 on this yesterday and I have to finish it by lunch. Any ideas welcome.

Got an old 2000 server servicing logons and files and such for a bunch of XP PCs using it for DHCP/DNS.

Got a newer 2003 server servicing logons and files for a couple of XP PCs using it for DNS not DHCP (static IPs that aren't in the other DHCP range).

Both servers have a different forest, one is domain. the other is newdomain.local.

How should the DNS/DHCP be setup so that PCs looking for the older server get given the right server name/ip to function whilst the ones looking for the newer server do likewise considering only 1 of them can run DHCP and DHCP gives out the DNS server (so currently the new PCs are going to the old server for DNS)

The problem currently is long logon times "applying user settings" and problems getting any of the GPOs to work on the new PCs. I'm sure I've had this setup working before. It's only until I have time to rebuild the older PCs and take down the old server!

Just the thought of some of the comlpications of DNS like who gets what as a NS record and such makes my eyes redder than they already area.

I've tried adding a DNS zone on each server for the other server's domain with the other server as the SOA and NS. I've made sure both servers are time sync'd and PC's logging on are set to sync with them.

_________________________________
Leozack

MakeUniverse($infinity,1,42);

 

[Leozack]

Ok - I think I've fixed it!

If so then it was as I thought, a DNS issue alone bringing the world down. I found some mistakes in my late night additions of DNS entries on the servers and corrected them.

The result was I now have a forward lookup zone on each server for the other server's domain. In each of those is a SOA & NS & A record for the other server. Also I added a reverse lookup PTR for each server on the other server.

Possibly another problem was I found both servers only had DNS records for themself, no clients at all! Not sure why but I've made sure DHCP is set to always update DNS now. But I added the new PC I'm testing on to the new server as an A record manually too, so maybe that helped.

Phew. Now an hour ro ghost it in and out to 14 PCs and set them up. Then I just need to make a generic user who's folders point to the old server so they can still get their work off the old server for now etc etc *sweat*

_________________________________
Leozack

MakeUniverse($infinity,1,42);