Troubleshooting
How to Improve P2P NAT Traversal Success
The practical goal is to reduce unnecessary translation and filtering while testing one variable at a time instead of disabling all security controls.
Create a reproducible baseline
- Update both clients and verify that both devices are online.
- Record the networks, time, and failure stage.
- Change one variable at a time and retry.
- Move one endpoint to a mobile hotspot as a comparison.
Reduce endpoint blocking
- Verify system time and time zone.
- Allow the client and background service through Windows Firewall.
- Temporarily pause third-party security software only for diagnosis, then restore it and add narrow rules.
- Check whether VPNs or other virtual adapters changed routing.
Note: Do not leave the firewall disabled or place the PC permanently in a router DMZ.
Simplify the router path
- Record the main router WAN address.
- Check whether the modem is also routing and assigning a private address.
- Where you control the setup, keep only one NAT layer by using bridge or access-point mode.
- Try UPnP only on a trusted network and review created mappings.
Identify CGNAT or restricted networks
- The WAN address is in 100.64.0.0/10 or another private range.
- The WAN address differs from a public-IP lookup.
- A mobile hotspot or different ISP changes the result.
- Campus, hotel, and guest networks may block UDP or client-to-client traffic.
Collect useful diagnostics
- Client and operating-system versions.
- Whether failure occurs at presence, traversal, or application access.
- WAN address class and number of routing layers.
- Logs from both endpoints for the same time window.