Link speed [Removed PII]

Brian maritz 20 Reputation points
2026-06-13T04:16:53.48+00:00

Link speed (Receive/Transmit): 100/100 (Mbps) IPv6 address: [Removed PII] fdca:[Removed PII] Link-local IPv6 address: [Removed PII] IPv6 DNS servers: [Removed PII] IPv4 address: [Removed PII] IPv4 DNS servers: [Removed PII] Primary DNS suffix: lan Manufacturer: Intel Description: Intel(R) Ethernet Connection I217-LM Driver version: 12.19.1.37 Physical address (MAC): [Removed PII]

Windows for home | Windows 10 | Internet and connectivity
Answer accepted by question author
franco d'esaro 25,086 Reputation points Volunteer Moderator
2026-06-13T08:02:24.4366667+00:00

Hi.

Ethernet speed stuck at 100 Mbps is usually caused by a hardware problem:

Faulty, loose or poor quality network cable.

Faulty Ethernet cable connector.

Faulty Ethernet LAN wall socket.

Faulty Ethernet LAN socket on PC or router/switch.

The first test to do is to unplug/replug the network cable at both ends or try replacing the cable with a higher quality or different brand.

-Is the PC's network cable connected to the Ethernet socket on the wall or is it connected directly to the router's LAN port?

-Are your PC and router in the same room or in different rooms or on different floors of the house?

If you have another computer with Gigabit Ethernet connectivity, unplug the network cable from your PC and plug it into the other computer and check if the speed is regular.

Was this answer helpful?

10 people found this answer helpful.
0 comments

2 additional answers

Sort by: Most helpful
Most helpful Newest Oldest
  1. nobuko c 125.1K Reputation points Independent Advisor
    2026-06-13T07:25:56.96+00:00

    Hello,

    Could you please clarify what problem you are experiencing and what exactly you would like to know?

    Was this answer helpful?

    3 people found this answer helpful.
    0 comments

  2. AI answer

    2026-06-13T04:17:17.1433333+00:00

    The output shows a normal, working network configuration with both IPv4 and IPv6 enabled:

    • Link speed: 100 Mbps up/down on the Intel(R) Ethernet Connection I217-LM.
    • IPv4:
      • Address: 192.168.11.226
      • DNS server: 192.168.11.1
    • IPv6:
      • Global unicast addresses (two of them):
        • fdca:c499:62a1::7fa
        • fdca:c499:62a1:0:d88d:1d62:699c:ddfe
      • Link-local address: fe80::5202:ec8a:15d7:a19%8
        • fe80::/64 is the standard IPv6 link-local prefix.
        • The %8 suffix is the interface index (scope ID) used by Windows to identify which network interface this link-local address belongs to.
      • IPv6 DNS server(s): fdca:c499:62a1::1 (listed twice but effectively the same server).

    Key points about what is shown:

    1. IPv6 address types
      • The fdca:c499:62a1::/64 addresses are unique local addresses (ULA), comparable to private IPv4 addresses (like 192.168.x.x). They are used within the local network and are not globally routable.
      • The link-local address fe80::5202:ec8a:15d7:a19%8 is used only on the local link (segment) for operations such as neighbor discovery and auto-configuration.
    2. Link-local scope and scope ID
      • IPv6 link-local addresses always start with fe80:: and have a scope limited to the local subnet.
      • On Windows, the scope ID (here 8) is appended with % to indicate which interface the address belongs to. This is required because the same link-local address could theoretically exist on multiple interfaces.
    3. DNS configuration
      • The system is configured to use both IPv4 and IPv6 DNS servers:
        • IPv4 DNS: 192.168.11.1
        • IPv6 DNS: fdca:c499:62a1::1
      • This is a typical dual-stack configuration where both IPv4 and IPv6 can be used for name resolution.
    4. Overall status
      • Nothing in the output indicates a misconfiguration. The presence of:
        • IPv4 private address (192.168.11.226)
        • IPv6 ULA addresses (fdca:...)
        • IPv6 link-local address (fe80:...%8)
        • Proper DNS entries is consistent with a correctly configured dual-stack home or small-office network.

    If troubleshooting connectivity, focus on:

    • Verifying that the default gateway and DNS servers respond (ping/tracert for IPv4, ping -6 for IPv6).
    • Ensuring the router supports and correctly advertises IPv6 (RA, DNS) if IPv6 connectivity is required beyond the local network.

    References:

    AI-generated content may be incorrect. Read our transparency notes for more information.

    Was this answer helpful?

    3 people found this answer helpful.

Your answer

Answers can be marked as 'Accepted' by the question author and 'Recommended' by moderators, which helps users know the answer solved the author's problem.