MSDN Archive Home
Help and FAQs
All Resource Updates
Change History (all pages)
nvspbind is a tool for modifying network bindings from the command line. It is especially useful in Server Core environments with the Hyper-V role enabled.
It can be used to set the correct bindings for NICs used in Virtual Networks.
It can also be used to enable or disable specific bindings on any NIC and to query and change the NIC connection order.
It utilizes the INetCfg APIs documented on MSDN (http://msdn.microsoft.com/en-us/library/ms805265.aspx).
Most options are documented in the readme and nvpsbind.txt which download with the install.
To get help run “nvspbind.exe /?”
Hyper-V Network VSP Bind Application 6.1.7690.0.
Copyright (c) Microsoft Corporation. All rights reserved.
/n display NIC information only
/u unbind switch protocol from specified nic(s)
/b bind switch protocol to specified nic(s)
/d disable binding of specified protocol from specified nic(s)
/e enable binding of specified protocol to specified nic(s)
/r repair bindings on specified nic(s)
/o show NIC order for specified protocol
/+ move specified NIC up in binding order for specified protocol
/- move specified NIC down in binding order for specified protocol
/++ move specified NIC up to top of binding order for specified protocol
/-- move specified NIC down to bottom of binding order for specified protocol
There are three variations:
package.EXE is the standard 64 bit version for server core.
package.EXE is a 32 bit version that works on Vista and newer.
package.EXE is a reduced functionality 32 bit version that works on XP and newer.
Although I work for Microsoft as a developer on the Hyper-V team, I must point out that as the license tab indicates this tool and documentation are provided "as-is". You bear the risk of using it. No express warranties, guarantees or conditions are provided. It is not supported or endorsed by Microsoft Corporation and should be used at your own risk.
Mar 11 2010 at 6:05 PM
, version 15
Jan 29 2010 at 7:43 PM
It is finally posted on the downloads tab. I have also added NIC connection ordering.
Feb 1 2010 at 11:20 AM
I have actually written a similar utility to allow us to script NIC binding configuration.
I have a question I was hoping you might be able to answer.
There is functionality within the API to move a binding directly to the top in one call.
See the documentation for MoveBefore or MoveAfter here:
However, I haven't been able to make this work.
I notice that you also have left out this functionality.
Is this due to a bug in the API?
I'm guessing that this feature has been rarely tested as the NIC properties dialog does not expose this functionality.
I currently have a call open at the moment regarding this issue.
Feb 4 2010 at 2:20 PM
I added the MoveBefore/MoveAfter last week. You can use the /+ /- options to change the order. ncpa.cpl uses those methods as well so they are well tested. What is not working for you -- are you getting an error from some API call or is it simply failing to change?
Feb 12 2010 at 5:50 AM
Watch Kieth give a 10 minute video demo of NVSPBIND at http://bit.ly/cTHlvS
Feb 13 2010 at 11:24 AM
Really great tool - been looking for something like this for ages!
One minor niggle - could the errorcode returned be non-0 if the command fails to succeed? For example, I'm using it withe the /+ and /- options in a VBScript to order the bindings, and it would be great to return if (a) the command failed (b) the adapter was currently at the top or bottom respectively with an errorlevel!
Feb 26 2010 at 7:35 PM
The errorcode is now non-0 on many (hopefully all) failures. I've also fixed up the GUIDs so they are properly formatted.
Mar 4 2010 at 9:05 PM
this is great!!!...was looking for something like this for a long long time. however, the XP package fails to run on XP and 2003 machines!! has anyone been successful in running them on 2003 servers? works great on 2008..
Mar 5 2010 at 5:54 PM
I think I may have found something that is not desired behavior.
If you make a NIC's name shorter, nvspbind.exe remembers the extra characters in the old NIC name when it is run again.
-change a nic's name to 99999999999999999999
-change the same nic's name to 88
-run nvspbind.exe /n
-nvspbind.exe now thinks the nic's name is 88999999999999999999
Mar 5 2010 at 6:56 PM
xp version has been fixed.
Mar 10 2010 at 10:24 AM
Sorry for the late reply. I haven't been monitoring this thread.
I also managed to implement +/- functionality using MoveBefore/MoveAfter. However, these methods are supposed to support Move to top/bottom in one call by supplying NULL in the second parameter.
I can't seem to get this to work.
This particular functionality is not exposed in the ncpa.cpl.
Does that make sense?
Mar 11 2010 at 6:03 PM
Added ++ and -- options which move it to the top (++) or bottom (--). It does so by supplying NULL in the second parameter. I cannot repro the name issue described by Ritesh_13 – which OS are you using?
Mar 12 2010 at 3:35 PM
Thanks for the updated version... I've now found what I was doing wrong.
Basically I was trying to re-order the bindings for the ms_msserver component instead of the ms_tcpip protocol.
It makes sense that you can't move the bindings around further down the binding hierarchy.
You need to affect the top level protocol.
many, many thanks.
Mar 22 2010 at 3:31 PM
Sorry for the delayed response. MSDN login was down for a few days.
I verified it works fine on Server 2003 R2 SP2, Server 2003 x64 SP2, Server 2008 R2 and XP SP2 I am seeing the isse only on Server 2008 SP1 and Server 2008 SP2:
- after changing NIC name to 99999999999999999999
"Broadcom BCM5709S NetXtreme II GigE (NDIS VBD Client)"
- after changing NIC name to 88
"Broadcom BCM5709S NetXtreme II GigE (NDIS VBD Client)"
May 10 2010 at 4:15 PM
Hi, this is a really useful program. However I’m experiencing the same problem mrpopgun described in the discussion, this being that when you nvspbind with no parameters you get both enabled and disabled entries against some protocols. It looks like these only appear against protocols that are enabled, but it is confusing any chance of a fix?
Jun 25 2010 at 6:26 AM
Hi, the program incorrectly works if language Russia
"Broadcom NetLink (TM) Gigabit Ethernet"
enabled: ms_netbios ( disabled: ms_server ( disabled: ms_wl
bs ( enabled: nt_dsnpfd (Dsnpfd Driver)
enabled: ms_msclient ( enabled: ms_netbt ( enabled: ms_tc
pip ( enabled: ms_ndisuio (NDIS- enabled: ms_pppoe (
enabled: ms_rspndr ( enabled: ms_netmon (
And still, how to install ms_server for connection if it is not install
/e and /d is work
sorry my english
Aug 26 2010 at 2:13 PM
XP version: 6.1.7725.0
The command "nvspbind /o *" doesn't return any info about "ms_psched" when this is installed on a XP and are binded to one or more nic's.
Still it's possible to bind and unbind the ms_psched to one or all nics (*)
Could this be fixed or added to this binary?
Jan 13 2012 at 3:34 AM
I am experiencing the same issue as Ritesh_13 on Server 2008 SP2 (x86). Shortening the interface name leaves the characters from the original name in there, like "Local Area Connection" becoming "PublicArea Connection", when it should show "Public". The XP version worked successfully on the same system.
Jul 12 2013 at 5:11 PM
Is this a solution that is able to be used on Clients as well as Server Core?
Nov 2 2013 at 3:35 PM
So, if you are a user and not a programmer, here is the step by step.
I have a cluster with 3 nodes on Server 2008 R2 Core. Each with LOTS of NICs. When I configure the NIC's I REALLY need a specific NIC to be at TOP of ms_tcpip!
ipconfig /all > nvspbind-results.txt
nvspbind /n >> nvspbind-results.txt
nvspbind /o ms_tcpip >> nvspbind-results.txt
Search for IP of your NIC
Search for It's Name
Search for Name in NVSPBNID list at bottom
nvspbind /++ "NIC-Name-Here" ms_tcpip
Sign in to add a comment
Fri Jan 22 2010 at 8:00 AM
More Tags ...
Visual Studio 2005
Visual Studio 2008
Visual Studio 2010
Manage Your Profile
MSDN Flash Newsletter
© 2008 Microsoft Corporation. All rights reserved.