A network technician needs to manually assign static network settings and verify connectivity on a Windows 11 client workstation using command-line tools after a local DHCP server failure. In what sequence should the technician perform the following steps to assign the static IP address, subnet mask, default gateway, and primary DNS server, and then verify hostname resolution?
- 1Launch an elevated Command Prompt session on the Windows workstation.
- 2Execute 'netsh interface ipv4 set address' specifying the interface name, static IP address, subnet mask, and default gateway.
- 3Execute 'netsh interface ipv4 set dnsservers' specifying the interface name and static primary DNS server address.
- 4Execute 'ipconfig /all' to verify that the static IP address, subnet mask, default gateway, and DNS server entries are correctly bound to the interface.
- 5Execute 'nslookup' against an internal domain name to test name resolution using the newly assigned DNS server.
Cevap
The correct sequence begins with opening an elevated Command Prompt, followed by setting the static IP address, subnet mask, and gateway using netsh, configuring the static DNS server address via netsh, verifying applied settings with ipconfig /all, and finally testing DNS name resolution using nslookup.
The proper sequence requires securing elevated Command Prompt privileges first. Next, the static IP, subnet mask, and default gateway are assigned using 'netsh interface ipv4 set address'. Then, the static DNS server is configured using 'netsh interface ipv4 set dnsservers'. After configuring the adapter, local settings must be verified using 'ipconfig /all'. Finally, end-to-end DNS name resolution is tested using 'nslookup'.
Adım Adım Çözüm
Anahtar Kavram
Windows Client Network Configuration using Netsh and Diagnostic Utilities