Configuring your network for Ditto

For Use with Ditto Receiver Only
This article only applies to organizations using Ditto tvOS Receiver or Ditto Windows Receiver. These network instructions do not apply to other Ditto receiver types (Chromecast, Apple TV 3, and older).

Ask us for assistance if needed.

Key Points

  • Make sure TCP ports 55200 - 55205 are open
  • Ditto Connect for Web requires and all variations of that domain to be whitelisted on the network
  • Ensure proper network traffic routing if using subnets
  • Discovery protocols such as mDNS, Bonjour, and multicast are not required
  • Ditto works with proxy servers if needed

Open TCP Ports

Ensure the devices on your network allow communications from TCP port 55200 - 55205. This is the port that Ditto uses to route sender and receiver communications. Some firewalls block ports 55200 - 55205 traffic. When organizations have trouble connecting to Ditto after initial setup, this often resolves the problem. 

Opening TCP ports 55200 -55205 does not create any known security vulnerabilities.

Whitelist Domains and all variations of that domain will need to be whitelisted on the network to use Ditto Connect for Web. Ditto Connect for Web can use several versions of this domain to make connections to the Ditto receiver.

If or any of its subdomains are blocked, then connection issues may occur with Ditto Connect for Web but not with the installable version of Ditto Connect. 

Ensure Proper Subnet Traffic Routing

Subnets, referred to as VLANs in certain cases, are frequently used in corporate and school networks to keep device traffic separated from other device traffic. For example, subnets can keep discovery traffic such as mDNS, Bonjour, and multicast announcements from flooding to other networks. This traffic policing and traffic shaping can prevent devices from discovering each other, such as the Ditto Receiver on a corporate network and guest devices on the guest wifi.  

Fortunately, Ditto will work even if your network requirements dictate that you must have separate subnets. Allow bidirectional IP routing between the subnets that support the Ditto Receiver and end-user devices. If you do not want to route all network traffic between subnets, you can selectively route network TCP port 55200 - 55205 traffic between the subnets.


Most screen-sharing solutions rely on discovery protocols such as mDNS, Bonjour, or multicast announcements for user devices to find and connect to a receiver. These protocols work fine on a simple network, but they don't scale well when there are hundreds of devices on different networks. 

Ditto doesn't require any of these protocols to work. This means you can disable multicast, Bonjour, and mDNS on your network entirely and Ditto will still work great. This also allows you to simplify your network by removing VLANs or subnets that only serve to keep multicast traffic from flooding to other networks.

Proxy Servers

Ditto also works with proxy servers.