The designers of TCP/IP wanted an identification scheme that was independent of any one computer or network equipment design, so they established a scheme of IP addresses.
If you've ever surfed the Web, you have probably seen IP addresses at one time or another (numbers such as 192.168.144.77).
As you administer TCP/IP on a network, a considerable part of your time will be devoted to IP address assignment because IP addresses don't just magically get assigned to network hosts—they have to be provided through manual configuration or some other means.
You just replaced a computer; the old computer is off the network and had held the DHCP IP address of 192.168.0.10.
You bring the new computer online and it obtains a DHCP lease for the same IP address. However, when you try to resolve the name of the new computer, the old computer's name still comes up. Here's how we'll start the troubleshooting process: 1.
There are a few other settings that must be correct on each client as well.
Here's a Power Shell script that lets you easily test for multiple different problem scenarios. Ensure dynamic updates are enabled on the DNS zone This is less likely to be the problem because all clients would not be working is the dynamic updates setting on the DNS zone. If set to Secure, you may begin to see more instances like the ones we'll be talking about in #4 below. Check permissions on the dns Node AD object This problem in particular was extremely hard for us to track down on one occasion.
If it's started, ensure there's no events in the computer's System event log that indicate a problem. Check the advanced DNS client NIC setting The "Register this connection's addresses in DNS" should be on by default, but we've seen instances where it's disabled through some kind of policy.
This must be checked for the DDNS process to proceed.
Fortunately, the people who brought us DNS to replace the file also came up with a solution to this dilemma.
DHCP was the Internet community's answer to dynamically distributing IP addresses.
This does not endear you to road warriors who travel among several offices, especially those who are regional managers.
If you manually manage IP addresses, almost any change to the network will require a visit to one or more computers to update TCP/IP configurations—not a happy prospect.
Objectives Microsoft lists the following objectives for the DHCP portion of the "Implementing, Managing, and Maintaining IP Addressing" section of Exam 70-291, "Implementing, Managing, and Maintaining a Microsoft Windows Server 2003 Network Infrastructure": Manage DHCP.