- Installing, Configuring, Managing, Monitoring, and Troubleshooting DNS in a Windows 2000 Network Infrastructure
- Installing, Configuring, Managing, Monitoring, and Troubleshooting DHCP in a Windows 2000 Network Infrastructure
- Configuring, Managing, Monitoring, and Troubleshooting Remote Access in a Windows 2000 Network Infrastructure
- Installing, Configuring, Managing, Monitoring, and Troubleshooting Network Protocols in a Windows 2000 Network Infrastructure
- Installing, Configuring, Managing, Monitoring, and Troubleshooting WINS in a Windows 2000 Network Infrastructure
- Installing, Configuring, Managing, Monitoring, and Troubleshooting IP Routing in a Windows 2000 Network Infrastructure
- Installing, Configuring, and Troubleshooting Network Address Translation (NAT)
- Installing, Configuring, Managing, Monitoring, and Troubleshooting Certificate Services
- Passing the Exam
- Exam Resources
Installing, Configuring, Managing, Monitoring, and Troubleshooting DHCP in a Windows 2000 Network Infrastructure
DHCP (Dynamic Host Configuration Protocol) is the capability for a client to request and receive an IP address automatically from a server. If you've never created a DHCP scope, you'd better create one before signing up for this exam. DHCP is a cornerstone of network infrastructure.
You'll need to know how to install the service and create scopes; included are superscopes and multicast scopes. Spend a couple of hours tooling around with the creation scope types and you'll have it whipped.
DHCP servers support dynamic updates with DNS. This allows a client's hostname to be registered in the DNS server automatically. You'll need to know the steps necessary to make this magic happen. Pay close attention to what operating systems can, or can't, participate in dynamic updates.
More than once I've consulted in networks in which (for no apparent reason) clients are getting IP addresses that are not in the DHCP scope. The problem? Someone created and activated a practice scope on a test DHCP server. These are called "rogue servers." Not any more. DHCP servers need to be authorized in Active Directory.
NOTE
Study Hint: Create a DHCP server that supports superscopes and dynamic DNS updates.