Config Files and Port Forwarding: Proof of a Working Boiii Server Setup
By Marcus Vance
A dedicated server running on your machine remains invisible to the outside world until your local gateway knows where to route incoming game requests. This requires adjusting network address translation (NAT) rules inside your home router, pointing incoming UDP traffic to your machine’s static local IPv4 address.
Access your router's administrative dashboard (commonly reached via 192.168.1.1 or 192.168.0.1) and locate the Port Forwarding tab. You must assign entries specifically across the User Datagram Protocol (UDP).
| Port / Range | Protocol | Target Scope | Functional Role in BOiii |
|---|---|---|---|
| 27017 | UDP | Host Machine | Primary game listener socket and traffic handshake |
| 3074 | UDP & TCP | Host Machine | Standard Call of Duty peer synchronization and NAT negotiation |
| 27016 | UDP | Master List | Heartbeat broadcasts pinging community server browsers |
After routing the ports in your gateway, open Windows Defender Firewall with Advanced Security. Create a new Inbound Rule, select Port, pick UDP, specify ports 27017, 3074, and permit the connection across Public and Private profiles. Skipping this step is the single most common cause of the "Server Not Responding" error reported by incoming players.
Marcus Vance is a cybersecurity auditor and technology writer dedicated to educating the public about online safety, data privacy regulations, enterprise security, and emerging cyber threats.
