Hey i opened the ports for mw2 but my nat type is still strict

in mw3 i opened the ports and now i have an open nat type... but in mw2 not

same problem.

The most common port to open is 28960 TCP/UDP.

 

This will guarantee an Open NAT, with uPnP enabled in your modem settings.

 

If this doesn't work, then don't worry it's probably a glitch.

You shouldn't really need to open any ports unless you're actually hosting a server

You shouldn't really need to open any ports unless you're actually hosting a server

 

Incorrect, if you have no ports open, how will someone connect to you, if you're playing a private match, Or trying to connect to a server which has port that you have blocked. Even if their port is open.

 

I would port forward 28960 TCP/UDP just incase

You shouldn't really need to open any ports unless you're actually hosting a server

 

Incorrect, if you have no ports open, how will someone connect to you, if you're playing a private match, Or trying to connect to a server which has port that you have blocked. Even if their port is open.

 

I would port forward 28960 TCP/UDP just incase

 

I know that my clan leader hosts servers off of his LAN and I forward the ports 28960-28980 to the server in his house

Yet he can always connect to our servers in Canada on the same ports that he has open to a different local IP

(That's on the router)

He has a firewall on and I don't think he has ever forwarded the ports in it

I guess windows adds the exception itself

 

But I would also recommend forwarding 28960 on your router and firewall just to be on the safe side

The NAT restricted red text is bugged, and it most likely won't be fixed. To determine whether the ports were open, the IWNetServer sent a packet (or the other way round?) to the client, which was known as the 'ipdetect' packet.

 

As someone said, as long as you are not hosting a server of any kind, it can be disregarded, and you can play normally.

 

 

IW4M's dedicated servers require the TCP port to be opened, though