![]() Although changing the ports cause tremendous lag, but it solved the problem, temporarily. After all the effort of forwarding ports and turn-off programs that might have potentially blocked the ports, my solution is to switch to another ports in the game settings, plays 1 or 2 matches, then switch back the original ports. On average I got at lease 1 or 2 Secured NAT error per 4 - 5 hours of game play (which is annoying as hell). If those aren't redirected you'll still get those error. If the desired Ports are blocked by another application (it doesn't matter wich is it) Waframe is looking for other free ports. Isn't there a possibility in your router to change the nat? It has to be done by your Router not on your PC If possible: disable it or at least turn it of at those devices you don't need online. The Router (if not configured otherwise) will still NAT the package becaus otherwise your PC wouldn't be reachable from the web. Your PC is sending packages to the Router, the Router exchanges next hop adresse with the Server you want to connect to and vice Versa. Natting is basically a procedure in what the router changes the package you have sent: THat's the IP your Router gets and it uses to be "Online" ![]() Nat is a function of your Router to gain Internet Access with more than one PC.
0 Comments
Leave a Reply. |