大网数据广告活动
网络与域名解析

Additional gateways appear in persistent routes

· 52CE 我爱测

Describes an issue in which using LBFO causes additional gateways to appear in persistent routes.

This article provides a solution to an issue where additional default gateways appear in persistent routes when you use Load Balancing and Failover (LBFO).

Original KB number:   2966111

Symptoms

Assume that a network adapter is configured with IP settings that include a default gateway. Later, an LBFO team is created that includes the previously configured network adapter. The newly created teamed network adapter is configured with IP settings. In this situation, you may see the previously configured default gateway route and the newly configured default gateway route in the "Persistent Route" section of the Route Print command output.

For example, if an adapter is configured with a default gateway of 10.0.0.1, and it is then added to an LBFO teamed adapter that is configured with a default gateway of 192.168.0.1, both default routes may appear under the "Persistent Route" section of the Route Print command output as shown here:

===========================================================================
Persistent Routes:
Network Address     Netmask   Gateway Address   Metric
0.0.0.0          0.0.0.0     10.0.0.1      Default
0.0.0.0          0.0.0.0     192.168.0.1   Default
===========================================================================

However, in the "Active Routes" section of the Route Print command output, only the newly configured LBFO teamed adapter default gateway is present.

Cause

This behavior is by design. The legacy route.exe tool does not indicate to which interface the routes in the "Persistent Routes" section are related. The Route Print command shows routes from the active network configuration store in the "Active Routes" section of the command output, and from the persistent network configuration store in the "Persistent Routes" section of the command output. However, the route.exe tool does not indicate to which adapter a persistent route belongs. Because the routes from the previously configured adapter are not in the active route table, there is no functional impact upon the active routing table or the networking behavior.

Resolution

We recommend that you use the Get-NetRoute PowerShell cmdlet when clarity is needed about which routes are in the active store or persistent store, and to which adapters routes apply.

The Get-NetRoute PowerShell cmdlet allows for the administrator to see specifically what is stored in each networking configuration store and to which interface the route belongs.

For the persistent store:

Get-NetRoute -AddressFamily IPv4 -PolicyStore PersistentStore

For the active store:

Get-NetRoute -AddressFamily IPv4 -PolicyStore ActiveStore

Source: Microsoft Learn / IT Pro troubleshooting by Microsoft and contributors. Documentation licensed CC BY 4.0. Code samples are covered by the MIT License. Converted from Markdown, with links normalized and embedded media omitted.

资料来源与适用范围

资料来源
Microsoft Learn / IT Pro troubleshooting
适用范围
- Supported versions of Windows Client · Source date 02/12/2026
内容语言
中文;命令、路径和错误标识保留技术原文
本地收录日期
2026-11-15
授权说明
CC BY 4.0 (documentation), MIT (code samples)

正文与所需资源由本站本地存储。查看来源及更新记录 ↗

请按适用版本和实际日志确认原因;本站没有对每一种系统或设备逐项执行文中的操作。