Ah, I suppose other options could include:
* modify the registry directly with the new static IP (reg add .....) and
then force a restart of the networking service (sc ....) to make it re-read
the configuration
* try WMI programmatically to see exactly which API or method is failing
and what the error code is
* debug the network properties GUI dialog to see how it sets the static IP
(assuming the GUI works) then develop a program using those methods
MHL
On Mon, Jun 3, 2013 at 12:46 PM, George M. Garner Jr. <
ggarner_online(a)gmgsystemsinc.com> wrote:
WMI and powershell are optional components which may be added. In this
particular case I do have both WMI and power shell available and already
tried the WMI commands which you suggest, with the same result.
This is my own box that I am testing on, btw. (not the client's system :-)
) so no problem with malware interfering with the commands.
Thanks for responding.
______________________________**_________________
Vol-users mailing list
Vol-users(a)volatilityfoundation.org
http://lists.volatilesystems.**com/mailman/listinfo/vol-users<http://lis…