Will Windows renew IP address sometime after “ipconfig /release”?












2















On a Windows 2000 PC, I did a "ipconfig /release" to disconnect it from the network. After about 6 hours, I checked it again and it was still disconnected. But then about 17 hours after that, I checked it again and it had renewed the IP address and was back on the network. I never did a "ipconfig /renew", so is Windows supposed to renew the IP address automatically some time after a "ipconfig /release"?



Or could there be some malware on this computer that detected it was off the network and renewed the IP address? (My ISP emailed me saying it detected malware on one of our computers so I am trying to figure out which computer it is.)










share|improve this question




















  • 1





    Had you woken/restarted the computer during the 17hrs? Either would possibly prompt Windows to wake the NIC and renew an IP...

    – Kinnectus
    Jul 22 '14 at 7:00











  • @BigChris This computer doesn't go into sleep mode, and it was powered on the entire 17 hours. Windows is also configured to not put the NIC into any power saving mode.

    – pacoverflow
    Jul 22 '14 at 7:05
















2















On a Windows 2000 PC, I did a "ipconfig /release" to disconnect it from the network. After about 6 hours, I checked it again and it was still disconnected. But then about 17 hours after that, I checked it again and it had renewed the IP address and was back on the network. I never did a "ipconfig /renew", so is Windows supposed to renew the IP address automatically some time after a "ipconfig /release"?



Or could there be some malware on this computer that detected it was off the network and renewed the IP address? (My ISP emailed me saying it detected malware on one of our computers so I am trying to figure out which computer it is.)










share|improve this question




















  • 1





    Had you woken/restarted the computer during the 17hrs? Either would possibly prompt Windows to wake the NIC and renew an IP...

    – Kinnectus
    Jul 22 '14 at 7:00











  • @BigChris This computer doesn't go into sleep mode, and it was powered on the entire 17 hours. Windows is also configured to not put the NIC into any power saving mode.

    – pacoverflow
    Jul 22 '14 at 7:05














2












2








2








On a Windows 2000 PC, I did a "ipconfig /release" to disconnect it from the network. After about 6 hours, I checked it again and it was still disconnected. But then about 17 hours after that, I checked it again and it had renewed the IP address and was back on the network. I never did a "ipconfig /renew", so is Windows supposed to renew the IP address automatically some time after a "ipconfig /release"?



Or could there be some malware on this computer that detected it was off the network and renewed the IP address? (My ISP emailed me saying it detected malware on one of our computers so I am trying to figure out which computer it is.)










share|improve this question
















On a Windows 2000 PC, I did a "ipconfig /release" to disconnect it from the network. After about 6 hours, I checked it again and it was still disconnected. But then about 17 hours after that, I checked it again and it had renewed the IP address and was back on the network. I never did a "ipconfig /renew", so is Windows supposed to renew the IP address automatically some time after a "ipconfig /release"?



Or could there be some malware on this computer that detected it was off the network and renewed the IP address? (My ISP emailed me saying it detected malware on one of our computers so I am trying to figure out which computer it is.)







windows dhcp ip-address






share|improve this question















share|improve this question













share|improve this question




share|improve this question








edited Jul 22 '14 at 7:11







pacoverflow

















asked Jul 22 '14 at 6:51









pacoverflowpacoverflow

71531636




71531636








  • 1





    Had you woken/restarted the computer during the 17hrs? Either would possibly prompt Windows to wake the NIC and renew an IP...

    – Kinnectus
    Jul 22 '14 at 7:00











  • @BigChris This computer doesn't go into sleep mode, and it was powered on the entire 17 hours. Windows is also configured to not put the NIC into any power saving mode.

    – pacoverflow
    Jul 22 '14 at 7:05














  • 1





    Had you woken/restarted the computer during the 17hrs? Either would possibly prompt Windows to wake the NIC and renew an IP...

    – Kinnectus
    Jul 22 '14 at 7:00











  • @BigChris This computer doesn't go into sleep mode, and it was powered on the entire 17 hours. Windows is also configured to not put the NIC into any power saving mode.

    – pacoverflow
    Jul 22 '14 at 7:05








1




1





Had you woken/restarted the computer during the 17hrs? Either would possibly prompt Windows to wake the NIC and renew an IP...

– Kinnectus
Jul 22 '14 at 7:00





Had you woken/restarted the computer during the 17hrs? Either would possibly prompt Windows to wake the NIC and renew an IP...

– Kinnectus
Jul 22 '14 at 7:00













@BigChris This computer doesn't go into sleep mode, and it was powered on the entire 17 hours. Windows is also configured to not put the NIC into any power saving mode.

– pacoverflow
Jul 22 '14 at 7:05





@BigChris This computer doesn't go into sleep mode, and it was powered on the entire 17 hours. Windows is also configured to not put the NIC into any power saving mode.

– pacoverflow
Jul 22 '14 at 7:05










2 Answers
2






active

oldest

votes


















0














Firstly, if you are trying to figure out which computer is infected with the malware, then you are on the wrong path. You should use special tools for that or monitor your processes, rather then guessing if PC reconnected to the network.



Answering your original question - PC is not supposed to be automatically renewing IP config after it has been released. However if you are using WiFi and you lost connection for a short period of time (which happens now and then) it might do the whole reconnect process which will include release, renew and flushdns.






share|improve this answer
























  • Yes I am running malware scanners on all computers. But I was curious if Windows was supposed to automatically renew the IP or not. This computer is directly connected to the router via ethernet, so I wonder why it reconnected.

    – pacoverflow
    Jul 22 '14 at 7:44



















0














Could be anything, because we can't guarantee there was no interference in the state of the machine between the computer executing your command and you coming back to check if it has an ip.



To answer your question, ipconfig /release does not have an option to change the timer, create a timer or remove the timer. A timer is not even mentioned in the documentation for ipconfig /release



Ipconfig doesn't do much except manipulate your tcp/ip stack and display your tcp/ip configuration. Its meant for troubleshooting and has many useful functions that do exactly and only what they say.






share|improve this answer























    Your Answer








    StackExchange.ready(function() {
    var channelOptions = {
    tags: "".split(" "),
    id: "3"
    };
    initTagRenderer("".split(" "), "".split(" "), channelOptions);

    StackExchange.using("externalEditor", function() {
    // Have to fire editor after snippets, if snippets enabled
    if (StackExchange.settings.snippets.snippetsEnabled) {
    StackExchange.using("snippets", function() {
    createEditor();
    });
    }
    else {
    createEditor();
    }
    });

    function createEditor() {
    StackExchange.prepareEditor({
    heartbeatType: 'answer',
    autoActivateHeartbeat: false,
    convertImagesToLinks: true,
    noModals: true,
    showLowRepImageUploadWarning: true,
    reputationToPostImages: 10,
    bindNavPrevention: true,
    postfix: "",
    imageUploader: {
    brandingHtml: "Powered by u003ca class="icon-imgur-white" href="https://imgur.com/"u003eu003c/au003e",
    contentPolicyHtml: "User contributions licensed under u003ca href="https://creativecommons.org/licenses/by-sa/3.0/"u003ecc by-sa 3.0 with attribution requiredu003c/au003e u003ca href="https://stackoverflow.com/legal/content-policy"u003e(content policy)u003c/au003e",
    allowUrls: true
    },
    onDemand: true,
    discardSelector: ".discard-answer"
    ,immediatelyShowMarkdownHelp:true
    });


    }
    });














    draft saved

    draft discarded


















    StackExchange.ready(
    function () {
    StackExchange.openid.initPostLogin('.new-post-login', 'https%3a%2f%2fsuperuser.com%2fquestions%2f786221%2fwill-windows-renew-ip-address-sometime-after-ipconfig-release%23new-answer', 'question_page');
    }
    );

    Post as a guest















    Required, but never shown

























    2 Answers
    2






    active

    oldest

    votes








    2 Answers
    2






    active

    oldest

    votes









    active

    oldest

    votes






    active

    oldest

    votes









    0














    Firstly, if you are trying to figure out which computer is infected with the malware, then you are on the wrong path. You should use special tools for that or monitor your processes, rather then guessing if PC reconnected to the network.



    Answering your original question - PC is not supposed to be automatically renewing IP config after it has been released. However if you are using WiFi and you lost connection for a short period of time (which happens now and then) it might do the whole reconnect process which will include release, renew and flushdns.






    share|improve this answer
























    • Yes I am running malware scanners on all computers. But I was curious if Windows was supposed to automatically renew the IP or not. This computer is directly connected to the router via ethernet, so I wonder why it reconnected.

      – pacoverflow
      Jul 22 '14 at 7:44
















    0














    Firstly, if you are trying to figure out which computer is infected with the malware, then you are on the wrong path. You should use special tools for that or monitor your processes, rather then guessing if PC reconnected to the network.



    Answering your original question - PC is not supposed to be automatically renewing IP config after it has been released. However if you are using WiFi and you lost connection for a short period of time (which happens now and then) it might do the whole reconnect process which will include release, renew and flushdns.






    share|improve this answer
























    • Yes I am running malware scanners on all computers. But I was curious if Windows was supposed to automatically renew the IP or not. This computer is directly connected to the router via ethernet, so I wonder why it reconnected.

      – pacoverflow
      Jul 22 '14 at 7:44














    0












    0








    0







    Firstly, if you are trying to figure out which computer is infected with the malware, then you are on the wrong path. You should use special tools for that or monitor your processes, rather then guessing if PC reconnected to the network.



    Answering your original question - PC is not supposed to be automatically renewing IP config after it has been released. However if you are using WiFi and you lost connection for a short period of time (which happens now and then) it might do the whole reconnect process which will include release, renew and flushdns.






    share|improve this answer













    Firstly, if you are trying to figure out which computer is infected with the malware, then you are on the wrong path. You should use special tools for that or monitor your processes, rather then guessing if PC reconnected to the network.



    Answering your original question - PC is not supposed to be automatically renewing IP config after it has been released. However if you are using WiFi and you lost connection for a short period of time (which happens now and then) it might do the whole reconnect process which will include release, renew and flushdns.







    share|improve this answer












    share|improve this answer



    share|improve this answer










    answered Jul 22 '14 at 7:35









    Art GertnerArt Gertner

    5,946113563




    5,946113563













    • Yes I am running malware scanners on all computers. But I was curious if Windows was supposed to automatically renew the IP or not. This computer is directly connected to the router via ethernet, so I wonder why it reconnected.

      – pacoverflow
      Jul 22 '14 at 7:44



















    • Yes I am running malware scanners on all computers. But I was curious if Windows was supposed to automatically renew the IP or not. This computer is directly connected to the router via ethernet, so I wonder why it reconnected.

      – pacoverflow
      Jul 22 '14 at 7:44

















    Yes I am running malware scanners on all computers. But I was curious if Windows was supposed to automatically renew the IP or not. This computer is directly connected to the router via ethernet, so I wonder why it reconnected.

    – pacoverflow
    Jul 22 '14 at 7:44





    Yes I am running malware scanners on all computers. But I was curious if Windows was supposed to automatically renew the IP or not. This computer is directly connected to the router via ethernet, so I wonder why it reconnected.

    – pacoverflow
    Jul 22 '14 at 7:44













    0














    Could be anything, because we can't guarantee there was no interference in the state of the machine between the computer executing your command and you coming back to check if it has an ip.



    To answer your question, ipconfig /release does not have an option to change the timer, create a timer or remove the timer. A timer is not even mentioned in the documentation for ipconfig /release



    Ipconfig doesn't do much except manipulate your tcp/ip stack and display your tcp/ip configuration. Its meant for troubleshooting and has many useful functions that do exactly and only what they say.






    share|improve this answer




























      0














      Could be anything, because we can't guarantee there was no interference in the state of the machine between the computer executing your command and you coming back to check if it has an ip.



      To answer your question, ipconfig /release does not have an option to change the timer, create a timer or remove the timer. A timer is not even mentioned in the documentation for ipconfig /release



      Ipconfig doesn't do much except manipulate your tcp/ip stack and display your tcp/ip configuration. Its meant for troubleshooting and has many useful functions that do exactly and only what they say.






      share|improve this answer


























        0












        0








        0







        Could be anything, because we can't guarantee there was no interference in the state of the machine between the computer executing your command and you coming back to check if it has an ip.



        To answer your question, ipconfig /release does not have an option to change the timer, create a timer or remove the timer. A timer is not even mentioned in the documentation for ipconfig /release



        Ipconfig doesn't do much except manipulate your tcp/ip stack and display your tcp/ip configuration. Its meant for troubleshooting and has many useful functions that do exactly and only what they say.






        share|improve this answer













        Could be anything, because we can't guarantee there was no interference in the state of the machine between the computer executing your command and you coming back to check if it has an ip.



        To answer your question, ipconfig /release does not have an option to change the timer, create a timer or remove the timer. A timer is not even mentioned in the documentation for ipconfig /release



        Ipconfig doesn't do much except manipulate your tcp/ip stack and display your tcp/ip configuration. Its meant for troubleshooting and has many useful functions that do exactly and only what they say.







        share|improve this answer












        share|improve this answer



        share|improve this answer










        answered Jan 31 at 19:41









        Caine KiewitCaine Kiewit

        726




        726






























            draft saved

            draft discarded




















































            Thanks for contributing an answer to Super User!


            • Please be sure to answer the question. Provide details and share your research!

            But avoid



            • Asking for help, clarification, or responding to other answers.

            • Making statements based on opinion; back them up with references or personal experience.


            To learn more, see our tips on writing great answers.




            draft saved


            draft discarded














            StackExchange.ready(
            function () {
            StackExchange.openid.initPostLogin('.new-post-login', 'https%3a%2f%2fsuperuser.com%2fquestions%2f786221%2fwill-windows-renew-ip-address-sometime-after-ipconfig-release%23new-answer', 'question_page');
            }
            );

            Post as a guest















            Required, but never shown





















































            Required, but never shown














            Required, but never shown












            Required, but never shown







            Required, but never shown

































            Required, but never shown














            Required, but never shown












            Required, but never shown







            Required, but never shown







            Popular posts from this blog

            flock() on closed filehandle LOCK_FILE at /usr/bin/apt-mirror

            Mangá

            Eduardo VII do Reino Unido