On IPv4 enterprise networks, which service most effectively minimizes manual TCP/IP configuration errors by automatically leasing addresses and related parameters to clients?

Introduction / Context:
Manual IP configuration leads to duplicate addresses, wrong masks, and incorrect gateway/DNS settings. Automating the assignment of IP parameters reduces help-desk load and speeds up client provisioning. This question examines which common infrastructure service directly addresses those problems.

Given Data / Assumptions:

• Clients use IPv4 and need IP address, subnet mask, default gateway, DNS, and possibly other options.
• We seek a service that dynamically assigns and manages these settings.
• Legacy name-resolution components (for example, WINS) are present as distractors.

Concept / Approach:
Dynamic Host Configuration Protocol (DHCP) servers lease IP addresses and supply options like mask, gateway, DNS, NTP, and more. They prevent conflicts by allocating unique addresses from scopes and reclaiming unused leases. WINS and WINS Proxy relate to NetBIOS name resolution and do not assign IP settings. A PDC (in classic Windows NT domains) provides authentication services, not IP address management.

Step-by-Step Solution:

Verification / Alternative check:
Deploy a DHCP scope and confirm clients obtain correct IP, mask, gateway, and DNS automatically with 'ipconfig /all' or 'nmcli dev show'. Conflicts and typos disappear when leases are centrally managed.

Why Other Options Are Wrong:

• WINS Server: Resolves NetBIOS names; no address leasing.
• WINS Proxy: Forwards NetBIOS name queries across subnets; not IP configuration.
• PDC: Domain authentication; not network-layer addressing.

Common Pitfalls:
Assuming DNS or WINS handle addressing; they map names to addresses, but only DHCP assigns addresses dynamically.

Final Answer:
DHCP Server