Examkin

Question

Difficulty: Very hardWindows Client Networking Configuration

A network administrator is performing command-line network configuration on a Windows 11 workstation where the graphical interface is unresponsive. The workstation requires static IPv4 configuration and complete connectivity verification. Place the administrative command-line steps in the correct chronological order required to identify the adapter name, apply IPv4 parameters, configure the primary DNS server, confirm local TCP/IP stack functionality, and test domain name resolution.

  1. 1Execute `netsh interface ipv4 show interfaces` to identify the exact interface name or index.
  2. 2Execute `netsh interface ipv4 set address name="Ethernet" static 192.168.50.25 255.255.255.0 192.168.50.1` to assign the static IPv4 address, subnet mask, and default gateway.
  3. 3Execute `netsh interface ipv4 set dnsservers name="Ethernet" static 10.1.1.10` to configure the primary DNS server.
  4. 4Execute `ping 127.0.0.1` to verify internal loopback functionality and local TCP/IP stack operation.
  5. 5Execute `nslookup server1.domain.local` to test domain name resolution against the static DNS server.

Answer

The correct order of administrative CLI commands is: 1) Execute `netsh interface ipv4 show interfaces` to identify the interface name. 2) Execute `netsh interface ipv4 set address ...` to configure static IP, subnet mask, and default gateway. 3) Execute `netsh interface ipv4 set dnsservers ...` to assign the primary DNS server. 4) Execute `ping 127.0.0.1` to verify local TCP/IP protocol stack initialization. 5) Execute `nslookup server1.domain.local` to validate DNS name resolution.
The correct sequence starts with discovering the exact interface identifier using `netsh interface ipv4 show interfaces`. Next, static IP, subnet mask, and default gateway settings are applied using `netsh interface ipv4 set address`. Once base IP configuration is set, `netsh interface ipv4 set dnsservers` assigns the target DNS server. Testing begins locally with `ping 127.0.0.1` to confirm TCP/IP stack binding, and concludes with `nslookup` to confirm end-to-end host name resolution.

Step-by-Step Solution

1
Identify the target network interface identifier.
Obtained the exact interface string (e.g., "Ethernet").
Netsh context commands require an accurate interface name parameter to modify specific network adapters.
2
Configure static IPv4 parameters on the interface.
Static IP, subnet mask, and default gateway are assigned to the network interface.
Layer 3 addressing must be configured before higher-level services or DNS server settings can be assigned.
3
Assign the primary static DNS server address.
The client network adapter is updated with the static DNS server IP.
DNS server configuration relies on valid local interface IP addressing to send outbound queries.
4
Test local TCP/IP loopback connectivity.
Successful echo requests from 127.0.0.1.
Pinging the loopback address verifies that the Windows TCP/IP protocol stack is active and properly initialized.
5
Verify domain name resolution using nslookup.
Hostname is resolved to an IP address by the configured DNS server.
Validates that DNS resolution works over the newly configured static network parameters.

Key Concept

Command-Line Windows Network Configuration and Troubleshooting Sequence
Rate this question

Topics

Windows Client Networking Configuration

More questions from this topic