When a user tries to connect to a computer, Jump Desktop Connect will try to establish a direct connection between devices by using UDP on ports starting at 35384 through 35484. Jump Desktop Connect uses TCP ports 80 and 443 to connect to our cloud infrastructure. Which ports does Jump Desktop Connect use? Here is a list of servers that you should allow through: If you have macOS's Gatekeeper feature enabled on macOS (enabled by default) your environment may also need access to Apple's certificate servers to make sure apps by 3rd party developers are allowed to run on the system. MacOS Gatekeeper and certificate validation servers Important note: Our servers are behind load balancers and public IP addresses may change.įor best performance a direct connection needs to be established between computers and UDP packets need to allowed to flow through your network / VPN / firewall. Required only if you are testing beta builds. You can ignore this if you have direct networking line of sight between devices or you're using your on relay server. Required for indirect or relayed connections. Make sure to allow the following hosts on your firewall: Server Name How do I allow Jump Desktop Connect to connect to your cloud infrastructure? See our Adding Computers To Your Team Guide.įor non-Teams users see our non-Teams mass deployment guide for Jump Desktop Connect. We recommend using Jump Desktop for Teams and the preconfigured installers. How can I mass deploy Jump Desktop Connect to computers? If a direct connection can not be established, Jump Desktop Connect will use one of our global relays to connect to the machine. When you try to connect, Jump Desktop Connect will use our cloud infrastructure to bootstrap a direct connection between your devices. Jump Desktop Connect uses an open source, widely deployed technology called WebRTC create connections behind NATs and firewalls. How does Jump Desktop Connect create a connection between computers?

Jump desktop remote printing rdp