DLNA Server
The DLNA Server component turns Banalytics into a local DLNA/UPnP media server. It exposes files from a configured File Storage component to smart TVs, media players, set-top boxes, and other DLNA-compatible clients on the same local network.
Expose File Storage as a local media server
The component publishes a UPnP MediaServer device, provides a ContentDirectory tree backed by the selected storage, and serves media bytes through an embedded HTTP streaming endpoint. This lets users browse and play recorded video, snapshots, audio files, or prepared media without opening the Banalytics web console.
Discovery
DLNA clients on the LAN discover the configured server name as a media server.
Content browsing
Folders and supported media files are exposed through the DLNA ContentDirectory service.
Streaming
The embedded server handles media downloads, HEAD requests, and byte-range requests for seeking.
Adding a DLNA server
Select the File Storage backend
Choose the File Storage component that contains videos, images, or audio files. The storage must be active and reachable when the DLNA server starts.
Set a client-facing server name
Use a short readable name such as Security Archive, Media Library, or Diagnostics. This is the name shown by TVs and media players.
Confirm the control and streaming ports
Keep the defaults unless another service already uses them. If you run several DLNA server instances, give each instance unique port values.
Allow access from the local network
Open inbound traffic to both configured ports on the agent host. The control port is used for UPnP communication, and the streaming port is used to fetch media files.
Supported formats and playback behavior
The server does not transcode media. It serves the original file with a MIME type detected from the file extension, so the client device must support the container, codec, audio track, subtitles, and bitrate.
Choosing settings for common scenarios
Local TV playback
Select a storage with media files and keep the default ports if they are free. Smart TVs and set-top boxes on the same LAN should discover the configured server name.
Recording archive browsing
Point the server to a storage where Banalytics recording or image tasks write finalized files. Operators can browse recordings from DLNA clients without opening the portal UI.
Separate libraries
Create separate DLNA server instances for different storages, for example Security Archive, Public Media, or Diagnostics. Use unique names and ports for each instance.
Operational guidance
Multi-interface hosts
HTTP media URLs are built from the detected local agent address and streaming port. On hosts with VPNs, containers, or multiple interfaces, clients may fail to stream if that address is not reachable from the DLNA network.
Large storages
Keep media organized into folders. Very large flat directories can make browse requests slower because DLNA clients ask for child folders and supported media files by path.
Playback quality
Large 4K files require enough storage throughput, network bandwidth, and client buffering. Prefer wired networking or strong Wi-Fi for high-bitrate video.
Configuration parameters
| Parameter | Required | Description | Default |
|---|---|---|---|
ID | Yes | A unique identifier automatically generated for this component instance. Read-only. | Auto |
Title | Yes | Display name of this DLNA server component inside Banalytics. | DLNA Server |
File Storage | Yes | Reference to the File Storage component that supplies media files exposed through DLNA. | None |
Server Name | Yes | DLNA device name advertised to UPnP clients. This is the name shown by smart TVs, media players, and other DLNA clients. | DLNA Server |
UPnP Port | Yes | UPnP discovery and control port. Change it when another local UPnP or jUPnP service already uses the default control port. Allowed range is 1024-65535. | 8895 |
Streaming Port | Yes | HTTP port used by DLNA clients to fetch media bytes from the embedded streaming endpoint. Change it when another HTTP service already uses the default streaming port. Allowed range is 1024-65535. | 8896 |
When clients cannot discover or play media
Check UPnP and multicast on the LAN
Some routers, Wi-Fi isolation modes, VLANs, VPNs, and container network modes block discovery traffic.
Verify firewall and port conflicts
Both the control port and streaming port must be available on the agent host and reachable by the DLNA clients.
Validate file compatibility
Unknown file extensions are hidden from browsing, and unsupported codecs or bitrates may appear in the library but fail during playback.
Related storage and recording pages
Use these pages to prepare the media library, create recordings, and decide where files should be stored before they are exposed through DLNA.