1. Forum
  2. Usenet
  3. ALT.COMP.OS.WINDOWS-10

  • Cannot Disable a Network i\Interface

    From Zaidy036@21:1/5 to All on Fri Dec 15 22:26:11 2023
    Win 10 Pro Desktop with last updates:

    Trying to make a batch to disable one network and then enable another.

    netsh interface show interface name=Ethernet > F:\_StatusE.txt

    Produces the following F:\_StatusE.txt

    Ethernet
    Type: Dedicated
    Administrative state: Enabled
    Connect state: Connected

    But the following will NOT work in Administrative CMD:
    netsh interface set interface Ethernet DISABLED

    Control panel could NOT disable it either.

    I searched but could not find an answer to the following:

    ***** What would make it impossible to disable a network interface?

    Anybody have a clue??

    --- SoupGate-Win32 v1.05
    * Origin: fsxNet Usenet Gateway (21:1/5)
  • From Paul@21:1/5 to All on Sat Dec 16 01:23:53 2023
    On 12/15/2023 10:26 PM, Zaidy036 wrote:
    Win 10 Pro Desktop with last updates:

    Trying to make a batch to disable one network and then enable another.

    netsh interface show interface name=Ethernet > F:\_StatusE.txt

    Produces the following F:\_StatusE.txt

    Ethernet
       Type:                 Dedicated
       Administrative state: Enabled
       Connect state:        Connected

    But the following will NOT work in Administrative CMD:
      netsh interface set interface Ethernet DISABLED

    Control panel could NOT disable it either.

    I searched but could not find an answer to the following:

    ***** What would make it impossible to disable a network interface?

    Anybody have a clue??

    There are more examples here.

    https://www.windowscentral.com/how-enable-or-disable-wi-fi-and-ethernet-network-adapters-windows-10

    One thing I've noticed, is occasionally, the parsing of Powershell,
    turns perfectly good commands into failures.

    If I type

    cmd.exe

    into my administrator Powershell terminal, then

    the-command-that-didnt-work-before

    then the thing works. This assumes the command is
    something command prompt friendly, like a netsh.

    I think I've had trouble with "bcdedit" for example.
    Something I was doing there, it would run, but it
    wasn't actually executing. And once I copy/pasted that
    into the cmd.exe subshell, it worked fine.

    Paul

    --- SoupGate-Win32 v1.05
    * Origin: fsxNet Usenet Gateway (21:1/5)
  • From Zaidy036@21:1/5 to All on Sat Dec 16 14:20:55 2023
    On 12/15/2023 10:26 PM, Zaidy036 wrote:
    Win 10 Pro Desktop with last updates:

    Trying to make a batch to disable one network and then enable another.

    netsh interface show interface name=Ethernet > F:\_StatusE.txt

    Produces the following F:\_StatusE.txt

    Ethernet
       Type:                 Dedicated
       Administrative state: Enabled
       Connect state:        Connected

    But the following will NOT work in Administrative CMD:
      netsh interface set interface Ethernet DISABLED

    Control panel could NOT disable it either.

    I searched but could not find an answer to the following:

    ***** What would make it impossible to disable a network interface?

    Anybody have a clue??
    A few more tests this morning with no help. Included closing all running program windows (FireFox, T-Bird, Notepad++)

    NETSH is working because 'netsh interface show interface' shows:
    Admin State State Type Interface Name ------------------------------------------------------------------------- Disabled Disconnected Dedicated Wi-Fi
    Enabled Connected Dedicated Ethernet
    Enabled Connected Dedicated vEthernet (Ethernet)

    I ran /SFC /VERIFY which found some problems and then /SFC /SCANNOW for correction but after still no success using NETSH and the Control Panel
    will not Disable or Enable any interface.

    I have tried the following in an Admin CMD window:
    netsh interface set interface Ethernet admin=DISABLED
    netsh interface set interface Ethernet DISABLED
    POWERSHELL Get-NetAdapter -Name ethernet* | Disable-NetAdapter
    and all result in a blinking cursor hang necessitating window closure
    and when restarting CMD no change in interface report.

    There must be some setting that locks my desktop network to Ethernet in Properties or gpedit.msc or ?

    --- SoupGate-Win32 v1.05
    * Origin: fsxNet Usenet Gateway (21:1/5)
  • From Andy Burns@21:1/5 to All on Sat Dec 16 19:31:59 2023
    Zaidy036 wrote:

    There must be some setting that locks my desktop network to Ethernet in Properties or gpedit.msc or ?

    Not sure why you conclude that ... after all if you unplugged the wired ethernet, or turned off the WiFi access point, that amounts to about the
    same thing ... you wouldn't expect the desktop as a whole to lock up,
    just things like web browser, or email client to lose connectivity ...

    --- SoupGate-Win32 v1.05
    * Origin: fsxNet Usenet Gateway (21:1/5)
  • From Zaidy036@21:1/5 to All on Sat Dec 16 15:28:45 2023
    On 12/15/2023 10:26 PM, Zaidy036 wrote:

    Attempted Restart but after 5 minutes rotating indicator still on screen
    so forced power off with button and then after a minute used power
    button to start.

    Now following work:
    POWERSHELL netsh interface show interface
    Get-NetAdapter -Name vEthernet* | Disable-NetAdapter
    Get-NetAdapter -Name Wi-Fi | Enable-NetAdapter

    Did above in sequence:
    Admin State State Type Interface Name ------------------------------------------------------------------------- Enabled Disconnected Dedicated Wi-Fi
    Disabled Disconnected Dedicated Ethernet
    Disabled Disconnected Dedicated vEthernet (Wi-Fi)

    After connection selected
    Admin State State Type Interface Name ------------------------------------------------------------------------- Enabled Connected Dedicated Wi-Fi
    Disabled Disconnected Dedicated Ethernet
    Enabled Connected Dedicated vEthernet (Wi-Fi)

    vEthernet was originally (Ethernet), now (Wi-Fi) so maybe that is why it
    is now connected.

    Will make batch to toggle between Ethernet/Wi-Fi using PS and see what
    happens.

    --- SoupGate-Win32 v1.05
    * Origin: fsxNet Usenet Gateway (21:1/5)
  • From Zaidy036@21:1/5 to All on Sat Dec 16 15:33:19 2023
    On 12/16/2023 2:20 PM, Zaidy036 wrote:

    On 12/15/2023 10:26 PM, Zaidy036 wrote:

    Attempted Restart but after 5 minutes rotating indicator still on screen
    so forced power off with button and then after a minute used power
    button to start.

    Now following work:
    POWERSHELL netsh interface show interface
    Get-NetAdapter -Name vEthernet* | Disable-NetAdapter
    Get-NetAdapter -Name Wi-Fi | Enable-NetAdapter

    Did above in sequence:
    Admin State State Type Interface Name ------------------------------------------------------------------------- Enabled Disconnected Dedicated Wi-Fi
    Disabled Disconnected Dedicated Ethernet
    Disabled Disconnected Dedicated vEthernet (Wi-Fi)

    After connection selected
    Admin State State Type Interface Name ------------------------------------------------------------------------- Enabled Connected Dedicated Wi-Fi
    Disabled Disconnected Dedicated Ethernet
    Enabled Connected Dedicated vEthernet (Wi-Fi)

    vEthernet was originally (Ethernet), now (Wi-Fi) so maybe that is why it
    is now connected.

    Will make batch to toggle between Ethernet/Wi-Fi using PS and see what
    happens.

    --- SoupGate-Win32 v1.05
    * Origin: fsxNet Usenet Gateway (21:1/5)
  • From Zaidy036@21:1/5 to All on Sat Dec 16 15:34:42 2023
    On 12/16/2023 3:28 PM, Zaidy036 wrote:
    On 12/15/2023 10:26 PM, Zaidy036 wrote:

    Attempted Restart but after 5 minutes rotating indicator still on screen
    so forced power off with button and then after a minute used power
    button to start.

    Now following work:
       POWERSHELL netsh interface show interface
       Get-NetAdapter -Name vEthernet* | Disable-NetAdapter
       Get-NetAdapter -Name Wi-Fi | Enable-NetAdapter

    Did above in sequence:
    Admin State    State          Type             Interface Name
    ------------------------------------------------------------------------- Enabled        Disconnected   Dedicated        Wi-Fi Disabled       Disconnected   Dedicated        Ethernet Disabled       Disconnected   Dedicated        vEthernet (Wi-Fi)

    After connection selected
    Admin State    State          Type             Interface Name
    ------------------------------------------------------------------------- Enabled        Connected      Dedicated        Wi-Fi Disabled       Disconnected   Dedicated        Ethernet Enabled        Connected      Dedicated        vEthernet (Wi-Fi)

    vEthernet was originally (Ethernet), now (Wi-Fi) so maybe that is why it
    is now connected.

    Will make batch to toggle between Ethernet/Wi-Fi using PS and see what happens.
    Sorry for new thread. Copied to original

    --- SoupGate-Win32 v1.05
    * Origin: fsxNet Usenet Gateway (21:1/5)
  • From knuttle@21:1/5 to Andy Burns on Sat Dec 16 16:36:49 2023
    On 12/16/2023 2:31 PM, Andy Burns wrote:
    Zaidy036 wrote:

    There must be some setting that locks my desktop network to Ethernet
    in Properties or gpedit.msc or ?

    Not sure why you conclude that ... after all if you unplugged the wired ethernet, or turned off the WiFi access point, that amounts to about the
    same thing ... you wouldn't expect the desktop as a whole to lock up,
    just things like web browser, or email client to lose connectivity ...


    There have been many suggestions and lines of code, but when every I
    want to disable a connection I go to the Notifications window in the
    lower right hand tool bar (White box) select the network that I am
    connect to and click disconnect. Make sure that the you disable the
    parameter Connect Automatically at start.

    To connect to a different network click connect.

    If you want to completely disable that port go toe Control Panel>
    Network and Internet > Network Connections. right click the port you
    want to disable and select disable

    --- SoupGate-Win32 v1.05
    * Origin: fsxNet Usenet Gateway (21:1/5)
  • From Zaidy036@21:1/5 to All on Sat Dec 16 16:42:36 2023
    On 12/16/2023 3:33 PM, Zaidy036 wrote:
    On 12/16/2023 2:20 PM, Zaidy036 wrote:

    On 12/15/2023 10:26 PM, Zaidy036 wrote:

    Attempted Restart but after 5 minutes rotating indicator still on screen
    so forced power off with button and then after a minute used power
    button to start.

    Now following work:
       POWERSHELL netsh interface show interface
       Get-NetAdapter -Name vEthernet* | Disable-NetAdapter
       Get-NetAdapter -Name Wi-Fi | Enable-NetAdapter

    Did above in sequence:
    Admin State    State          Type             Interface Name
    ------------------------------------------------------------------------- Enabled        Disconnected   Dedicated        Wi-Fi Disabled       Disconnected   Dedicated        Ethernet Disabled       Disconnected   Dedicated        vEthernet (Wi-Fi)

    After connection selected
    Admin State    State          Type             Interface Name
    ------------------------------------------------------------------------- Enabled        Connected      Dedicated        Wi-Fi Disabled       Disconnected   Dedicated        Ethernet Enabled        Connected      Dedicated        vEthernet (Wi-Fi)

    vEthernet was originally (Ethernet), now (Wi-Fi) so maybe that is why it
    is now connected.

    Will make batch to toggle between Ethernet/Wi-Fi using PS and see what happens.


    I do not remember but this may have been the first Restart after the
    /SFC /SCANNOW and repairs were only effective then.

    --- SoupGate-Win32 v1.05
    * Origin: fsxNet Usenet Gateway (21:1/5)
  • From Paul@21:1/5 to All on Sun Dec 17 04:45:07 2023
    On 12/16/2023 2:20 PM, Zaidy036 wrote:
    On 12/15/2023 10:26 PM, Zaidy036 wrote:
    Win 10 Pro Desktop with last updates:

    Trying to make a batch to disable one network and then enable another.

    netsh interface show interface name=Ethernet > F:\_StatusE.txt

    Produces the following F:\_StatusE.txt

    Ethernet
        Type:                 Dedicated
        Administrative state: Enabled
        Connect state:        Connected

    But the following will NOT work in Administrative CMD:
       netsh interface set interface Ethernet DISABLED

    Control panel could NOT disable it either.

    I searched but could not find an answer to the following:

    ***** What would make it impossible to disable a network interface?

    Anybody have a clue??
    A few more tests this morning with no help. Included closing all running program windows (FireFox, T-Bird, Notepad++)

    NETSH is working because 'netsh interface show interface' shows:
    Admin State    State          Type             Interface Name
    ------------------------------------------------------------------------- Disabled       Disconnected   Dedicated        Wi-Fi Enabled        Connected      Dedicated        Ethernet Enabled        Connected      Dedicated        vEthernet (Ethernet)

    I ran /SFC /VERIFY which found some problems and then /SFC /SCANNOW for correction but after still no success using NETSH and the Control Panel will not Disable or Enable any interface.

    I have tried the following in an Admin CMD window:
       netsh interface set interface Ethernet admin=DISABLED
       netsh interface set interface Ethernet DISABLED
       POWERSHELL Get-NetAdapter -Name ethernet* | Disable-NetAdapter
    and all result in a blinking cursor hang necessitating window closure and when restarting CMD no change in interface report.

    There must be some setting that locks my desktop network to Ethernet in Properties or gpedit.msc or ?

    As another option, I've been having trouble with my RealTek GbE,
    and I switched it off in the BIOS, in the peripheral section.
    Retail motherboards (home build) have that option. I've frequently
    in the past, turned off the Firewire port, since I have so little
    Firewire hardware.

    *******

    If you switch off an item in the BIOS, you can remove the entry
    from Device Manager with this. I removed both the hidden (old)
    RealTek entry, as well as the RealTek #2 entry. And then, if
    I wanted to, I could turn the NIC back on in the BIOS, and
    Windows "rediscovers" the port and labels it RealTek without
    the #2 on the end :-) Nice.

    https://www.uwe-sieber.de/files/DeviceCleanup.zip

    This did not cure my problem, of the port dropping
    a minute or two after the desktop comes up. No packets
    leave on the port (DNS or otherwise), once the NIC is
    somehow disconnected. I can attempt ping and it says
    host unreachable and the NIC LED does not flash.

    Using ProcMon, I can see some activity from WinHTTP Web Proxy AutoDiscovery,
    at about the same point in time. But nothing in Event Viewer indicates
    a collision of wills. Only the globe icon on the Taskbar, dumps
    an entry in Event Viewer stating that the connectivity test is
    failing at that point in time. It can't reach the Microsoft test address.

    My emergency NIC, an ASIX based device, is working fine and that's
    how I can post.

    The NIC also works fine in Linux. Not a hardware problem.

    Paul

    --- SoupGate-Win32 v1.05
    * Origin: fsxNet Usenet Gateway (21:1/5)