Remote access questions...

General discussion about the media server. Feature requests. Hints, tips and tricks.
Locked
liquid
Posts:10
Joined:Mon Dec 08, 2008 3:47 am
AV Hardware:2TB MyBook World edition II, Dell M2010 running Vista Home Edition, Xbox 360
Remote access questions...

Post by liquid » Wed Dec 17, 2008 4:04 am

I have successfully accessed my twonky server from outside my LAN setup. Two things bug me however.

1. If i access it from inside my LAN, use the web browser interface and click a video file, It attempts to download the file instead of stream it... Is this supposed to happen? If I attempt to open the link with WMP it just hangs trying to load.

2. From outside my lan, all the links point to my LAN ip address. 192.x.x.x:9000 instead of x.x.x.x:9000 which would be the IP of my router assigned by my isp. I have set up port forwarding to be able to get in from outside. Is there a setting I need to toggle to fix this?

Thanks,
liquid

wami
Posts:2
Joined:Wed Dec 17, 2008 7:58 pm
AV Hardware:twonky

Re: Remote access questions...

Post by wami » Wed Dec 17, 2008 8:02 pm

Same problem, I took a request two weeks ago, til now no reply from "Support" or what is calling so :x

kr

Michael

liquid
Posts:10
Joined:Mon Dec 08, 2008 3:47 am
AV Hardware:2TB MyBook World edition II, Dell M2010 running Vista Home Edition, Xbox 360

Re: Remote access questions...

Post by liquid » Fri Dec 19, 2008 7:42 am

Did some searching found this in another thread... by Goo5e
Finally found a workaround for this after having the same problem for some time, hopefully this will sort it for you too. Here's what you need to do:

Edit the twonkyvision-mediaserver.ini file (the live version is in applications/twonkymedia, but I couldn't edit it directly - some kind of permissions problem. I just edited a copy on my PC then deleted the version on my NAS and copied it over after I'd made the changes on the PC.

Find the section '# Dynamic DNS' and put the external internet address you use to remotely access your NAS after the 'dyndns='. E.g. I use http://www.no-ip.info for my IP redirection, I assume you've probably got yours already set up in a similar fashion. So the line should read something like:

dyndns=http://yourserver.no-ip.info:9100

It is important that you use a port other than 9000 as this is reserved for internal use by twonky, doesn't matter too much as long as it's a spare port - 9100 works fine for me.

Further down the ini there is a '# HTTP remote port' section. You need to add the same port as used above, e.g:

httpremoteport = 9100

Finally you need to add the port redirect on your router for 9100 (or whichever port you've chosen). And that should be it sorted.

Now to access your server just enter http://yourserver.no-ip.info:9100 in your browser and all media links should be prefixed with your external http redirected address rather than the internal 192.168 address.

Working perfectly for me at long last!
I havn't tried it but it seems like it would work...

FarmCretin
Posts:2
Joined:Sat Jan 03, 2009 6:43 am
AV Hardware:home ubuntu server
xbox 360
linksys router

Re: Remote access questions...

Post by FarmCretin » Sat Jan 03, 2009 6:51 am

thats the exact method i've been using for the past few releases. i've been editing the "httpport=" value in "twonkyvision_mediaserver.ini" to the port of my choosing. i have many webUIs running at the same time and its an absolute necessity to run twonky on a port other than 80. in the new 5.0 release, there is no twonkyvision_mediaserver.ini, and i dont so another way of achieving this. if any one finds a way, please share.

malaki86
Posts:28
Joined:Mon Nov 26, 2007 10:40 pm

Re: Remote access questions...

Post by malaki86 » Thu Dec 31, 2009 1:08 pm

I'm having the same problem (version 4.4.9), but they Dynamic DNS & Remote Port are already correct in the ini file.

I've restarted the twonky server from the config page. Should I also restart the machine?

malaki86
Posts:28
Joined:Mon Nov 26, 2007 10:40 pm

Re: Remote access questions...

Post by malaki86 » Thu Dec 31, 2009 2:33 pm

Restarting the machine made no difference either. The links still show as http://192.168.1.2:9000/etc...

Locked