New
#1
Cannot change an IP address other than directly editing the registry
Hi, all.
I have run into a situation I wish I knew how to get out of. One of my systems won't allow me to change the IP address (static) or use ipconfig /renew to pull a new one via DHCP (dynamic). If I try to change IPv4 settings, every time I try, it wants me to reboot the machine, and this is regardless of which interface I try it on (ordinarily, there are several additional "interfaces" on this machine, usually pseudo-interfaces software packages provide, though see below on what I did to deal with those and try to eliminate them as possible problems).
The only way I can reliably change the IP address on this system is editing the registry for that particular interface and rebooting.
I've tried the usual
stuff. but to no avail. I've also tried updating, uninstalling, then reinstalling the ethernet controller driver, in this case, an on-board RealTek RTL8168. And to be EXTRA safe, I even went so far as to remove any software that creates additional "adapters", e.g. LogMeIn Hamachi, VMware Player, VirtualBox, etc. I'm not even afraid to edit the registry to get rid of all the crap these left behind after I uninstalled them. When they are there, some already have IP addresses assigned to them (e.g. the VirtualBox host-only network has a static, but when I check IPv4 settings, it says it's in DHCP, even though it's not). Hell, I've gone so far as to do this:Code:netsh int ip reset blah.txt netsh winsock reset
And my machine STILL insists on giving me the finger.Code:netsh int ipv4 uninstall netsh int ipv4 install
Here's the output of netsh command prompt wizardry when I show then try to disable the interface:
The system in question is running Windows 7 Ultimate 64-bit.Code:C:\Users\(redacted)>netsh int show int "On-board wired GBE" On-board wired GBE Type: Dedicated Administrative state: Enabled Connect state: Connected C:\Users\(redacted)>netsh int set int "On-board wired GBE" disable An interface with this name is not registered with the router.
Also, just so everyone knows, I prefer static IPs. Right now, it's the only way that works since DHCP won't.
Ordinarily, I'm pretty good with stuff like this (in other words, I'm no newbie; fly as high as you feel the need to, and I am not afraid of command lines), but this one has me stumped.
Any ideas?
--IJ.