Soru

Zorluk: Çok zorWindows Client Networking Configuration

A Windows 11 Pro workstation in an enterprise office is connected to two active networks via separate network adapters. Ethernet 1 connects to the corporate network using a static IP configuration of 10.50.10.45/24 with default gateway 10.50.10.1. Ethernet 2 connects to a high-speed isolated test network via DHCP, receiving an IP address of 192.168.1.100/24 with default gateway 192.168.1.1. Users observe that when both adapters are connected, traffic destined for internal corporate resources on remote subnets (such as 10.200.0.0/16) fails because Windows routes non-local traffic out Ethernet 2 due to its higher link speed. Which of the following configuration changes in the Windows TCP/IP properties will persistently ensure default traffic prioritizes Ethernet 1?

  1. Clear the Automatic Metric checkbox in the Advanced TCP/IP Settings of Ethernet 1 and manually assign a lower numerical interface metric than Ethernet 2.Cevap
  2. B
    Configure the DNS server address on Ethernet 2 to match the primary corporate DNS server at 10.50.10.1.
  3. C
    Execute ipconfig /flushdns followed by netsh interface ipv4 reset from an elevated command prompt.
  4. D
    Change the Network Location Profile of Ethernet 2 from Public to Private in the Control Panel Network and Sharing Center.

Cevap

Clear the Automatic Metric checkbox in the Advanced TCP/IP Settings of Ethernet 1 and manually assign a lower numerical interface metric than Ethernet 2.
In multi-homed Windows environments where multiple network adapters connect to different gateways, Windows uses the interface metric to select the active default route. By default, Automatic Metric assigns lower numerical values (higher priority) to interfaces with higher connection link speeds. Unchecking Automatic Metric in Advanced TCP/IP settings and explicitly configuring a lower numerical metric on Ethernet 1 forces Windows to prefer Ethernet 1 for outbound traffic targeting non-local subnets.

Adım Adım Çözüm

1
Analyze the multi-homed routing issue in Windows.
Identified that two active default gateways exist on separate subnets and Windows Automatic Metric is auto-assigning a lower metric (higher priority) to Ethernet 2 based on adapter link speed.
When multiple default gateways are present, Windows relies on interface metrics to build the IP routing table.
2
Determine how Windows evaluates interface metrics.
Lower metric values indicate higher route preference.
To force traffic through Ethernet 1, Ethernet 1 must have a lower numerical metric value than Ethernet 2.
3
Identify the persistent GUI configuration method in Windows Client Networking.
Open Ethernet 1 IPv4 properties -> Advanced -> uncheck Automatic Metric -> set a low manual Interface Metric (e.g., 10).
This persistently overrides auto-metric calculation across system reboots without requiring startup scripts.

Anahtar Kavram

Windows IPv4 Interface Metric and Multi-Homed Default Gateway Routing Preference
Tahmini Süre:2m 0s
Bu soruyu puanla