NETGEAR is aware of a growing number of phone and online scams. To learn how to stay safe click here.
Forum Discussion
Solved
Port Forwarding not working
First of all, information.
Router model: CG3700EMR.
Firmware Version: V2.01.03
The model isn't on this website for some reason, but I found somewhere that the CG3700 is very similar to the CG3200?
Okay now for the problem. I need to Port Forward my 25565 port but it's not working. I have no idea why but when I go to websites like canyouseeme.org it just reports "Error: I could not see your service on 176.23.22.104 on port (25565)
Reason: Connection timed out" I've tried everything from disabling all firewalls (router and computer) to making multiple ports forwards (one for TCP and one for UDP) to disable UPnP. Nothing works. The port stays closed no matter what I do (I have tried restarting the router.). If any more information is needed I will supply. I have some images that show the log and the problem.
You've published your public IP address, and obscured your (harmless)
private address. You're keeping the wrong address secret, which helps
no one.
> [...] multiple ports forwards (one for TCP and one for UDP) [...]
That was a waste of effort. One rule can do both.
> The port stays closed no matter what I do [...]
Are you running a server at 192.168.blur.blur which is listening on
port 25565? What is the server at 192.168.blur.blur?
In my experience, people who talk about opening ports often don't
understand the problem. For a port to appear to be "open", there must
be a program on the target system which is listening at that port. If
you're not running such a program, then all the port forwarding in the
world won't help.
5 Replies
My reply got deleted? Well, here it is again. I'm sorry I accidentally posted every picture twice. And if anyone knows how to delete/edit previous posts, can you please tell me?
Yeah, I want to delete that one because I figured out that that wasn't the problem...
You've published your public IP address, and obscured your (harmless)
private address. You're keeping the wrong address secret, which helps
no one.
> [...] multiple ports forwards (one for TCP and one for UDP) [...]
That was a waste of effort. One rule can do both.
> The port stays closed no matter what I do [...]
Are you running a server at 192.168.blur.blur which is listening on
port 25565? What is the server at 192.168.blur.blur?
In my experience, people who talk about opening ports often don't
understand the problem. For a port to appear to be "open", there must
be a program on the target system which is listening at that port. If
you're not running such a program, then all the port forwarding in the
world won't help.