1. Forum
  2. USENET
  3. alt.comp.os.windows-10

  • Re: Change name of adapter (not its interface alias)

    From Char Jackson@none@none.invalid to alt.comp.os.windows-10 on Fri Dec 19 01:12:13 2025
    From Newsgroup: alt.comp.os.windows-10

    On Wed, 17 Dec 2025 21:33:30 -0600, VanguardLH <V@nguard.LH> wrote:

    Got time to address this issue. What you mentioned worked. There were
    2 network profiles that had the names of the SSIDs in the wifi cable
    modem, but they were actually RJ45 Ethernet wired connections as ports
    on the backpanel of the computer. I renamed both of them: HomeEther1 >(connected) and HomeEther2 (not connected).

    I'm not yet using the 2nd one (unconnected), and probably won't as I
    don't need to bridge through this desktop to another segment in my
    intranet nor have my desktop PC act as a router or firewall to other
    intranet hosts. The mobo had other features that I wanted, and happened
    to have 2 Ethernet ports (for bridging, I guess).

    I used to have a mobo with two network interfaces. I used the second one
    to access a NAS, which was on a separate network segment. By using two
    physical interfaces, each of them could run at full speed without
    affecting the other. You can do everything with a single interface that
    you can do with dual interfaces, but you may not see the best possible
    overall speed if you're stacking multiple networks on a single
    interface.

    I didn't delete any of the other network profiles. A couple were for
    Proton VPN. Didn't know what the other few were for, and was not
    interested in hunting them down.

    Thanks again. Renaming the network profiles makes it far more clear to
    which I'm connected.

    --- Synchronet 3.21a-Linux NewsLink 1.2