Forum Replies Created
-
AuthorPosts
-
October 20, 2020 at 07:51 in reply to: Router on double-NAT – Can’t get external IP for remote connections #29987goborghParticipant
At home I have the exact same router and I can see the external IP address. At my office, like I explained, I’m being provided access through the building and the IP address I get is the one from the building’s IP, not the one from outside.
In short, with the same router on both location, one is available to access from an outside location and the other doesn’t.
October 19, 2020 at 08:26 in reply to: Router on double-NAT – Can’t get external IP for remote connections #29969goborghParticipantIn any case, doing that doesn’t make NoMachine see the external IP address, perhaps the issue is not with the router itself but with NoMachine.
October 2, 2020 at 07:29 in reply to: Router on double-NAT – Can’t get external IP for remote connections #29756goborghParticipantHi Kroy,
Unfortunately those instructions don’t take into consideration the double router situation.
Airport Extreme doesn’t allow me to put an external IP in the port mapping, it just restricts me to the 10.0.1.x, where x is the only option I have available to change.
Perhaps a change in recent firmware, I heard dydns stopped supporting the newer firmwares.
October 1, 2020 at 07:33 in reply to: Router on double-NAT – Can’t get external IP for remote connections #29742goborghParticipantThe router actually supports Upnp, they just call it “Enable NAT Port Mapping Protocol”, or so I’ve heard.
When I try to setup port mapping, I’m limited by “10.0.1.xxx” address, it doesn’t let me edit the whole address unfortunately.
Also, the issue is that I’m behind a second router, the building one.
Still I still believe this router is not good for this kind of things, it’s very limiting on what you can do, what router would you recommend?
-
AuthorPosts