- Apr 21, 2016
- 2
- 0
- 1,510
I have a TP-Link TD-8616 modem, and an Asus RT-AC52U router. When I connect my computer directly to the modem I can see the modem setup and status web pages no problem. Connect the router and I can no longer see the modem web pages. I see lots of other people asking about this, but no answers that work.
At first I thought the problem is that the modem address is 192.168.1.1 which is a private network, hence the router would not pass that address to the outside world, which would mean the router never sees the requests for its web pages. So I changed the router address to 9.9.9.9 (This is not a random choice. Network 9 is owned by IBM but is inside their firewall so since I am outside their firewall there is no chance I will ever need to access that address, hence no conflicts.) Since network 9 it is not a private network, I was expecting the router to pass it to the outside word, and then the modem would see it and respond. Nope!
I am in the category of having a little knowledge. In this case a little knowledge seems to be useless, rather than dangerous. According to tracert it goes right past the modem to the outside world, and of course doesn't work. I also notice that a tracert to any sites that do work also go right past the modem, and does not show the modem as a host on the way. I am pretty sure that points to my problem, but I don't know how to fix it. Suggestions?
It really puzzles me that modem responds when not using a router, but doesn't respond when the router is in between. How does the modem even know what is on the other end of the ethernet cable?
I see some people suggest adding static routes in the router. I tried a few of them, more of less shots in the dark, needless to say that did not help.
I couldn't get it to work with my previous routers either. I would really appreciate any suggestions. Thanks, Alex.
At first I thought the problem is that the modem address is 192.168.1.1 which is a private network, hence the router would not pass that address to the outside world, which would mean the router never sees the requests for its web pages. So I changed the router address to 9.9.9.9 (This is not a random choice. Network 9 is owned by IBM but is inside their firewall so since I am outside their firewall there is no chance I will ever need to access that address, hence no conflicts.) Since network 9 it is not a private network, I was expecting the router to pass it to the outside word, and then the modem would see it and respond. Nope!
I am in the category of having a little knowledge. In this case a little knowledge seems to be useless, rather than dangerous. According to tracert it goes right past the modem to the outside world, and of course doesn't work. I also notice that a tracert to any sites that do work also go right past the modem, and does not show the modem as a host on the way. I am pretty sure that points to my problem, but I don't know how to fix it. Suggestions?
It really puzzles me that modem responds when not using a router, but doesn't respond when the router is in between. How does the modem even know what is on the other end of the ethernet cable?
I see some people suggest adding static routes in the router. I tried a few of them, more of less shots in the dark, needless to say that did not help.
I couldn't get it to work with my previous routers either. I would really appreciate any suggestions. Thanks, Alex.
Facebook
Twitter
Instagram