Timeline for Unable to port forward properly
Current License: CC BY-SA 3.0
5 events
| when toggle format | what | by | license | comment | |
|---|---|---|---|---|---|
| Mar 6, 2018 at 19:49 | vote | accept | Shahid Thaika | ||
| Mar 6, 2018 at 19:18 | comment | added | acejavelin | @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. | |
| Mar 6, 2018 at 19:12 | comment | added | acejavelin | @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. | |
| Mar 6, 2018 at 19:06 | comment | added | Shahid Thaika | 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. | |
| Mar 6, 2018 at 18:49 | history | answered | acejavelin | CC BY-SA 3.0 |