I agree that you missed the point entirely.
However ...
The NETSH command is useful information.
Thank you.

I've given up on DHCP and assigned a static address to my laptop on my network.

When I go into the field to connect to a network printer with a cross-over cable to test the NIC,
I don't want to change any settings on the printer.

I want to match the IP & subnet of the printer to my laptop to troubleshoot it.
And I don't want to waste time rebooting and switching back & forth.

Ps: The vbs for XP runs on Win2K but errors out.
Do one for Windows 2000 and I'll consider switching back to DHCP.