A network administrator is setting up an Alternate IP Configuration on a Windows 11 laptop for a field technician who frequently alternates between a DHCP-enabled corporate network and an isolated static-only testing lab. After entering the static parameters for the lab under the Alternate Configuration tab in TCP/IPv4 properties, the laptop is connected to the lab network but receives an APIPA address () instead of applying the alternate static configuration. Which of the following is the root cause of this issue?
- The General tab of the IPv4 properties is manually set to a static IP address rather than configured to obtain an IP address automatically.Cevap
- BThe laptop is running Windows 11 Home edition, which disables the Alternate IP Configuration feature on network adapters.
- CThe technician configured IPv4 properties through the Network Connections control panel applet (ncpa.cpl) rather than Credential Manager.
- DThe technician failed to run the ipconfig /registerdns command to bind the alternate static address to the physical network adapter.
Cevap
The General tab of the IPv4 properties is manually set to a static IP address rather than configured to obtain an IP address automatically.
In Windows client networking, the Alternate IP Configuration tab allows a user to specify static IP settings (such as IP address, subnet mask, default gateway, and DNS servers) that are automatically applied only when a DHCP server fails to respond on the network. For this mechanism to function, the main General tab under TCP/IPv4 properties must be set to 'Obtain an IP address automatically'. If the General tab is configured with static IP properties, Windows will never initiate a DHCP request, and the Alternate Configuration tab is completely ignored.
Adım Adım Çözüm
Anahtar Kavram
Windows TCP/IPv4 Alternate IP Configuration Prerequisites