New
#1
Side effects of releasing/renewing IP addresses?
There is a fairly well know security package that is causing some users problems on Win 10 AU - browser connections get blocked. (Other TCP/IP connectivity is unaffected - just browsers.) A user of the product found that releasing and renewing DHCP-provided IP address - i.e., doing "ipconfig /release" followed by ipconfig /renew"" temporarily fixes the problem. Can someone explain to me what doing a release/renew does to Windows such that a program - even a program with deeply embedded hooks - would even know this has happened.
Obviously the computer will get a new IP address from DHCP. (Which, for many DHCP servers, will likely be the same as the old one.) If it gets a new address, will this make Windows switch it's network profile from "Private" to "Guest or Public"? (I know the security package will see that.)
And a few more questions relating to /release and /renew but unrelated to the problem:
I see there are IPv6 versions of /release and /renew. Does that mean that /release and /renew apply to only IPv4 addresses, or do those commands apply to both IPv4 and IPv6? If only IPv4, is there a way to release and renew all addresses? The DHCP server supplied a list of DNS servers as part of the DHCP handshake. Does the release and renew process also renew the list of DNS servers? If so, is there the same division of IPv4 and IPv6?