DC CORE
Access a server behind NAT.
A server behind a router can initiate a connection even when unsolicited inbound traffic cannot reach it. Central uses outbound agent connections for supported management paths, so the server does not normally need a public port-forward.
Reach a private server through an outbound connection.
For an office server behind a broadband router, begin with its local service and the outbound path. Do not assume a public address on the router makes every private host reachable, or that opening port 22 or 3389 is required.
Prepare and verify the connection.
- Start at the target. Check the agent can run on the server, or that the approved connection point can reach the required local service. Keep the target’s authentication and firewall rules.
- Prepare outbound access. Use the destination and port requirements provided in Central. Ask the network operator to review restrictive egress rules, proxies or filtering before enrolment.
- Test from outside the site. Connect from the location your operator will use. Verify the target identity, the available tool and your ability to end the session.
Use Central for the setup and management tools.
Sign in to Central for the package and deployment instructions for your machine. Supported management paths use outbound agent connections, so public inbound management ports are not normally required. Your local network and target services retain their own access controls.
Central starts at £10/month for five devices, excluding VAT. See pricing and inclusions and check supported platforms.