Skip to main content

NAT types explained and how to fix Strict NAT

Your NAT type determines how your node connects to other peers. If your node is behind Strict or Symmetric NAT, connections may fail or your node may show “Monitoring failed”

A
Written by Adine
Updated today

NAT types (simplified)

Open NAT

  1. Best connectivity

  2. Fully reachable by other peers

Moderate NAT

  1. Works in most cases

  2. Some connections may fail

Strict / Symmetric NAT

  1. Limited or no incoming connections

  2. Can prevent sessions from completing


Why Strict NAT causes issues

With Strict or Symmetric NAT:

  1. Incoming connections are restricted

  2. Port mappings are unpredictable

  3. Peer-to-peer communication may fail

This results in:

  1. Monitoring failures

  2. No sessions or incomplete connections


How to fix Strict NAT

1. Enable UPnP (recommended)

  1. Log in to your router

  2. Enable UPnP (usually under Advanced settings)

  3. Restart your node

2. Use port forwarding

  1. Assign a static IP to your node host

  2. Log in to your router

  3. Navigate to the port forwarding section

  4. Forward UDP ports:

    56000–56100
  5. Restart node and test again

If your router does not support UPnP, port forwarding is required.

3. Use DMZ (last resort)

  1. Log in to your router

  2. Enable DMZ

  3. Assign your node host IP

Note:

  1. DMZ reduces network security

  2. Use only if other methods fail


Platform-specific steps

If you need system-specific instructions:


Notes

  1. Router settings vary by manufacturer

  2. Avoid using multiple methods at the same time (e.g. UPnP + port forwarding + DMZ)

  3. Test connectivity after each change

Did this answer your question?