PortTriggering(NAT TYPE Strict)

Oct 7, 2018
3
0
10
Hello everybody i got problem. Me and my friend are unable to connect in several games.. so i decided to Try port forwarding my router (im beginner at this never done it before)
So i normally loged in to my router (Wireless TP-LINK Router TL-WR741ND) i watched bunch of videos About it and everybody is doing it through “Virtual Server” tab in router like mine. So i tried it too.. i have dynamic ip so i writen my IPV4 there port and hit enabled. Did this for all ports and nothing happend still nat type strict. Then i notice below “Virtual Servers” Tab a “Port Trigering” tab so i decided to Try that.. it was basicly same like The “Virtual Servers” tab but this one did not had ip tab there. But it worked ! I had nat type moderate. But The biggest problem was and thats the case im writing this i had 1 000-20 000 ping.. it was still bouncing on high numbers and most of The time i was not able to even connect a server.. so i want to ask If im doing something wrong and What cause this high Ping for me.. THANKS FOR ALL REPLAYS ! ^^
 
You really want port forwarding, not port triggering. I think the mistake you made when you try to do the port forwarding is it sounds like you put in your public IP address. The IP address you enter should be the IP address of the computer or console you are playing on (sounds like this might be a PS4). Try to set up the port forwarding again with IP address of your computer or console.
 
There are a few things to consider here.

1. Port trigger is the samething as port fowarding. The only difference is port trigger only opens that port when it is being used. When its not, the port is closed, hence it is more secure. Also some device handle port triggering differently. For example, on your modem it due to it not having a field to list an IP address, it most likely opens that port up for everything on the LAN, instead of a specific internal address. Most other devices, it works exactly the same way port forwarding does.

Normally port trigger is the preferred selection for port forwarding as it offers better protection. However, results may vary depending on your device.

2. You said you had a router behind the modem for wifi. How was it connected? Do you have the LAN traffic going through it as well? Depending on how you connected the LAN to the router, the router could be at play here as well, resulting in a double NAT. Meaning whatever port forwards you make in the firewall, you will need to make in your router as well. To avoid this in the future, call your ISP and ask them to bridge the modem. It will turn off the modems firewall and NAT features and simply pass all traffic down to your router. From there you can manage everything from your router, instead of two different places. Double NAT causes all kinds of issues.

3. Have you checked local windows firewall? Even if it is off, by default it is set to deny outbound packets. You either need to go into advanced settings and change to to allow both out and inbound packets by default when firewall is disabled OR make an exception for that port in your local windows firewall.

4. On your PC, are you using a static LAN ip?
 
Your WAN ip is a private IP address. This means there is another router in the path. If this other router is not in your house then you can not solve the NAT problem because the router is likely controlled by the ISP.

If this is the IP your ISP gives you the only real solution is to see if they offer public ip addresses....likely for a extra monthly charge.