September 20, 201114 yr I have 2 machines. One running Win7 x86 and the other running Win7 x64.I can't figure this out but the command that works with x86 to disable a wired NIC simply does not work on the x64 version. I of course changed the name of the nic appropriately. The command line I used on the x86 was .....netsh interface set interface "nvidia" DISABLED this works perfectly.the same on x64 was ...netsh interface set interface "realtek" DISABLEDThis simply does not work and the cursor simply blinks !!!I wonder why M$ engineers thought it prudent to have them work differently. Only reason I use x64 version is its capacity to access more than 3.2 GB of ram. I don;t see any other advantage to it.Any and all help / suggestions welcome.
September 20, 201114 yr netsh interface set interface "Local Area Connection" DISABLEDWorked just fine on my Win7 x64 system.
September 21, 201114 yr Author @MagicAndreI have tried all kinds of variation after thoroughly reading the netsh.chm and Netsh_TechnicalReference.chm. including the one suggested by you. I have only mentioned the actual command line that WORKED on the 32 bit version. And it does so in less than a couple of seconds.@IcemanNDI think I will try your variation by removing the name I have assigned to the NIC and letting it default to "Local Area Connection".Thanks to both of you.
September 21, 201114 yr you must set the name of the connection as you see it the network sharing center
September 21, 201114 yr Author you must set the name of the connection as you see it the network sharing centerI have Realtek Gigalan chip on board and a Belkin wifi pci addon card. For quick identification I named them Realtek and Belkin ( I monitor the transfer rates by 2 instances of NetWorx portable.) As I mentioned earlier the command did not work with the specified name so am planning to remove the name and revert to the default name assigned by windows, namely "Local Area Connection" and see. Well after all it is M$ Windows, so all is not easy and hunky dory!.
September 21, 201114 yr Well, I cannot repro this either, for what it's worth. No matter what I name it, it just works.
September 22, 201114 yr Author I guess I will have to live with it, hopefully only till I reinstall the OS.
October 12, 201114 yr Author I have no idea what happened but the command that worked on x86 and not on x64 suddenly started working on x64 also.I just realised that this is M$ Windows after all
Create an account or sign in to comment