Hi All,
Ok I have setup a HTPC with Mint and minidlna
On the HTPC itself minidlna running, and using VLC as a client I can 'see' the minidlna server under VLC's Playlist Network uPnP option
If I move to another Linux Mint client (a Laptop) and run VLC I can NOT see the minidlna server.
What have I missed? It's got to be something basic/simple! Feels like a networking issue! but where?
Ultimate goal is to get smart TV/BD players to 'see' this HTPC
I have also tried windows 7 media player to no avail.
Below is my minidlna.conf
Any suggestions please?
# If you want to restrict a media_dir to a specific content type, you can
# prepend the directory name with a letter representing the type (A, P or V),
# followed by a comma, as so:
# * "A" for audio (eg. media_dir=A,/var/lib/minidlna/music)
# * "P" for pictures (eg. media_dir=P,/var/lib/minidlna/pictures)
# * "V" for video (eg. media_dir=V,/var/lib/minidlna/videos)
#
# WARNING: After changing this option, you need to rebuild the database. Either
# run minidlna with the '-R' option, or delete the 'files.db' file
# from the db_dir directory (see below).
# On Debian, you can run, as root, 'service minidlna force-reload' instead.
media_dir=/var/lib/minidlna
media_dir=V,/home/htpc/Videos
media_dir=A,/home/htpc/Music
media_dir=P,/home/htpc/Videos
# Path to the directory that should hold the database and album art cache.
db_dir=/var/lib/minidlna
# Path to the directory that should hold the log file.
log_dir=/var/log
# Minimum level of importance of messages to be logged.
# Must be one of "off", "fatal", "error", "warn", "info" or "debug".
# "off" turns of logging entirely, "fatal" is the highest level of importance
# and "debug" the lowest.
log_level=error
# Use a different container as the root of the directory tree presented to
# clients. The possible values are:
# * "." - standard container
# * "B" - "Browse Directory"
# * "M" - "Music"
# * "P" - "Pictures"
# * "V" - "Video"
# if you specify "B" and client device is audio-only then "Music/Folders" will be used as root
#root_container=.
# Network interface(s) to bind to (e.g. eth0), comma delimited.
network_interface=eth0
# IPv4 address to listen on (e.g. 192.0.2.1).
#listening_ip=
# Port number for HTTP traffic (descriptions, SOAP, media transfer).
port=8200
# URL presented to clients.
# The default is the IP address of the server on port 80.
#presentation_url=http://example.com:80
# Name that the DLNA server presents to clients.
friendly_name=HTPC-MINIDLNA
# Serial number the server reports to clients.
serial=12345678
# Model name the server reports to clients.
#model_name=Windows Media Connect compatible (MiniDLNA)
# Model number the server reports to clients.
model_number=1
# Automatic discovery of new files in the media_dir directory.
inotify=yes
# List of file names to look for when searching for album art. Names should be
# delimited with a forward slash ("/").
album_art_names=Cover.jpg/cover.jpg/AlbumArtSmall.jpg/albumartsmall.jpg/AlbumArt.jpg/albumart.jpg/Album.jpg/album.jpg/Folder.jpg/folder.jpg/Thumb.jpg/thumb.jpg
# Strictly adhere to DLNA standards.
# This allows server-side downscaling of very large JPEG images, which may
# decrease JPEG serving performance on (at least) Sony DLNA products.
strict_dlna=yes
# Support for streaming .jpg and .mp3 files to a TiVo supporting HMO.
enable_tivo=no
# Notify interval, in seconds.
#notify_interval=895
# Path to the MiniSSDPd socket, for MiniSSDPd support.
#minissdpdsocket=/run/minissdpd.sock
Regards
Steve
minidlna - works localy but can't see via dlna clients?
Forum rules
Before you post read how to get help. Topics in this forum are automatically closed 6 months after creation.
Before you post read how to get help. Topics in this forum are automatically closed 6 months after creation.
minidlna - works localy but can't see via dlna clients?
Last edited by LockBot on Wed Dec 28, 2022 7:16 am, edited 1 time in total.
Reason: Topic automatically closed 6 months after creation. New replies are no longer allowed.
Reason: Topic automatically closed 6 months after creation. New replies are no longer allowed.
Re: minidlna - works localy but can't see via dlna clients?
Hi,
did you open TCP port 8200 and UDP port 1900 on your firewall? I suppose ufw is active!? You can easily open allow incoming traffic on those ports using the GUI gufw for the firewall.
The minidnla.conf looks file.
Cheers!
did you open TCP port 8200 and UDP port 1900 on your firewall? I suppose ufw is active!? You can easily open allow incoming traffic on those ports using the GUI gufw for the firewall.
The minidnla.conf looks file.
Cheers!
Re: minidlna - works localy but can't see via dlna clients?
On linux mint 20.4 I found I had to specify the network interface, and then it worked like a charm instantly after sudo service minidlna restart
Usually linux mint comes without firewall, so that's not likely to interfere
(remember to uncomment the # in front of network_interface, and specify your interface name(s) found with ifconfig)
Usually linux mint comes without firewall, so that's not likely to interfere
Code: Select all
# Network interface(s) to bind to (e.g. eth0), comma delimited.
# This option can be specified more than once.
network_interface=enp4s0