Before you start
You need infrastructure-reading permission and the corresponding administration capability for forwarding changes. Verify the intended workload, destination, protocol and exposure before making a change.
What to do
- Open Networking & firewall and inspect existing manual forwards alongside interfaces, routes, listening ports and the effective firewall information.
- When an authorised new forward is needed, use Forward port and review its public/destination port, TCP or UDP protocol and the intended hosting-machine destination.
- Read the exposure warning and enter the requested port confirmation. Do not add a manual duplicate merely because a game's automatically managed port is not in the manual list.
- Inspect the operation result and the resulting forward entry, then verify the intended service separately. A forward does not start a stopped process or supply application authentication.
- To remove a manual forward, review the exact port, protocol and destination before using Remove and its confirmation. Check the resulting inventory and intended service behaviour afterwards.
What happens next
The forwarding inventory shows the accepted manual mapping. Public reachability still depends on the workload, its listener and the applicable network and application controls.
If something goes wrong
Check the selected destination, protocol, port and existing automatic mappings before diagnosing a failure. Do not disable a firewall or unrelated protection to make a test pass. After an uncertain change, inspect the operation and current forward entry before retrying. Contact the infrastructure administrator with the intended service and redacted error rather than publishing internal network details.
