This topic has been marked solved and closed to new posts due to inactivity. We hope you'll join the conversation by posting to an open topic or starting a new one.
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 web browser)
-change the public IP with the ISP.
-Triple check that I put in the correct information.
-Disable UPnP.
-Downgrade the router, still the same problem, I upgrade it back afterward.
-Disable firewall in my computer.
I currently use the Netgear R7000P, firmware V1.3.1.64_10.1.36. My PC is running Windows 10. I do not know if there is something wrong or this is a firmware problem.
Please, I'am very desperate for some help. Anyone out there please help me out.
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.
Think, for a moment, how little useful information that non-description conveys to the non-psychics in your audience.
"can't" is not a useful problem description. It does not say what you did. It does not say what happened when you did it. As usual, showing actual actions (commands) with their actual results (error messages, LED indicators, ...) can be more helpful than vague descriptions or interpretations.
> I've try to port forward using this router before [...]
Why were you using port forwarding?
> Today, when I try to port forward, it doesnt work. [...]
Why are you trying to use port forwarding? Regarding "doesn[']t work", see "not a useful problem description [...]", above.
What are your actual port-forwarding rules? Copy+paste is your friend.
> -change the public IP with the ISP.
What is the router's WAN/Internet IP address? Is that your public IP address? ("a.b" of "a.b.c.d" would be enough of your public IP address to satisfy my curiosity.)
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, ...
Now that I've noticed the attached picture, ...
What's at "192.168.1.10"? Is that a reserved address for some device (server)?
>"can't" is not a useful problem description. It does not say what you did. It does not say what happened when you did it. As usual, showing actual actions (commands) with their actual results (error messages, LED indicators, ...) can be more helpful than vague descriptions or interpretations.
What I did is, Im trying to port forward to a port to host a Minecraft/ video games server. I went into the router, go into the advanced tab and port forwarding/ port triggering. I then add a custom service, port 25565 as the same internal and external port. I then go into cmd and type ipconfig and use the IPv4 that is assign to my pc. I haven't try to set a static IP yet, I do not think thats that the issue. After, I ran the server file and try to join the server using my public IP and it couldn't connect. I try canyouseeme.org and it said the port is close.
>Why were you using port forwarding?
To host a server to play Minecraft with my friends.
>What are your actual port-forwarding rules? Copy+paste is your friend.
I assume you're talking about the port forward menu. If this is not correct, can you please explain further about port forwarding rules.
Service Name Protocol TCP/UDPTCPUDP External Port Range (1~65534) (Use commas to separate ports and/or port ranges. For example: 30, 50–60, 65500–65510) Use the same port range for Internal port
Internal Port Range
(1~65534) Internal IP address ... Or select from currently attached devices
> What is the router's WAN/Internet IP address? Is that your public IP address? ("a.b" of "a.b.c.d" would be enough of your public IP address to satisfy my curiosity.)
I double check and my IP address for my internet port is the same address as my public IP. I assume "a.b" is 47.205
>The usual problems with this stuff are:
For number 1. I've double check that the IP address of the internet port is the same as the public IP. "(An intermediate NAT router, for example, could cause this. Or an ISP using carrier-grade NAT to conserve IPv4 addresses.)" I dont under stand what that mean. Can you explain more?
For number 2. I'm pretty sure I got the right port and right IPv4 address of my PC. I do not understand whats " wandering target" mean. Can you explain?
For number 3. "Server not listening on the port-forwarding target system." Can you explain it more?
For number 4. I disable my PC firewall, I do not know where the Nighthawk R7000P firewall setting is, So I assume that it wasn't a obstruction to port forwarding. As for ISP, I've contact them, they said they only block ports 80 and 25.
>What's at "192.168.1.10"? Is that a reserved address for some device (server)?
That is the IPv4 address for my PC yesterday. I did not set it to a static IP so it changes. Today my new IPv4 is 192.168.1.12
> [...] 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:
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.
> 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
in the outside world can't connect, then you can worry about that.
I've try the test, I believe, I try to connect to the server using the internal IP address and it did conect and go through. But when I try to connect to the WAN IP address, which is the public IP address, It could not connect, I've a friend connect to it and he can't connect either.
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.
