Skip to content
Callaba

NDI ports and discovery: troubleshoot missing sources and video

On this page

An NDI source can be missing from the list, visible but unable to connect, or connected without usable picture or sound. Start with the symptom you see:

Use the same sender and receiver throughout the checks. Note their source names, NDI versions, network interfaces and the time of each test so you can compare the results.

When an NDI source is missing, prove discovery first

Confirm that the sender application or device is running and has its NDI output enabled. Then check that the receiver is looking on the intended interface and that both endpoints belong to the expected NDI group. A source missing in one application but visible in an NDI diagnostic tool can be an application/runtime or configuration problem, not a network-wide discovery failure.

By default, NDI uses mDNS for zero-configuration discovery. Its IPv4 multicast address is 224.0.0.251 on UDP 5353, and it is limited to one physical or logical LAN. On Windows, a Public network profile can prevent the mDNS responses NDI needs; on managed domain networks, the administrator must allow the discovery traffic. See the official NDI mDNS reference.

For an isolated, routed or cloud environment, choose a documented discovery design instead of assuming multicast will traverse it. A manual host entry can query a remote machine on TCP 5960, but it only helps a receiver find the sources on that machine. It does not establish media connectivity or create network capacity.

Configure Discovery Server on the sender and receiver

NDI Discovery Server is a centralized registry for installations where mDNS is undesirable or unavailable. Its default listener is TCP 5959, and the service can be bound to a chosen address or configured for a different port. Clients must use the same server address and port that the deployment intends.

The important detail is role-specific. A sender configured with Discovery Server does not advertise through mDNS; that sender is visible to finders and receivers configured for that server. Finders and receivers can also use mDNS for local machines that are not configured for Discovery Server. Treat this as a design choice, not a toggle to apply to one host and forget.

NDI 5 documents comma-separated Discovery Server addresses for supported clients. Test the exact sender, receiver and NDI version under a server loss: newer receiver-listener implementations can require client logic to detect a failed server and reconnect. The Discovery Server overview and its configuration reference are the source of truth for the installed version.

Use the port rule that matches the NDI mode

The following is one functional table, not a permission to allow an unrestricted range between every host. Apply the rule in the direction, zone and connection count used by the deployed sender and receiver. Confirm the installed NDI version and selected receive mode before making a least-privilege rule.

FunctionOfficial port ruleWhat the result proves
mDNS discoveryUDP 5353; IPv4 multicast 224.0.0.251Discovery traffic is present on that LAN, not that media is usable.
Discovery ServerTCP 5959 by default; configurableA client can reach the registry endpoint, not that it has a stream.
Manual host queryTCP 5960A remote host can be queried for sources.
Base TCP mediaTCP 5961 and up; at least one port per connectionUse when the selected connection mode uses base TCP.
NDI 5+ Reliable UDPUDP 5960 and up; shared with TCP, one port per NDI processConnection sharing changes the count assumption.
Multi-TCP or UDP receivingTCP/UDP 6960 and up; at least one port per connectionReceiver-side media rule for that mode.
Multi-TCP, unicast UDP or multicast UDP sendingTCP/UDP 7960 and up; at least one port per connectionSender-side media rule for that mode.

Current NDI documentation says versions 4.6 and later no longer use ephemeral ports. The complete NDI port reference should accompany any firewall change.

Check subnets and network interfaces

mDNS has a LAN boundary; routing, multicast relays and VPN behavior do not turn it into a general routed discovery service. Use Discovery Server or the participating product's documented manual-addressing method when the source and receiver are on separate controlled networks.

On a multi-homed host, record which interface owns discovery and which carries media. A management adapter, Wi-Fi connection or VPN can make a source appear from the wrong network or make replies leave by a route the receiver cannot use. Give the media interface stable addressing, avoid duplicate machine names, and make interface preference deterministic before the event.

Source listed but no picture or sound

A listed source means the receiver obtained a source advertisement or registry entry. It does not prove that the selected transport can open, that the return path is allowed, or that the receiver can decode the video. Inspect the active source URL and port, connection state, receive mode, video presence, audio presence and rendered output.

The current NDI Discovery tool can display registered senders, source address/port and receiver monitoring data including connection state, receive mode and video or audio presence. Use that evidence to select the next check. A TCP probe to port 5959 proves reachability to Discovery Server only; it does not prove an NDI media session.

Check whether mDNS reaches this Linux interface

Command
sudo tcpdump -ni <media-interface> udp port 5353

Expected result: mDNS packets appear while discovery is active on that interface. These packets confirm discovery traffic at this interface, not access to the selected media ports. Run packet capture and firewall diagnostics only with the authorization required for that production network.

Check Discovery Server reachability from Windows

Command
Test-NetConnection <discovery-server> -Port 5959

Expected result: a successful TCP connection to the configured server address and port. This confirms a reachable TCP listener. Check registration, group membership and media delivery in the NDI application.

Check discovered sources in Callaba

Callaba Cloud NDI gives an operator a place to configure discovery, interfaces and adapters, and its discovered-device workflow can show the current inventory. That is useful for separating a saved device entry from a source currently discovered by the selected instance. Check the selected source at the final receiver as well as in the inventory.

Once the source is current and the media path has been verified, configure the NDI adapter or the downstream job the production actually needs. Check its output separately in the target receiver; a discovery result is an input to that decision, not the acceptance test.

Record the working configuration

  1. Missing source: prove sender output, group, selected NIC and mDNS or Discovery Server configuration.
  2. Source listed, no session: record source address, transport mode and active media rule; inspect endpoint firewall and routing in both directions.
  3. Session, no usable frames: inspect receive mode, bitrate, video/audio presence, decode compatibility and actual rendered output.
  4. Before acceptance: repeat the successful path on the production interfaces and record configuration, source name and evidence for the runbook.

Next steps

Use Cloud NDI to configure the intended discovery and interface path, then read the discovered devices reference when the workflow needs an inventory check. Keep the production acceptance test at the final receiver: advancing picture, expected audio and the selected output path.