The UK Home Automation Archive

Archive Home
Group Home
Search Archive


Advanced Search

The UKHA-ARCHIVE IS CEASING OPERATIONS 31 DEC 2024


[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]

RE: TIVO - edit programme names?



>	I had to use apache to get this to work and you could also set
>thing in the TiVo web config.
>
>What have you got that is doing the port forwarding.
>


My Vigor 2200 router... I have the redirection set to map port 82
externally, and I have also configured a new virtual directory on my IIS
server to privide a friendly URL...

So it should go:

http://paulgordon.homeip.net/tivo
- hits my IIS servers virtual directory,
which is configured to do a redirect to...

http://paulgordon.homeip.net:82
- IIS sends the redirect to the browser
which then makes another request for port 82, which will hit my router and
should be redirected to the appropriate internal address...

I use this method for several internal servers with no problems. Of course
for troubleshooting I can bypass the IIS redirect which is only there to
allow the use of "/tivo" rather then ":82" anyway, and
just hit the router
directly...

As was mentioned earlier, I guess it could well be restrictions on port 82
>from
was "supposedly" using an insecure LAN with no restrictions
anyway....

When I get some time, I *do* plan to replace the workaround I'm using above
with ISA server doing reverse proxying of all internal servers so I can
publish everything on port 80, and do away with all this redirection
nonsense! - Time as ever is the enemy here, - today I have to build a deck
for instance, so I'm not going to fix it any time soon!

Paul G.

_________________________________________________________________
Express yourself with cool emoticons http://www.msn.co.uk/messenger



Home | Main Index | Thread Index

Comments to the Webmaster are always welcomed, please use this contact form . Note that as this site is a mailing list archive, the Webmaster has no control over the contents of the messages. Comments about message content should be directed to the relevant mailing list.