vexed wrote:For the router, it is NOT needed to port forward internal ports to the LAN, in fact, that can screw things up.
Port forwarding is used for external connections to the machine hosting the game.
So, if you are hosting on 192.168.1.55, then the port forward should be TCP port 2100 for 192.168.1.55.
You don't mention which specific router you have, but, usually the cheap ones won't let you go through the lobby to connect to your game, if you are both on the same subnet.
Now, with that out of the way:
Step 1: disable AV & firewall. (Some AV's also have firewalls as well).
Step 2: run warzone, select MP, setup what you want, then hit start hosting button. If the router has the ports open for WZ to this machine, then you will be shown in the lobby, so, either make the game private, or change the masterserver_name=lobby.wz2100.net in the config file to masterserver_name=127.0.0.1 or whatever.
Step 3: WZ should be waiting for connections. Verify this by opening a admin level command prompt and typing in
netstat -na |find "2100" and you will see:
Code: Select all
TCP 0.0.0.0:2100 0.0.0.0:0 LISTENING
TCP [::]:2100 [::]:0 LISTENING
As you can see, it is saying both IPv4 and IPv6 port 2100 (TCP) is waiting (listening) for connections.
That is all you need to verify.
Now, the other machine should connect via IP to the one hosting, (192.168.1.55 for my example), and it should work.
If not, then something is blocking it on their end, most likely firewall or some AV programs or misconfigured router.