Can’t find the Twonkymedia service after installing 6.0.30
After installing the new Twonkymedia 6.0.30, I can’t find the service, when I try using the IP xxx.xxx.xxx.xxx:9000, I get the message
can’t connect.
I had a total reset to default on my TS-459Pro, after harddisk failure, so I formated all my drives, but now it seems the buildt in UPnP, doesn’t work either.
Are there any other services I need to start before using Twonky or the buildt in UPnP service?
EDIT: It seem’s that Twonkymedia can be found on my other IP adress for the network LAN2, not on LAN1, how come?
Having two interfaced configured into the same TCP/IP subnet is not reliable, services can bind to one or both interfaces – and thee is actually no control.
The TCP/IP stakc can use any interface to send the return packets – and thehse will come from a different IP address.
Do _not_
– connect both interfaces into the same broadcast network and the same DHCP server subnet.
– configure both interfaces into the same TCP/IP subnet
This can and will lead to massive operational and reliability issues.
One useful thing to know is that you can force Twonky to advertise itself on only one IP address via a simple RPC call (typed into a web browser); the example below shows how I’d set it if my NAS was on 192.168.96.20:
CODE: SELECT ALL
http://192.168.96.20:9000/rpc/set_option?ip=192.168.96.20
The above call adds ip=xxx.xxx.xxx.xxx (or in my above example, ip=192.168.96.20) to the Twonky ini file and sets Twonky to broadcast on only that IP address.
By default, Twonky advertises itself on both the IP and loopback addresses (in the above case, 192.168.96.20 and 127.0.0.1) and some early Linn DS control points (very early versions of Kinsky PDA) randomly picked up either (this has now been fixed), so I used to set the IP as above to hide the 127.0.0.1 option; I’d thus expect it might also be useful where two IP addresses have been allocated to a dual-port NAS.
Not sure if this will help, but it’s handy to know it might save you having to use two different subnets.
If your NAS changes its IP address, it doesn’t cause any problems accessing Twonky; it just broadcasts on both loopback and normal until you send a new RPC call with the correct address.