Super User is a question and answer site for computer enthusiasts and power users. Join them; it only takes a minute:

Sign up
Here's how it works:
  1. Anybody can ask a question
  2. Anybody can answer
  3. The best answers are voted up and rise to the top

There are a few ways you can list network interfaces via commandline. For example:

netsh interface show interface
netsh interface ip show interfaces
ipconfig |findstr "adapter"

For Mobile Broadband Connections:

netsh mbn show interfaces

All of those will list network interfaces as long as they are enabled. If you disable an interface (ie 'netsh interface set interface "interfaceName" admin=disable'), it will no longer be listed with those commands.

My question is this: how do you list an interface that has been disabled? Something that works for Mobile Broadband connections as well as regular connections would be great.

share|improve this question
    
If you have found the solution please post as a self-answer and accept it. – Jeffrey Lin Jul 15 '13 at 0:22
    
had to wait 8 hours to add my answer. i still don't know if my solution works for MBN connections though. I'll have to wait another 2 days to mark my answer as accepted – Lectrode Jul 15 '13 at 7:53
up vote 3 down vote accepted

I found this command seems to work:

wmic nic get NetConnectionID

It shows regular connection interfaces including those that have been disabled.

share|improve this answer
    
I don't have an MBN connection to test. Does anyone know if this lists disabled Mobile Broadband connections? – Lectrode Jul 15 '13 at 7:46

Make sure that you are using an elevated command-prompt, otherwise it won’t have access to everything and may not be able to show disabled interfaces as expected (figure 1). For example, I was unable to use the admin=disable parameter from a non-elevated prompt.

Technically, it should still be able to read the NICs from a non-elevated prompt—I was able to see all interfaces (figure 2) including disabled ones—so your system may have some policies or something in place that prevents it from working from a non-elevated one.


Figure 1: Screenshot of elevated command prompt showing disabled interfaces

Screenshot of elevated command prompt showing disabled interfaces

Figure 2: Screenshot of non-elevated command prompt showing disabled interfaces

Screenshot of non-elevated command prompt showing disabled interfaces

share|improve this answer

You must log in to answer this question.

Not the answer you're looking for? Browse other questions tagged .