TiVo Community Forums Archives - TivoWeb Through a Router

TiVoCommunity.com
(c)opyright 1995-2005 All rights reserved
indexcheckTC
This area is a static history of posts in the TiVo Community Forum Archive.
This archive history was made for the simple indexing of search sites like Google.

Pages:1

TivoWeb Through a Router
(Click here to view the original thread with full colors/images)

Posted by: fbnts

Hi, I have been using TivoWeb for many months now hastle free. however I had it set up through my server and using Orenosp Software Router which worked perfect. We now have a broadband router and i have set the port forwarding up but it refuses to work.

I am using an external port of 444 and mapping it to 192.168.0.200 port 80 which works perfect on my internal network.
All other port forwarding works - ie external webmail running on our Win 2000 Domain Controller and incoming VPN Connections.

Do i require any other settings on the tivo?

thanx

Tom

Posted by: devnull

You might try the following to help isolate where the problem is:
1. set tivoweb to port 444 to see if there's a mapping problem at your router
2. Point 444 at your domain controller to see if it's actually coming through the router
3. Try a different port. 444 is actually used for something:
snpp 444/tcp # Simple Network Paging Protocol
snpp 444/udp # Simple Network Paging Protocol

Your ISP might block it.

gary

Posted by: fbnts

Thanks for the reply. I have tried them, all other services work fine - we have a pop server, web server and VPN Services working fine and i used to use port 444 using the software router. So i cant really understand why it doesn't route through the router.

Does tivoweb only use TCP or do i also need to forward UDP?

Thanx

Tom

Posted by: bbocaner

does your tivo have a default gateway?

Posted by: fbnts

yes - its set to 192.168.0.254 (The router) i checked that because i forgot to change it over from 192.168.0.1 when i got the router and then found that it ran out of Guide Data

Posted by: cojonesdetoro

Tivoweb uses TCP only. Do you have telnet set up? Try to foward telnet and see if it behaves the same way. If you have a linux machine, then tcpdump(or other packet scanner) would be helpful.

BTW, There's a security problem with what you're trying to do. If you don't care, so be it, but I figured I'd warn you anyway.