Side effects of releasing/renewing IP addresses?

Page 2 of 2 FirstFirst 12

  1. Posts : 720
    Win10 x64 Pro - 2 desktops, 2 laptops
    Thread Starter
       #11

    bro67 said:
    Again you need to state what software you are using for Security, because yes it does matter. Being so cryptic and wanting to beat around the bush in trying to some how place all of this on Microsoft, when it is not always the case, is not going to change the fact that if you have a serious problem and want help, you have to do your part by putting in your post pertinent information, such as what Internet Security software that you are running on your computer.
    You've apparently missed the point of my posting. I'm not blaming Microsoft of anything. I'm not blaming the security software of anything, either. And I don't have the problem I mentioned or I'd do some experimenting myself.

    I saw the report of a problem that didn't make any sense, realized I didn't know what ipconfig /release and /renew actually do, and wanted to undo that ignorance. I've now done some experimentation, gained a little knowledge, and found that my ignorance was even greater than I supposed.

    The /release does have a significant side effect. Since it releases the IPv4 addrs (including default gateway and DNS servers) it obviously isolates the PC from the (IPv4) network. Windows reverts to Automatic Private IP Addressing (APIPA) and gives the adapter an addr in the APIPA range - 169.254.0.1 - 169.254.255.254. So even if the PC could communicate with the router it would no longer be on the router's subnet. This all goes back to normal with the /renew. (I expected Windows to start using a "public" network profile, but it does not.)

    The IPv6 addrs were not effected by any of this. Surprisingly, they were also not effected by /release6, but ISATAP tunneling shut down. Ipconfig /renew6 hung for a long time, and didn't seem to do anything except find an IPv6 DNS server ... and caused a complaint from the Teredo tunneling service.

    This probably makes sence to someone that really understands IPv6, but that's not me.
      My Computer


  2. Posts : 720
    Win10 x64 Pro - 2 desktops, 2 laptops
    Thread Starter
       #12

    alphanumeric said:
    ... What IP address you get the second time around depends on what your getting it from. If your router reserves an IP for each device based on its MAC address you'll just get the same IP again. If not it will be the next available one from the IP scope set on the router. If there is no reserving IP addresses its first come first serve. They are given out in order as each device asks for one, from lowest to highest in the scope set.
    Thank you. Our postings overlapped. I believe the DHCP server in my router reserves the IP addrs for (at least) the length of their lease - 24 hours. So if I disconnect and reconnect within 24 hours it will give the same address.
      My Computer


  3. Posts : 1,255
    Windows 10 Pro
       #13

    Normally there should be no ill effects from releasing and renewing an IP address. Network communication is inherently unreliable and properly designed software will handle any temporary disruptions this may cause.
      My Computer


  4. Posts : 9,765
    Mac OS Catalina
       #14

    pokeefe0001 said:
    You've apparently missed the point of my posting. I'm not blaming Microsoft of anything. I'm not blaming the security software of anything, either. And I don't have the problem I mentioned or I'd do some experimenting myself.

    I saw the report of a problem that didn't make any sense, realized I didn't know what ipconfig /release and /renew actually do, and wanted to undo that ignorance. I've now done some experimentation, gained a little knowledge, and found that my ignorance was even greater than I supposed.

    The /release does have a significant side effect. Since it releases the IPv4 addrs (including default gateway and DNS servers) it obviously isolates the PC from the (IPv4) network. Windows reverts to Automatic Private IP Addressing (APIPA) and gives the adapter an addr in the APIPA range - 169.254.0.1 - 169.254.255.254. So even if the PC could communicate with the router it would no longer be on the router's subnet. This all goes back to normal with the /renew. (I expected Windows to start using a "public" network profile, but it does not.)

    The IPv6 addrs were not effected by any of this. Surprisingly, they were also not effected by /release6, but ISATAP tunneling shut down. Ipconfig /renew6 hung for a long time, and didn't seem to do anything except find an IPv6 DNS server ... and caused a complaint from the Teredo tunneling service.

    This probably makes sence to someone that really understands IPv6, but that's not me.
    Again the only one missing the point here is you. So what is this widely known Security Software, that there are only about 20 or so different Security suites out there and none of them have anything to do with Windows, same as Windows has nothing to do with them. Also a 169 IP just means that the Ethernet NIC did not get a real IP and still has nothing to do with Windows or some unclaimed Security software.

    The fact remains that you are being so cryptic about your original post, we can all take it that you just wanted to raise your post count for no reason at all.
      My Computer


  5. Posts : 9,765
    Mac OS Catalina
       #15

    pokeefe0001 said:
    Thank you. Our postings overlapped. I believe the DHCP server in my router reserves the IP addrs for (at least) the length of their lease - 24 hours. So if I disconnect and reconnect within 24 hours it will give the same address.
    All modern day Gateways reserve a lease up to 24 hours, unless your either do a hard reset or reboot it. Some even go as far as reserving them longer if the MAC ID of the device matches a IP in IPTables that was used up to 30 days prior.
      My Computer


 

  Related Discussions
Our Sites
Site Links
About Us
Windows 10 Forums is an independent web site and has not been authorized, sponsored, or otherwise approved by Microsoft Corporation. "Windows 10" and related materials are trademarks of Microsoft Corp.

© Designer Media Ltd
All times are GMT -5. The time now is 17:38.
Find Us




Windows 10 Forums