Router Config IP Rejected












0















I'm currently using a D-Link DIR-601 router, and up until now, I have had very few problems with it. I've connected to the router control panel before using the IP 192.168.0.1. However, sometimes I would first have to restart my router for it to let me connect. After some research, I determined that it was a IP clash between my router and my modem, so I changed my router's IP to 192.168.0.4, which seemed to fix the problem. However, a couple months later, I tried connecting to 192.168.0.4, but my connection keeps getting rejected. In Opera, I get this error message:
"Opera's connection attempt to 192.168.0.4 was rejected. The website may be down, or your network may not be properly configured."
In IE, I just get a "This page can’t be displayed" error. I'd really appreciate any assistance.










share|improve this question























  • What model is your modem? Is it also a router?

    – David Schwartz
    Jan 22 '14 at 21:56











  • I'm not sure what my modem is. I am using a router that runs into a data outlet for my university.

    – Trey Stone
    Jan 23 '14 at 1:41











  • What the router's WAN IP? Is it a private IP or a public one?

    – David Schwartz
    Jan 23 '14 at 7:34
















0















I'm currently using a D-Link DIR-601 router, and up until now, I have had very few problems with it. I've connected to the router control panel before using the IP 192.168.0.1. However, sometimes I would first have to restart my router for it to let me connect. After some research, I determined that it was a IP clash between my router and my modem, so I changed my router's IP to 192.168.0.4, which seemed to fix the problem. However, a couple months later, I tried connecting to 192.168.0.4, but my connection keeps getting rejected. In Opera, I get this error message:
"Opera's connection attempt to 192.168.0.4 was rejected. The website may be down, or your network may not be properly configured."
In IE, I just get a "This page can’t be displayed" error. I'd really appreciate any assistance.










share|improve this question























  • What model is your modem? Is it also a router?

    – David Schwartz
    Jan 22 '14 at 21:56











  • I'm not sure what my modem is. I am using a router that runs into a data outlet for my university.

    – Trey Stone
    Jan 23 '14 at 1:41











  • What the router's WAN IP? Is it a private IP or a public one?

    – David Schwartz
    Jan 23 '14 at 7:34














0












0








0








I'm currently using a D-Link DIR-601 router, and up until now, I have had very few problems with it. I've connected to the router control panel before using the IP 192.168.0.1. However, sometimes I would first have to restart my router for it to let me connect. After some research, I determined that it was a IP clash between my router and my modem, so I changed my router's IP to 192.168.0.4, which seemed to fix the problem. However, a couple months later, I tried connecting to 192.168.0.4, but my connection keeps getting rejected. In Opera, I get this error message:
"Opera's connection attempt to 192.168.0.4 was rejected. The website may be down, or your network may not be properly configured."
In IE, I just get a "This page can’t be displayed" error. I'd really appreciate any assistance.










share|improve this question














I'm currently using a D-Link DIR-601 router, and up until now, I have had very few problems with it. I've connected to the router control panel before using the IP 192.168.0.1. However, sometimes I would first have to restart my router for it to let me connect. After some research, I determined that it was a IP clash between my router and my modem, so I changed my router's IP to 192.168.0.4, which seemed to fix the problem. However, a couple months later, I tried connecting to 192.168.0.4, but my connection keeps getting rejected. In Opera, I get this error message:
"Opera's connection attempt to 192.168.0.4 was rejected. The website may be down, or your network may not be properly configured."
In IE, I just get a "This page can’t be displayed" error. I'd really appreciate any assistance.







networking wireless-networking router wireless-router wifi-configuration






share|improve this question













share|improve this question











share|improve this question




share|improve this question










asked Jan 22 '14 at 21:52









Trey StoneTrey Stone

612




612













  • What model is your modem? Is it also a router?

    – David Schwartz
    Jan 22 '14 at 21:56











  • I'm not sure what my modem is. I am using a router that runs into a data outlet for my university.

    – Trey Stone
    Jan 23 '14 at 1:41











  • What the router's WAN IP? Is it a private IP or a public one?

    – David Schwartz
    Jan 23 '14 at 7:34



















  • What model is your modem? Is it also a router?

    – David Schwartz
    Jan 22 '14 at 21:56











  • I'm not sure what my modem is. I am using a router that runs into a data outlet for my university.

    – Trey Stone
    Jan 23 '14 at 1:41











  • What the router's WAN IP? Is it a private IP or a public one?

    – David Schwartz
    Jan 23 '14 at 7:34

















What model is your modem? Is it also a router?

– David Schwartz
Jan 22 '14 at 21:56





What model is your modem? Is it also a router?

– David Schwartz
Jan 22 '14 at 21:56













I'm not sure what my modem is. I am using a router that runs into a data outlet for my university.

– Trey Stone
Jan 23 '14 at 1:41





I'm not sure what my modem is. I am using a router that runs into a data outlet for my university.

– Trey Stone
Jan 23 '14 at 1:41













What the router's WAN IP? Is it a private IP or a public one?

– David Schwartz
Jan 23 '14 at 7:34





What the router's WAN IP? Is it a private IP or a public one?

– David Schwartz
Jan 23 '14 at 7:34










2 Answers
2






active

oldest

votes


















0














I've dealt with a similar issue just yesterday and I think I know what is going on here...



It sounds like a mixture of a routing conflict between WAN and LAN along with security policies being applied.



If you have 192.168.0.1 as your modem and 192.168.0.4 on your router, you are effectively telling your router that the 192.168.0.0/24 network exists on both WAN and LAN... If on top of this, your router has a security policy that tells it to block access to the GUI on the WAN IP range, it will then block you from connecting.



I highly recommend you change your modem to 192.168.1.1 and set your router's WAN port to 192.168.1.2, then you can continue to use 192.168.0.0/24 on your LAN.



Alternatively, do it the other way round and set your LAN's ip range to something different, but you will need to change settings on anything statically assigned.



As for why you connected before, it is possible that the firewall policy to block accessing the GUI is hard coded to the WAN ip range, but, this only applies when the interface is up... try unplugging the modem and then seeing if you can connect... I can't guarantee this will work, but it may.



Hope this helps and also makes sense.






share|improve this answer
























  • After rebooting the router a couple more times, it finally let me into the control panel. I was able to change the IP of the router to 192.168.1.2. I then became unable to connect to the internet for some time. However, after coming back from classes, it had somehow fixed itself and allowed me onto the internet with the router IP of 192.168.1.2. Unfortunately, after prolonged use of the router (6+ hours?), I get locked out of the control panel again and have to reboot repeatedly to get back in. So the problem has been downgraded to an annoyance, but any suggestions would still be appreciated.

    – Trey Stone
    Jan 24 '14 at 5:18











  • I am guessing after changing the router's IP, you didn't change the ip on your computers... Make sure they have a new DHCP lease with the gateway of 192.168.2.1 and an ip of 192.168.2.x - if you were able to get on at all, I guess you do have that... As for loosing control over the router, I think you need a new one - it just sounds bad/bugged now...

    – William Hilsum
    Jan 25 '14 at 10:21











  • I would never use a 192.168.0.x, 192.168.1.x, 192.168.168.x for a router, those subnets are too common and the default in many devices. I would recommend setting the router to something like 192.168.47.1, 192.168.183.1, or just about anything else, it just reduces potential issues.

    – acejavelin
    Apr 9 '16 at 13:42



















0














For your problem getting locked out, it sounds like a firmware issue. Here is the link to the page to download firmware. Only thing you need to go find out on your router, is which hardware revision it is, which should should be located on the bottom of it, or where ever it has model number.



Once you download the most up to date firmware, its a matter of going to your routers control panel, find the area to upload the firmware, usually its in the administration area. Then update the firmware.



D-Link DIR-601 Firmware






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%2f705576%2frouter-config-ip-rejected%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














    I've dealt with a similar issue just yesterday and I think I know what is going on here...



    It sounds like a mixture of a routing conflict between WAN and LAN along with security policies being applied.



    If you have 192.168.0.1 as your modem and 192.168.0.4 on your router, you are effectively telling your router that the 192.168.0.0/24 network exists on both WAN and LAN... If on top of this, your router has a security policy that tells it to block access to the GUI on the WAN IP range, it will then block you from connecting.



    I highly recommend you change your modem to 192.168.1.1 and set your router's WAN port to 192.168.1.2, then you can continue to use 192.168.0.0/24 on your LAN.



    Alternatively, do it the other way round and set your LAN's ip range to something different, but you will need to change settings on anything statically assigned.



    As for why you connected before, it is possible that the firewall policy to block accessing the GUI is hard coded to the WAN ip range, but, this only applies when the interface is up... try unplugging the modem and then seeing if you can connect... I can't guarantee this will work, but it may.



    Hope this helps and also makes sense.






    share|improve this answer
























    • After rebooting the router a couple more times, it finally let me into the control panel. I was able to change the IP of the router to 192.168.1.2. I then became unable to connect to the internet for some time. However, after coming back from classes, it had somehow fixed itself and allowed me onto the internet with the router IP of 192.168.1.2. Unfortunately, after prolonged use of the router (6+ hours?), I get locked out of the control panel again and have to reboot repeatedly to get back in. So the problem has been downgraded to an annoyance, but any suggestions would still be appreciated.

      – Trey Stone
      Jan 24 '14 at 5:18











    • I am guessing after changing the router's IP, you didn't change the ip on your computers... Make sure they have a new DHCP lease with the gateway of 192.168.2.1 and an ip of 192.168.2.x - if you were able to get on at all, I guess you do have that... As for loosing control over the router, I think you need a new one - it just sounds bad/bugged now...

      – William Hilsum
      Jan 25 '14 at 10:21











    • I would never use a 192.168.0.x, 192.168.1.x, 192.168.168.x for a router, those subnets are too common and the default in many devices. I would recommend setting the router to something like 192.168.47.1, 192.168.183.1, or just about anything else, it just reduces potential issues.

      – acejavelin
      Apr 9 '16 at 13:42
















    0














    I've dealt with a similar issue just yesterday and I think I know what is going on here...



    It sounds like a mixture of a routing conflict between WAN and LAN along with security policies being applied.



    If you have 192.168.0.1 as your modem and 192.168.0.4 on your router, you are effectively telling your router that the 192.168.0.0/24 network exists on both WAN and LAN... If on top of this, your router has a security policy that tells it to block access to the GUI on the WAN IP range, it will then block you from connecting.



    I highly recommend you change your modem to 192.168.1.1 and set your router's WAN port to 192.168.1.2, then you can continue to use 192.168.0.0/24 on your LAN.



    Alternatively, do it the other way round and set your LAN's ip range to something different, but you will need to change settings on anything statically assigned.



    As for why you connected before, it is possible that the firewall policy to block accessing the GUI is hard coded to the WAN ip range, but, this only applies when the interface is up... try unplugging the modem and then seeing if you can connect... I can't guarantee this will work, but it may.



    Hope this helps and also makes sense.






    share|improve this answer
























    • After rebooting the router a couple more times, it finally let me into the control panel. I was able to change the IP of the router to 192.168.1.2. I then became unable to connect to the internet for some time. However, after coming back from classes, it had somehow fixed itself and allowed me onto the internet with the router IP of 192.168.1.2. Unfortunately, after prolonged use of the router (6+ hours?), I get locked out of the control panel again and have to reboot repeatedly to get back in. So the problem has been downgraded to an annoyance, but any suggestions would still be appreciated.

      – Trey Stone
      Jan 24 '14 at 5:18











    • I am guessing after changing the router's IP, you didn't change the ip on your computers... Make sure they have a new DHCP lease with the gateway of 192.168.2.1 and an ip of 192.168.2.x - if you were able to get on at all, I guess you do have that... As for loosing control over the router, I think you need a new one - it just sounds bad/bugged now...

      – William Hilsum
      Jan 25 '14 at 10:21











    • I would never use a 192.168.0.x, 192.168.1.x, 192.168.168.x for a router, those subnets are too common and the default in many devices. I would recommend setting the router to something like 192.168.47.1, 192.168.183.1, or just about anything else, it just reduces potential issues.

      – acejavelin
      Apr 9 '16 at 13:42














    0












    0








    0







    I've dealt with a similar issue just yesterday and I think I know what is going on here...



    It sounds like a mixture of a routing conflict between WAN and LAN along with security policies being applied.



    If you have 192.168.0.1 as your modem and 192.168.0.4 on your router, you are effectively telling your router that the 192.168.0.0/24 network exists on both WAN and LAN... If on top of this, your router has a security policy that tells it to block access to the GUI on the WAN IP range, it will then block you from connecting.



    I highly recommend you change your modem to 192.168.1.1 and set your router's WAN port to 192.168.1.2, then you can continue to use 192.168.0.0/24 on your LAN.



    Alternatively, do it the other way round and set your LAN's ip range to something different, but you will need to change settings on anything statically assigned.



    As for why you connected before, it is possible that the firewall policy to block accessing the GUI is hard coded to the WAN ip range, but, this only applies when the interface is up... try unplugging the modem and then seeing if you can connect... I can't guarantee this will work, but it may.



    Hope this helps and also makes sense.






    share|improve this answer













    I've dealt with a similar issue just yesterday and I think I know what is going on here...



    It sounds like a mixture of a routing conflict between WAN and LAN along with security policies being applied.



    If you have 192.168.0.1 as your modem and 192.168.0.4 on your router, you are effectively telling your router that the 192.168.0.0/24 network exists on both WAN and LAN... If on top of this, your router has a security policy that tells it to block access to the GUI on the WAN IP range, it will then block you from connecting.



    I highly recommend you change your modem to 192.168.1.1 and set your router's WAN port to 192.168.1.2, then you can continue to use 192.168.0.0/24 on your LAN.



    Alternatively, do it the other way round and set your LAN's ip range to something different, but you will need to change settings on anything statically assigned.



    As for why you connected before, it is possible that the firewall policy to block accessing the GUI is hard coded to the WAN ip range, but, this only applies when the interface is up... try unplugging the modem and then seeing if you can connect... I can't guarantee this will work, but it may.



    Hope this helps and also makes sense.







    share|improve this answer












    share|improve this answer



    share|improve this answer










    answered Jan 22 '14 at 22:10









    William HilsumWilliam Hilsum

    108k16160253




    108k16160253













    • After rebooting the router a couple more times, it finally let me into the control panel. I was able to change the IP of the router to 192.168.1.2. I then became unable to connect to the internet for some time. However, after coming back from classes, it had somehow fixed itself and allowed me onto the internet with the router IP of 192.168.1.2. Unfortunately, after prolonged use of the router (6+ hours?), I get locked out of the control panel again and have to reboot repeatedly to get back in. So the problem has been downgraded to an annoyance, but any suggestions would still be appreciated.

      – Trey Stone
      Jan 24 '14 at 5:18











    • I am guessing after changing the router's IP, you didn't change the ip on your computers... Make sure they have a new DHCP lease with the gateway of 192.168.2.1 and an ip of 192.168.2.x - if you were able to get on at all, I guess you do have that... As for loosing control over the router, I think you need a new one - it just sounds bad/bugged now...

      – William Hilsum
      Jan 25 '14 at 10:21











    • I would never use a 192.168.0.x, 192.168.1.x, 192.168.168.x for a router, those subnets are too common and the default in many devices. I would recommend setting the router to something like 192.168.47.1, 192.168.183.1, or just about anything else, it just reduces potential issues.

      – acejavelin
      Apr 9 '16 at 13:42



















    • After rebooting the router a couple more times, it finally let me into the control panel. I was able to change the IP of the router to 192.168.1.2. I then became unable to connect to the internet for some time. However, after coming back from classes, it had somehow fixed itself and allowed me onto the internet with the router IP of 192.168.1.2. Unfortunately, after prolonged use of the router (6+ hours?), I get locked out of the control panel again and have to reboot repeatedly to get back in. So the problem has been downgraded to an annoyance, but any suggestions would still be appreciated.

      – Trey Stone
      Jan 24 '14 at 5:18











    • I am guessing after changing the router's IP, you didn't change the ip on your computers... Make sure they have a new DHCP lease with the gateway of 192.168.2.1 and an ip of 192.168.2.x - if you were able to get on at all, I guess you do have that... As for loosing control over the router, I think you need a new one - it just sounds bad/bugged now...

      – William Hilsum
      Jan 25 '14 at 10:21











    • I would never use a 192.168.0.x, 192.168.1.x, 192.168.168.x for a router, those subnets are too common and the default in many devices. I would recommend setting the router to something like 192.168.47.1, 192.168.183.1, or just about anything else, it just reduces potential issues.

      – acejavelin
      Apr 9 '16 at 13:42

















    After rebooting the router a couple more times, it finally let me into the control panel. I was able to change the IP of the router to 192.168.1.2. I then became unable to connect to the internet for some time. However, after coming back from classes, it had somehow fixed itself and allowed me onto the internet with the router IP of 192.168.1.2. Unfortunately, after prolonged use of the router (6+ hours?), I get locked out of the control panel again and have to reboot repeatedly to get back in. So the problem has been downgraded to an annoyance, but any suggestions would still be appreciated.

    – Trey Stone
    Jan 24 '14 at 5:18





    After rebooting the router a couple more times, it finally let me into the control panel. I was able to change the IP of the router to 192.168.1.2. I then became unable to connect to the internet for some time. However, after coming back from classes, it had somehow fixed itself and allowed me onto the internet with the router IP of 192.168.1.2. Unfortunately, after prolonged use of the router (6+ hours?), I get locked out of the control panel again and have to reboot repeatedly to get back in. So the problem has been downgraded to an annoyance, but any suggestions would still be appreciated.

    – Trey Stone
    Jan 24 '14 at 5:18













    I am guessing after changing the router's IP, you didn't change the ip on your computers... Make sure they have a new DHCP lease with the gateway of 192.168.2.1 and an ip of 192.168.2.x - if you were able to get on at all, I guess you do have that... As for loosing control over the router, I think you need a new one - it just sounds bad/bugged now...

    – William Hilsum
    Jan 25 '14 at 10:21





    I am guessing after changing the router's IP, you didn't change the ip on your computers... Make sure they have a new DHCP lease with the gateway of 192.168.2.1 and an ip of 192.168.2.x - if you were able to get on at all, I guess you do have that... As for loosing control over the router, I think you need a new one - it just sounds bad/bugged now...

    – William Hilsum
    Jan 25 '14 at 10:21













    I would never use a 192.168.0.x, 192.168.1.x, 192.168.168.x for a router, those subnets are too common and the default in many devices. I would recommend setting the router to something like 192.168.47.1, 192.168.183.1, or just about anything else, it just reduces potential issues.

    – acejavelin
    Apr 9 '16 at 13:42





    I would never use a 192.168.0.x, 192.168.1.x, 192.168.168.x for a router, those subnets are too common and the default in many devices. I would recommend setting the router to something like 192.168.47.1, 192.168.183.1, or just about anything else, it just reduces potential issues.

    – acejavelin
    Apr 9 '16 at 13:42













    0














    For your problem getting locked out, it sounds like a firmware issue. Here is the link to the page to download firmware. Only thing you need to go find out on your router, is which hardware revision it is, which should should be located on the bottom of it, or where ever it has model number.



    Once you download the most up to date firmware, its a matter of going to your routers control panel, find the area to upload the firmware, usually its in the administration area. Then update the firmware.



    D-Link DIR-601 Firmware






    share|improve this answer




























      0














      For your problem getting locked out, it sounds like a firmware issue. Here is the link to the page to download firmware. Only thing you need to go find out on your router, is which hardware revision it is, which should should be located on the bottom of it, or where ever it has model number.



      Once you download the most up to date firmware, its a matter of going to your routers control panel, find the area to upload the firmware, usually its in the administration area. Then update the firmware.



      D-Link DIR-601 Firmware






      share|improve this answer


























        0












        0








        0







        For your problem getting locked out, it sounds like a firmware issue. Here is the link to the page to download firmware. Only thing you need to go find out on your router, is which hardware revision it is, which should should be located on the bottom of it, or where ever it has model number.



        Once you download the most up to date firmware, its a matter of going to your routers control panel, find the area to upload the firmware, usually its in the administration area. Then update the firmware.



        D-Link DIR-601 Firmware






        share|improve this answer













        For your problem getting locked out, it sounds like a firmware issue. Here is the link to the page to download firmware. Only thing you need to go find out on your router, is which hardware revision it is, which should should be located on the bottom of it, or where ever it has model number.



        Once you download the most up to date firmware, its a matter of going to your routers control panel, find the area to upload the firmware, usually its in the administration area. Then update the firmware.



        D-Link DIR-601 Firmware







        share|improve this answer












        share|improve this answer



        share|improve this answer










        answered Aug 12 '16 at 14:45









        FrostalfFrostalf

        40937




        40937






























            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%2f705576%2frouter-config-ip-rejected%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

            Aardman Animations

            Are they similar matrix

            “minimization” problem in Euclidean space related to orthonormal basis