TABLE OF CONTENTS Your company has been planning a migration from their Windows NT 4.0 domain to a new Windows Server 2003 domain for over a year. You have a corporate office in Charleston, SC and 15 satellite branches spread out over the east coast. In each branch, you are currently running a Windows NT 4.0 domain controller that is also functioning as a DNS, WINS, and DHCP server. In the corporate office you have three domain controllers and two member servers. The member servers in corporate are running WINS, DHCP, and DNS. The WINS servers at each branch are configured in a hub and spoke replication model with corporate. All branch DNS servers pull a secondary zone from a DNS server in corporate. Finally the time has come and you are ready to start your migration. You upgrade your primary DNS server to Windows 2000. You enable dynamic updates. You configure all of the domain controllers in corporate to point to the new Windows Server 2003 DNS server. Next you upgrade your PDC to Windows 2000. Everything seems to be working fine, but in a few hours you start getting calls from some of your branches that the DNS service is giving them Dr. Watson errors. What could be a cause of the problem?
The NT 4.0 servers are running service pack 5.
The NT 4.0 servers should not be running DNS since they are...
