Cannot change an IP address other than directly editing the registry

Kaktussoft · 26 Jun 2013

IRJustman said:

Forgot to mention that a "netsh winsock reset" now yields the desired results in the return message, but not QUITE the fullly-desired results. Everything ELSE works, though.

So "netsh winsock reset" works. What "fullly-desired results" are missing?

Kaktussoft · 26 Jun 2013

IRJustman said:

Still no dice. Still wants a reboot, and it "shows" as being DHCP, even though it's static. Does the same even if I'm logged in as administrator. However, the other issues I was having owing to a SERIOUSLY hosed Winsock catalog are gone. I'll continue to look at that other article as well.

--IJ.

So you gave it a static address succesfully. It asks a reboot, but it was active immediately, no reboot necessary. Did you check registry if ip address is really there?

You reboot and then it was dhcp again..strange. Did something remove the ip address form registry? If so: Edit in registry the ip address manually and look if it keeps the value in registry after reboot.

Kaktussoft · 26 Jun 2013

IRJustman said:

Code:

C:\Users\(redacted)>netsh int set int "On-board wired GBE" disable
An interface with this name is not registered with the router.

Any ideas?

--IJ.

This command 'netsh int set int "On-board wired GBE" disable' has to be run from elevated command prompt!

jobeard · 02 Jul 2013

hmm; I prefer fixed addresses too so I can have special firewall rules for specific ranges of ip addresses.

To effect fixed IPs, I let the DHCP in the router interact with Address Reservation list, using the MAC address of the NIC to predict the desired IP address. As I'm on a laptop, this works well too for hotspot usage as the router is still at home and all that stuff doesn't interfere with hotspot configurations.

IRJustman · 20 Jul 2013

Sorry about the late response; Real Life(R) got in the way.

In any event, I did manage to figure out a lot of my issues. It mainly has to do with permissions on the \HKLM\System\ControlSetxxx\Services\TCPIP key. It turns out that some of the permissions were missing. I read off the permissions from a known-working Windows 7 system, and now I can not only view, but change, the IPv4 configuration just fine.

~~I notice I can't re-add "Dhcp" as an entity as having permission into the services\Dhcp and services\TCPIP keys. However, setting obtain automatically still seems to work fine.~~ EDIT: I figured this one out finally (thanks, Google!), so now both keys have all pertinent permissions set correctly.

About the only thing left is that I STILL have to reboot to get things, which is now an annoyance but still deal-with-able. I'll refer to the link earlier in the thread for more info.

--IJ.

IRJustman · 21 Jul 2013

And just another update, I can now do a

Code:

C:\>netsh int ip reset blah.txt
C:\>netsh winsock reset

without errors (HKLM\System\ControlSetxxx\Services\Winsock and HKLM\System\ControlSetxxx\Services\Winsock2 both had incorrect permissions, but I have since fixed them), but it still isn't fixing this last issue of needing a reboot to "finalize" anything. As far as I can tell, it's still taking my change requests and putting them into effect right away (visible both in ipconfig (/all) and, thanks to my registry permissions jockeying, in TCP/IP settings).

--IJ.

IRJustman · 21 Jul 2013

As of right now, everything is now working as they should. Found that Tweaking.com's Windows Repair (All In One) finished the job by resetting the registry's permissions to a reasonably-close-to-default state (which I now have to bugger up for my own purposes *evil grin*). Now, TCP/IP settings work as they should again.

--IJ.