Netgear DGN2200v2(BEZEQ) port forwarding allways fails

[ChemiHatake]

Hello,
I'm trying to open a port so I can host my webpage map and access it from my mobile phone,
But it doesn't matter what I do, The ports are always closed.
I've already opened ports a while ago for hosting a mc server and it worked,
but I've deleted them when I stopped using the server and now I just can't open the ports.

Please help, I've tried following many tutorials and installing port forwarding software but they all do the same and the result is always the same.

Chemi ~

[trpted]

#1 Go to http://whatismyipaddress.com/

#2 On that web page is the non bogan IP (Public) Address that users from Internet use to connect to you.

#3 In your router, you must have the same non bogan IP Address.

#4 If your router you do not see the non bogan IP Address, it first depends on the WAN IP in the router.

a) If the WAN IP in the router is in the IP Address Range of 100.64.0.0 - 100.127.255.255, then CGNAT/NAT444/LSN is present.

--

If you want more details about CGNAT/NAT444/LSN, you can look at

http://en.wikipedia.org/wiki/Carrier-grade_NAT

The possible fixes to fix your issue if CGNAT/NAT444/LSN is present.

#1 Have them in their NAT router forward the ports to the IP of your router..

#2 Upgrading the type of plan that you are on with your ISP so that you get a non bogan IP Address.

For example if you are a Residential Service Plan, consider going to a Business Service Plan.

#3 Consider switching to another ISP that can give you you a non bogan IP Address.

#4 For the long term future, get IPv6 working.

--

b) If the WAN IP in the router is any of these IP Address Range(s):

From 10.0.0.0 to 10.255.255.255, from 172.16.0.0 to 172.31.255.255 OR from 192.168.0.0 to 192.168.255.255 now it matters the type of NAT router it is.

-> Based upon your type of router, CGNAT/NAT444/LSN is present ( see above for fix ).

d) If the WAN IP was not any of those, it would be a good idea to check to see how the non bogan IP Address is not the same (and not NAT). If users need help finding why that is, they are to asking for help doing so.

[ChemiHatake]

#1 Go to http://whatismyipaddress.com/

#2 On that web page is the non bogan IP (Public) Address that users from Internet use to connect to you.

#3 In your router, you must have the same non bogan IP Address.

#4 If your router you do not see the non bogan IP Address, it first depends on the WAN IP in the router.

a) If the WAN IP in the router is in the IP Address Range of 100.64.0.0 - 100.127.255.255, then CGNAT/NAT444/LSN is present...

Thanks for writing this detailed and informative comment.

So I have the best plan possible at the moment,
And I successfully opened ports a while ago. But I haven't switched an ISP or the plan since then.

So maybe Ill ask them some questions about that (not sure the ones answering the phones will even understand what I want) but ill try anyways.

And I found a way to use a static IP in the router settings and maybe its worth a shot.
So what should I put in there to make it work?
And how do I do the first fix and the forth one? 

(sorry for the low quality picture it was captured on my phone)

[trpted]

The only way to setup a Static WAN IP based upon the type of NAT router that you have is like this..

#1 Contact the ISP.

#2 You might have to upgrade the type of plan that you are on with your ISP so that you get one.

For example if you are a Residential Service Plan, consider going to a Business Service Plan.

#3 They will provide to you the following settings: IP Address, Subnet Mask, Default Gateway, and DNS Sever(s) to use.

#4 The following settings that they told you to use, you must use:  IP Address, Subnet Mask, and Default Gateway.

#5 For the DNS Server(s):

a) it is recommend to use the ones that they provide, at first.

b) Once you know the connection is up and running, most ISPs will allow you to connect and use any DNS Server(s) that you want to use.

c) There are some exceptions to this (5b above). Examples that come to mind..............

One -> Those DNS Server(s) are related to malware. For example typing in paypal.com into your URL normally takes you to the real paypal.com, but if the DNS Server(s) are bad don't count on it. Instead takes you to a phishing site that looks and feels like the real paypal.com

Two -> Those DNS Server(s) are for IPv6 clients and if you do not have public IPv6. Note by public IPv6 I do not mean an IPv6 Address that starts off with fe80.

Three -> Those DNS Server(s) are not just DNS, they are DNSSEC (kind of like SSL but for DNS) and if your DNS client does not understand DNSSEC. Note: When I hear/read the word SSL, the first thing that comes to mind is an URL that starts off with HTTPS instead of HTTP.