NETGEAR is aware of a growing number of phone and online scams. To learn how to stay safe click here.
Forum Discussion
Solved
R6200v2 Unable to open ports
I recently moved into a new apartment and have been trying to set up my a port on my network to run a server, but it is not opening. I have already allowed the port through my firewall and even t...
> Could you explain how I find the address? [...]
Which "the address"? Every network interface has one (and your
router has two, which you seem to have found).> My Internet IP address is being obtained dynamically from the ISP and
> my Internet Port IP address is 192.168.1.64. The Router Information IP
> address is 10.0.0.1.And there it is. "192.168.1.64" is a private address, assigned to
your NAT router by some other NAT router, hence "double NAT". Any
effective port forwarding would need to be done on the other router
(which, presumably, but not certainly) has a public address on its far
side.The R6200v2 would normally use "192.168.1.*" on its LAN side, but it
detected that subnet on its WAN/Internet side, and thus switched to
using its alternate LAN subnet, "10.0.0.*" to avoid the conflict.> Not sure if any of that is helpful or not.
It's everything which is needed to reveal that you're approximately
doomed.The only solutions I know are: 1) to ask your ISP for a real public
address (which I'd guess might not be possible with the current
apartment service scheme), or 2) to use a tunneling service like the one
mentioned in another recent thread (near the end):
> I recently moved into a new apartment [...]
From what/whom do you get your Internet connection?
What's the IP address of the WAN/Internet interface on your R6200v2?
Is it a public address?
The usual problems with this stuff are:
1. Wrong external IP address (different from the port-forwarding
router's WAN/Internet IP address). (An intermediate NAT router, for
example, could cause this. Or an ISP using carrier-grade NAT to
conserve IPv4 addresses.)
2. Bad port-forwarding rule (wrong port(s), wrong target address --
including a wandering target).
3. Server not listening on the port-forwarding target system.
4. External influences: ISP blocking, other firewalls, ...
You seem to be dealing with 2-4, but if your apartment building
provides your connection, then my money would be on "1".
I receive my connection from AT&T's fibre service. They partner with the complex I am in, but are considered seperate, both in costs and service provided.
Could you explain how I find the address? The WAN setup has the default DMZ Server box checked which is the same as my IP as my local PC. My Internet IP address is being obtained dynamically from the ISP and my Internet Port IP address is 192.168.1.64. The Router Information IP address is 10.0.0.1.
The address from my PC is 10.0.0.2.
Not sure if any of that is helpful or not.
> Could you explain how I find the address? [...]
Which "the address"? Every network interface has one (and your
router has two, which you seem to have found).> My Internet IP address is being obtained dynamically from the ISP and
> my Internet Port IP address is 192.168.1.64. The Router Information IP
> address is 10.0.0.1.And there it is. "192.168.1.64" is a private address, assigned to
your NAT router by some other NAT router, hence "double NAT". Any
effective port forwarding would need to be done on the other router
(which, presumably, but not certainly) has a public address on its far
side.The R6200v2 would normally use "192.168.1.*" on its LAN side, but it
detected that subnet on its WAN/Internet side, and thus switched to
using its alternate LAN subnet, "10.0.0.*" to avoid the conflict.> Not sure if any of that is helpful or not.
It's everything which is needed to reveal that you're approximately
doomed.The only solutions I know are: 1) to ask your ISP for a real public
address (which I'd guess might not be possible with the current
apartment service scheme), or 2) to use a tunneling service like the one
mentioned in another recent thread (near the end):