Tuesday, March 18, 2008

Netsh Is Not Working

If you encountered a problem where netsh couldn't pull the interface name and show the UID instead:
>netsh interface show interface
Admin State State Type Interface Name
-------------------------------------------------------------------------
Enabled Dedicated {38E7FAC8-FC0C-46CE-BA06-59C5323F1CEF}
Enabled Dedicated {59F5094B-3EC3-4F9B-892A-DF5F773292D9}
Enabled Dedicated {92C5A1C0-8075-486C-B8A8-AAF8914F7E96}
Enabled Dedicated {A9BC217F-9B17-44C9-843D-7C1B8471EAC3}
Enabled Internal Internal
Enabled Loopback Loopback

This inability to get the name of the interface is a problem since netsh will not work properly. The command only will take interface name, not UID.

The solution is outlined here.
I am unable to get this to work when I try to specify the interface name. "Local Area Connection" is considered invalid, and gets me no where. When I dump the netsh info, it lists all my interfaces as some gibberish like "{ADB7473C-C67B-49DE-B0D9-A25E990A39F5}", but even using that, and otherwise following the examples, the interface is called invalid.
i have enabled remote registry service then it's working [...]
>net start remoteregistry
The Remote Registry service was stopped successfully.

>netsh interface show interface
Admin State State Type Interface Name
-------------------------------------------------------------------------
Enabled Dedicated Local Area Connection
Enabled Dedicated VMware Virtual Ethernet Adapter (basic host-only support for VMnet1)
Enabled Dedicated VMware Virtual Ethernet Adapter (Network Address Translation (NAT) for VMnet8)
Enabled Dedicated Local Area Connection 2
Enabled Internal Internal
Enabled Loopback Loopback

This only took 2.5 hours of my life. No biggie.

No comments: