NETGEAR is aware of a growing number of phone and online scams. To learn how to stay safe click here.
Forum Discussion
Solved
I cant port forward no matter what I do.
I've try to port forward using this router before and it work brilliantly. Today, when I try to port forward, it doesnt work. I've try to fix it by: -Factory reset the router. (button and through ...
I've found the solution. For me, my main PC does not connect my port to my public IP, therefore I use my old windows 7 laptop as a internal IP and the server. I port forward the server and went on canyouseeme.org and it see the port. The problem is, probably, somewhere in my main PC, there is a Windows problem that doesn't allow the public IP to work. It probably can be fix with a new installation of Windows. Therefore, I use my laptop now to run the server and it work fine.
> [...] I then go into cmd and type ipconfig and use the IPv4 that is
> assign to my pc. [...]
That's the "192.168.1.10"?
> [...] I haven't try to set a static IP yet, I do not think thats that
> the issue. [...]
Terminology: a static IP address is configured on the actual device
(your "my pc"); a reserved dynamic IP address can be configured on (the
DHCP server of) your router. You really will want to use one of those
methods to fix the LAN IP address of your server system.
> [...] Today my new IPv4 is 192.168.1.12
Every time it changes, your port-forwarding rules (which contain that
address) become useless.
> [...] I ran the server file and try to join the server using my public
> IP and it couldn't connect. [...]
I don't know what "run the server file" means, but let's worry about
that later.
[...] my IP address for my internet port is the same address as my
> public IP. I assume "a.b" is 47.205
Sounds right (for Frontier?).
Can you connect to the server from a system on your LAN using the
server's LAN IP address? If not, then all the port forwarding in the
world won't help.
Can you connect to the server from a system on your LAN using the
router's WAN/Internet IP address? Assuming that the "NAT loopback"
feature of your router is working, that test would verify the
port-forwarding rules (which look plausible to me).
> For number 1. [...]
That seems to be ok. You don't seem to have it, but for more
details:
https://en.wikipedia.org/wiki/Carrier-grade_NAT
> For number 2. [...]
A "wandering target" is a server whose LAN IP address keeps changing.
Like yours ("192.168.1.10", "192.168.1.12", ...), until you get it
fixed (in the sense of "not changing").
> For number 3. [...]
If you're not running a server program which listens at port 25565
(or whatever), then you won't be able to connect to that server at that
port number.
> For number 4. [...]
Try the two "Can you connect" tests above. If they work, but someone
in the outside world can't connect, then you can worry about that.
>Sounds right (for Frontier?).
Yes, I currently have frontier.
> Can you connect to the server from a system on your LAN using the
server's LAN IP address? If not, then all the port forwarding in the
world won't help.
Sorry, Im new to all the terminology in term of port forwarding and releated materials. I assume you're saying that can I connect to 192.168.1.12 which is my server IP and what I try to port forward to. Yes, I can connect to 192.168.1.12.
> Can you connect to the server from a system on your LAN using the
router's WAN/Internet IP address? Assuming that the "NAT loopback"
feature of your router is working, that test would verify the
port-forwarding rules (which look plausible to me).
I think this is where my issue lies. I try to connect to the server using the Internet IP address/WAN but I wasn't able to connect. I do not know what is "NAT loopback" is and I do not know if thats the issue. Is there a way to check the NAT loopback? and disable it.
> A "wandering target" is a server whose LAN IP address keeps changing.
Like yours ("192.168.1.10", "192.168.1.12", ...), until you get it
fixed (in the sense of "not changing").
Is a wandering IP a problem if I updating it in the server and inside my port forwarding section in the router?
> If you're not running a server program which listens at port 25565
(or whatever), then you won't be able to connect to that server at that
port number.
Earlier, you said " I don't know what "run the server file" means". Well the server file in my case is something that listens at port 25565.
>Try the two "Can you connect" tests above. If they work, but someone
I've found the solution. For me, my main PC does not connect my port to my public IP, therefore I use my old windows 7 laptop as a internal IP and the server. I port forward the server and went on canyouseeme.org and it see the port. The problem is, probably, somewhere in my main PC, there is a Windows problem that doesn't allow the public IP to work. It probably can be fix with a new installation of Windows. Therefore, I use my laptop now to run the server and it work fine.