DHCP, Dyndns.org and SageTv Client Connection

[yeswork]

I have searched the SageTv forums but can't seem to find the answer to this question -

Can the SageTv client connect to a SageTv server by using a name (not explicit ip address) that is assigned to an IP address not on the local subnet by DHCP if the SageTv server has a domain name assigned via a reverse DNS service?

What works:

SageTv 4.1 server machine on local private IP network - 192.168.2.105

SageTv client 4.1 machine on same local private IP network - connects and works fine when given 192.168.2.105 explicitly.

As background:

SageTv server machine with local IP of 192.168.2.105 and is connected to the internet via a router.

The SageTv server machine has a public domain name assigned/published Using the dyndns.org service - machinename.dyndns.org resolves to 207.xxx.xxx.xxx

SageTv server machine also runs a "regular" web server (not sage web server) on port 8000. Local router has IP forwarding enabled for port 8000.

SageTv client machine using MS Internet Explorer, can connect OK to the "regular" web server running on the SageTv server. This works whether the connection is initiated via explicit IP or via DNS lookup - all of the following work - http://machinename.dyndns.org:8000 or http://207.xxx.xxx.xxx:8000 or http://192.16.2.105:8000. This makes me believe ip resolution and port forwarding are OK.

Now the local router has IP forwarding enabled for 8000, 7760, 42024 and 7818 for passing SageTv traffic.


What does not work:


SageTv does not connect to machinename.dyndns.org, or 207.xxx.xxx.xxx (but does connect to 192.168.2.105) The error message is 17 network error.

however

telnet from SageTv client to sagetv server at 192.168.2.105:42024, or 207.xxx.xxx.xxx:42024 or machinename.dyndns.org:42024 all connect (no errors). This also makes me believe that port forwarding and firewall setting are OK


I'd like to be able to have the SageTv client connect to the SageTv server at machinename.dnydns.org automatically but it does not work.


Any suggestions?

Thanks

[yeswork]

So is SageTv subnet restricted?

[mayamaniac]

I know it works using computer name, or most of the time it works if you just type in the computer name, might help if you enable NetBios protocal also in addition to TCP/IP.

In SageTV 4, it should automatically detect the server and list it in the IP box. Again, this works most of the time, sometime it doesn't and you have to type in an IP. But in Detailed Setup, under General, there's an option to Auto Connect to Server. I use that so I never have to deal with this issue.

As for why the dyndns.org doesn't work, this is because a port isn't specified. To make it work, you could enable DMZ mode in the router for the server machine. This will forward all ports to that machine. Otherwise, you have to ask SageTV gurus for list of ports SageTV to use and configure your router to forward those to the server.

[yeswork]

Thanks for the reply mayamaniac.


I remain confused. Yes my client "automagically" find the server - on the local private subnet.

I am looking to connect over a router. I have opened the ports 7760, 42024 and 7818 (as both TCP and UDP) and gotten an assigned name from a DNS server for the IP of the server machine.

While I can connect to the SageTv server machine via other ports via DNS lookup and can telnet to the SageTv ports via DNS lookup, I can't seem to connect via SageTv client.

Since I can see/connect to the SageTv server on other ports using DNS lookup; I know http, ftp etc work to/from that machine. I am beginning to wonder if SageTv client is restricted to looking at the local subnet for a server.

Any insights?

[flavius]

Just curious - why would you want to use the dyndns name inside your network? If it is the obvious, i'd look at something like http://www.orb.com. I don't know if this *restriction* exists, it certainly would make sense, though.

[yeswork]

Thanks flavius. I eventually want to move the SageTv client off the local subnet; just checking to make sure it works locally first (so far by DNS lookup it does not).

Yes, Orb seems to provide a server function for tv over the web. Will it let me view SageTv recordings? I am not sure I want to install yet another suite of software to provide what seems like functionality SageTv could provide.

I find it mysterious why this SageTv "feature" or "restriction" does not seem to be documented anywhere.

If I own a legitimate SageTv server license and SageTv client license, and connect to view my own tv or recordings, I can't see how I would be violating any restrictions by having them communicate over the Internet.

Still confused.

[blade]

Unless you have a very fast upload connection then Sage isn't going to work across the internet anyway due to bandwith limitations.

[mayamaniac]

Yeah, SageTV is not meant to work over the internet. Alternatively, you can try nielm's webserver plugin. In his latest version, it supports access to your SageTV files for playback through the browser.

[yeswork]

Blade, thanks for your thoughts.

I think I might have enough bandwidth to make it useable. Currently I can connnect from SageTv Client to SageTv Server over wireless 802.11b at the edge of the wifi range; ever since upgrading to Sage 4.1 I get smooth audio and video. Using NetSat Live I see bandwidth usage at about 550KB.

My upstream connection to the Internet is rated at 7MB - I think I really see about 1MB. Seems fast enough on the outflow.

[gplasky]

Blade, thanks for your thoughts.

I think I might have enough bandwidth to make it useable. Currently I can connnect from SageTv Client to SageTv Server over wireless 802.11b at the edge of the wifi range; ever since upgrading to Sage 4.1 I get smooth audio and video. Using NetSat Live I see bandwidth usage at about 550KB.

My upstream connection to the Internet is rated at 7MB - I think I really see about 1MB. Seems fast enough on the outflow.
You'll find out you do not have enough bandwidth. Unless your Internet connection is at LAN speed it will not work to your satisfaction. It has been tried by many individuals before. If you think you only see about 1MB to the Internet that is a lot less than your wireless connection. Search the forum. Best option so far if you HAVE to watch your recordings over the Internet is ORB. If I have to take them with me they are either copied to a laptop or burned to DVD.

Gerry

[yeswork]

Setting the bandwidth issues aside; I am still confused as to why I can't point to my SageTv server via DNS.

Getting back to the bandwidth issues; how did "people" test Sage-over-Internet if the SageServer and SageClient had to be on the same subnet? Seems to me it would be a local test, not Internet test.

For me, it now seems like just too much work to actually do something that conceptually seemed simple to do.

Slingbox - here I come.

[gplasky]

Who said anybody tested Sage over the Internet? Certainly not streaming the videos. I use Nielm's webserver and can get to my Sage server using DynDNS. I can schedule my recordings or see wht's recording. I don't try to play the videos or the music over the Internet. Your trying to use the wrong tool for the wrong purpose. Slingbox or Orb is what you're looking for if you're streaming your recordings over the Internet.

Gerry

[yeswork]

I foolishly installed ORB.

Orb works but now I get no sound when I watch live TV in SageTv.

I do hear sound from previously recorded SageTv recordings.

Settings in SageTv are default for all audio and video.

Any suggestions?

Conflicts like this are the reason I was trying to "standardize" on using SageTv.

[heffe2001]

Setting the bandwidth issues aside; I am still confused as to why I can't point to my SageTv server via DNS.

Getting back to the bandwidth issues; how did "people" test Sage-over-Internet if the SageServer and SageClient had to be on the same subnet? Seems to me it would be a local test, not Internet test.

For me, it now seems like just too much work to actually do something that conceptually seemed simple to do.

Slingbox - here I come.

Sage isn't subnet restricted, I connect to my sage server all the time with client on my laptop while I'm at work (different subnets, connected via VPN). The problem you're likely having trying connect internally with the outside DNS name is that 99% of all routers/firewalls won't allow you to reverse a connection like that through them (go from a nat'ed PC connection, to the outside interface, back inside to another nat'ed PC). And I can about bet you're using more bandwidth than you have on your outbound, unless you're compressing your shows with divx/xvid to a very low bitrate. I basically have a full T1 between 2 of my locations (other location has a couple channels split out for voice, rest for data), and can't play video compressed as xvid from location to location..