Il 04/06/2017 18:08, ITwrx.org ha scritto:
this computer is the one you successfully accessed the minidlna web page from? or a different computer connected via ethernet? i'm just trying to verify that you have successfully accessed the webpage for minidlna from a wireless device/computer.
if yes, then you could use nmap or a nmap gui (nmap-qt4 ?) to scan the host that is supposed to be serving minidlna and make sure that port is actually open/visible. IOW, just start ruling things out. If that port is open/accessible from a remote machine then try different apps on the clients to make sure it's not just buggy clients. you might also try different minidlna servers. i know when i tried to use minidlna the servers and client apps were very picky and some were very flakey too. i ended up ditching minidlna(even though i had it working most of the time) and just using samba just because i didn't like how non-robust it all was.
The computer I was referring to is the server I am trying to access. I've accessed the webpage from my laptop.
There is a strange thing indeed: the server has actually no firewall, however the 1900 UDP port, which should be open for SSDP seems closed.
Here it is the result of some investigation --- # On my laptop $ nmap -sU -p 1900 santini_server Starting Nmap 7.40 ( https://nmap.org ) at 2017-06-05 11:32 ora legale Europa occidentale Nmap scan report for santini_server (192.168.0.109) Host is up (0.027s latency). PORT STATE SERVICE 1900/udp closed upnp MAC Address: 00:1E:2A:43:47:3E (Netgear)
Nmap done: 1 IP address (1 host up) scanned in 12.43 seconds
# On the server $ sudo iptables --list Chain INPUT (policy ACCEPT) target prot opt source destination
Chain FORWARD (policy ACCEPT) target prot opt source destination
Chain OUTPUT (policy ACCEPT) target prot opt source destination --- No idea why MiniDLNA does not check the port.