Skip to main content

You are not logged in. Your edit will be placed in a queue until it is peer reviewed.

We welcome edits that make the post easier to understand and more valuable for readers. Because community members review edits, please try to make the post substantially better than how you found it, for example, by fixing grammar or adding additional resources and hyperlinks.

3
  • Upvoted, since I had a feeling it had to do with my ISP and you explained why. What about the second part of the question. i.e. with my second ISP via portable router. I had done port forwarding on that in the past while on Windows 7. However, unlike the first router, where typing 172.16.X.X:5555 would forward and open a test webpage, the same does not happen on the second. Commented Mar 6, 2018 at 19:06
  • @ShahidThaika Most likely your ISP issued public IPs at that time, and does not do that now (this is becoming a more common practice due to constraints on IPv4 addresses worldwide). It could also be that your second ISP did not have client isolation in their network, so for example a router with 172.16.12.75 could talk to 172.16.111.94 without issues within their network and they now don't allow that. Without knowing more about the conditions at that time it is hard to say for certain.
    – acejavelin
    Commented Mar 6, 2018 at 19:12
  • @ShahidThaika Also, because it is not clear at what point in the network you are trying to open the webpage from (inside or outside the local LAN), this could relate to either how the ISP or your router handles a "loopback" to itself if you were testing from inside your LAN. Some will redirect back to you, and others will reject these packets, this could be the router or the ISP.
    – acejavelin
    Commented Mar 6, 2018 at 19:18