Netsh can't parse funny interface names

  • Thread starter Thread starter Mark K Vallevand
  • Start date Start date
M

Mark K Vallevand

I have two images. One to boot from CF and a much smaller one to boot from
USB ramdisk. On the CF image netsh works fine on commands like this:
netsh interface ip set address "Odd Name z=z" static 172.26.10.0
255.255.0.0
But, on the smaller USB ramdisk image, the same command complains that the
name "Odd name z" is not found. Its like it get stuck on the '=' in the
name. Remove the '=' from the name and netsh is OK.

I've added all the netsh stuff that Microsoft and this group has
recommended. Still no luck. I'm suspecting that there is a shell parsing
dll or something that is still missing.

Any ideas?

(Oh, the idea "don't use odd names" is implied.)

--
Regards.
Mark K Vallevand (e-mail address removed)

Beer is living proof that God loves us and wants us to be happy.
- Benjamin Franklin


THIS COMMUNICATION MAY CONTAIN CONFIDENTIAL AND/OR OTHERWISE PROPRIETARY
MATERIAL and is thus for use only by the intended recipient. If you received
this in error, please contact the sender and delete the e-mail and its
attachments from all computers.
 
No. I saw this one, and didn't try it. Both images are using the explorer
shell, so I didn't think it applied. I tried it now, and it made no
difference. In my USB ramdisk image, netsh doesn't like the '=' character
in interface names.

--
Regards.
Mark K Vallevand (e-mail address removed)

Beer is living proof that God loves us and wants us to be happy.
- Benjamin Franklin


THIS COMMUNICATION MAY CONTAIN CONFIDENTIAL AND/OR OTHERWISE PROPRIETARY
MATERIAL and is thus for use only by the intended recipient. If you received
this in error, please contact the sender and delete the e-mail and its
attachments from all computers.
 
Mark,

If your image are both Explorer Shell based then it is not the HrRenameConnection problem since the Explorer will call it for you.

You can try to compare registered netsh plug-ins on your both builds and see if there is any difference in the lists:
[HKLM\SOFTWARE\Microsoft\NetSh]
 
Nope. Extensions in the registry are the same.

--
Regards.
Mark K Vallevand (e-mail address removed)

Beer is living proof that God loves us and wants us to be happy.
- Benjamin Franklin


THIS COMMUNICATION MAY CONTAIN CONFIDENTIAL AND/OR OTHERWISE PROPRIETARY
MATERIAL and is thus for use only by the intended recipient. If you received
this in error, please contact the sender and delete the e-mail and its
attachments from all computers.


KM said:
Mark,

If your image are both Explorer Shell based then it is not the
HrRenameConnection problem since the Explorer will call it for you.

You can try to compare registered netsh plug-ins on your both builds and
see if there is any difference in the lists:
[HKLM\SOFTWARE\Microsoft\NetSh]

--
Regards,
KM, BSquare Corp.

No. I saw this one, and didn't try it. Both images are using the
explorer
shell, so I didn't think it applied. I tried it now, and it made no
difference. In my USB ramdisk image, netsh doesn't like the '='
character
in interface names.

--
Regards.
Mark K Vallevand (e-mail address removed)

Beer is living proof that God loves us and wants us to be happy.
- Benjamin Franklin


THIS COMMUNICATION MAY CONTAIN CONFIDENTIAL AND/OR OTHERWISE PROPRIETARY
MATERIAL and is thus for use only by the intended recipient. If you
received
this in error, please contact the sender and delete the e-mail and its
attachments from all computers.
Click to expand...
Click to expand...
 
Back
Top