I do not want to allow the whole Applikation (like WindowsFirewall). I try to open 1030, 1900, 2869, 5000, 9000, 9020, 9021and 9080, but only if i shutdown the FW TwonkyManager works correct.
No other things like AV etc. installed.
From the application point of view we can only define the ports that Twonky web config page will use. The server uses UDP ports 1030, 1900, 9080 and TCP port 9000 – unless it’s already in use. In that case, we select the first available free port after 9000. UPnP uses 1900 UDP port and 2869 TCP port.
The local TwonkyManager player uses port 9020.
The TwonkyManager controller uses port 9021
While interacting with different devices (DMP's and DMR's) connected on the network Twonky can use any port depending on the availability and device specifications.
For example:- For playing files on an Xbox 360 or a networked digital media player ports from 8554-8558 will be used.
I suggest that easy way to resolve this issue is you can add to allow all Twonky connections as an exception in firewall settings.
OK, my Twonky server installation runs on a central home server (Ubuntu Linux 64 bit) with several services for home users, e.g. file / printer sharing, http proxy, voip, active directory and some more (see www.zentyal.org) for details. One of the services is the firewall protecting the server from unrequested requests. The firewall is by default closed for all ports exept the required once for the services running on it. E.G. 8080 /443 are open by a service execption rule for the https server (apache). As all other ports are closed, my twonky server installation is not visible to my clients. Opening just port 1900 does not help. If I open all ports (but I do not want to) the clients connect to Twonky perfectly. I can open single ports or port ranges - so I would like to know which prots I will have to open within my firewall to make sure that twonky is visilbe & accessible to any client on my LAN (at least 5 - 7 clients: IPad, IPhone, No-Name Media Player (Medion), Windows 7 Media Player, Linux with different players)
Thank you and best regards
CHAMP0These are just about all the ports that I am aware of that are in play
TCP port 2869
UDP port 1900
TCP port 9000
UDP port 1030, 1900, 9080
(possibly UDP 1030-1032 )
TCP port 9055
TCP port 9050
TCP port 1030, 11xx
UDP port 1900
(11xx seems to be random and is used to talk to server on port 9000)
There is also this, but I need to see if this is still true, as https isnt working
that I know of
TwonkyServer using TLS (SSL) - 9443