Page 1 of 1

Webbrowse on Vista, dynamic DNS

Posted: Sun Jul 22, 2007 4:08 pm
by Rainer
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

Re: Webbrowse on Vista, dynamic DNS

Posted: Sun Jul 22, 2007 4:46 pm
by Rainer
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

Re: Webbrowse on Vista, dynamic DNS

Posted: Sun Jul 22, 2007 5:43 pm
by Rainer
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

Use a different port for remote access

Posted: Mon Jul 23, 2007 8:42 am
by dogbot123
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.

Re: Use a different port for remote access

Posted: Tue Jul 24, 2007 6:03 am
by Rainer
Thanks, this works!