RE: NETSH Fails When Passed String Containing "="

Yes. This problem has not been fixed for Windows Server 2003. Part of the
reason is that there exists a workaround in using the mmc console to do this.
The other reason is that no customer has requested a fix to date.

You can open a support incident with PSS and reference report id 178569. If
you can provide a strong business case then the sustaining engineering group
may end up producing a hotfix. The bar to obtain a fix is pretty high so
there are no guarantees. Either way, you should receive a full refund (or
incident credit if permier) one the support incident is resolved.

It is fixed in Windows Server codenamed "Longhorn"

"Pete Davis" wrote:

> Good afternoon -
>
> I am having a bit of a problem with NETSH on Windows 2003 SP1 (Standard). I
> am using NETSH to manage a number of IP reservations, and it's a very useful
> tool, except for one problem; NETSH fails when you try to set a
> reservedoptionvalue (a string) containing an '='.
>
> An example of what I mean:
> dhcp server 127.0.0.1 scope 127.0.1.0 set reservedoptionvalue 127.0.1.5 176
> string "TFTPSERVER=127.0.9.9" (will fail)
>
> dhcp server 127.0.0.1 scope 127.0.1.0 set reservedoptionvalue 127.0.1.5 176
> string "SOME OTHER TEXT" (will work fine)
>
> I see this bug was "fixed in Windows 2000 SP4" according to the KB, but this
> is 2003 SP1. Surely I can't be the only person who has run into this problem?
> Am I doing something wrong? If anyone knows of a bugfix or a workaround I
> would be grateful. I am not looking forward to manually setting the options
> on several hundred reservations.
>
> Thanks,
>
> Pete


JohnGil (MSFT)

Does it work if you leave a space before the = ? I can remember having
that sort of problem before in netsh.

"JohnGil (MSFT)" <JohnGil (MSFT)@discussions.microsoft.com> wrote in message
news:884CF126-6621-4508-8BAB-(E-Mail Removed)...
> Yes. This problem has not been fixed for Windows Server 2003. Part of
> the
> reason is that there exists a workaround in using the mmc console to do
> this.
> The other reason is that no customer has requested a fix to date.
>
> You can open a support incident with PSS and reference report id 178569.
> If
> you can provide a strong business case then the sustaining engineering
> group
> may end up producing a hotfix. The bar to obtain a fix is pretty high so
> there are no guarantees. Either way, you should receive a full refund (or
> incident credit if permier) one the support incident is resolved.
>
> It is fixed in Windows Server codenamed "Longhorn"
>
> "Pete Davis" wrote:
>
>> Good afternoon -
>>
>> I am having a bit of a problem with NETSH on Windows 2003 SP1 (Standard).
>> I
>> am using NETSH to manage a number of IP reservations, and it's a very
>> useful
>> tool, except for one problem; NETSH fails when you try to set a
>> reservedoptionvalue (a string) containing an '='.
>>
>> An example of what I mean:
>> dhcp server 127.0.0.1 scope 127.0.1.0 set reservedoptionvalue 127.0.1.5
>> 176
>> string "TFTPSERVER=127.0.9.9" (will fail)
>>
>> dhcp server 127.0.0.1 scope 127.0.1.0 set reservedoptionvalue 127.0.1.5
>> 176
>> string "SOME OTHER TEXT" (will work fine)
>>
>> I see this bug was "fixed in Windows 2000 SP4" according to the KB, but
>> this
>> is 2003 SP1. Surely I can't be the only person who has run into this
>> problem?
>> Am I doing something wrong? If anyone knows of a bugfix or a workaround I
>> would be grateful. I am not looking forward to manually setting the
>> options
>> on several hundred reservations.
>>
>> Thanks,
>>
>> Pete