Webbrowse on Vista, dynamic DNS

General discussion about the media server. Feature requests. Hints, tips and tricks.
Locked
Rainer
Posts:6
Joined:Sun Jul 22, 2007 3:57 pm
Webbrowse on Vista, dynamic DNS

Post by Rainer » Sun Jul 22, 2007 4:08 pm

Dear developpers,

I have spent a full day trying to change the private address 192.168.178.3 into my dynamic host name on ....no-ip.org.

I love Twonkey Vision, after this exercise however I am rather frustrated. I have changed both ini files following your explanations in the forum.

As this did not work, I have completely removed Twonkey, I have cleared the installation including all files and the registry - and before running the program after the installation I have modified the Ini files again. I reconfigured everything and to my surprise, the ini-files still contain the right entries for dyndns=http://xxx.no-ip.org:9000 and httpremoteport=9000 - still however, I get the wrong, local address when calling the ....webbrowse function.

Please help resolving this issue - final. I am running Vista, Twonkyvision 4.4.

Regards,

Rainer

Rainer
Posts:6
Joined:Sun Jul 22, 2007 3:57 pm

Re: Webbrowse on Vista, dynamic DNS

Post by Rainer » Sun Jul 22, 2007 4:46 pm

One more remark, although the links to Music, Videos and Pictures point to my local address 192.168.178.3, the <Home> button at the left points to the correct DynDNS address.

Hope this hint helps for a speedy resolution.

Regards,

Rainer

Rainer
Posts:6
Joined:Sun Jul 22, 2007 3:57 pm

Re: Webbrowse on Vista, dynamic DNS

Post by Rainer » Sun Jul 22, 2007 5:43 pm

I have just checked the HTML code generated and saw that the <Home> button contains a relative address while the dynamic content buttons point to an absolute address.

An easy solution would be to use relative addressing only when calling the webbrowse.css stylesheet.
Would appreciate very much if you could short term do a recompilation and deliver us un updated file, this should be quite easy as short term solution.

Regards,

Rainer

dogbot123
Posts:2
Joined:Tue Jul 17, 2007 4:27 pm
Location:UK

Use a different port for remote access

Post by dogbot123 » Mon Jul 23, 2007 8:42 am

Twonkymedia uses TCP port 9000 by default for internal access (e.g. from within you home network). If you want to configure remote access over the internet you MUST use a different port, 9100 for example.

Thus set dyndns=http://xxx.no-ip.org:9100 and httpremoteport=9100 and make sure your router is set up accordingly (if you have one)

http://xxx.no-ip.org:9100/mediabrowse should now work from the web
http://192.168.178.3:9000 should still be used internally.

Rainer
Posts:6
Joined:Sun Jul 22, 2007 3:57 pm

Re: Use a different port for remote access

Post by Rainer » Tue Jul 24, 2007 6:03 am

Thanks, this works!

Locked