SageTV Community  

Go Back   SageTV Community > Hardware Support > Hardware Support
Forum Rules FAQs Community Downloads Today's Posts Search

Notices

Hardware Support Discussions related to using various hardware setups with SageTV products. Anything relating to capture cards, remotes, infrared receivers/transmitters, system compatibility or other hardware related problems or suggestions should be posted here.

Reply
 
Thread Tools Search this Thread Display Modes
  #41  
Old 03-13-2014, 03:30 PM
Tiki's Avatar
Tiki Tiki is offline
Sage Icon
 
Join Date: Feb 2005
Location: Southwest Florida, USA
Posts: 2,009
Quote:
Originally Posted by Ender View Post
In the screenshot labeled Adv-Diag-NetworkStats-Summary, is the wan section a link? If so, click on it to see what you are working with. Then possibly someone could come up with a solution for you.

The next thing I would try, is to put the modem in bridged mode, then go on the TP-Link router, and go to the page that the wan connection type screenshot came from, and try the auto detect. It cannot hurt.
Right - at the top of the page, right under the tab that says "advanced" in the blue area are a bunch of choices that look like sub-menus "Version, Diagnostics, LAN, WAN, Restart". Try clicking on the "WAN" sub-menu.
__________________
Server: Ryzen 2400G with integrated graphics, ASRock X470 Taichi Motherboard, HDMI output to Vizio 1080p LCD, Win10-64Bit (Professional), 16GB RAM
Capture Devices (7 tuners): Colossus (x1), HDHR Prime (x2)
,USBUIRT (multi-zone)
Source:
Comcast/Xfinity X1 Cable
Primary Client: Server Other Clients: (1) HD200, (1) HD300
Retired Equipment: MediaMVP, PVR150 (x2), PVR150MCE,
HDHR, HVR-2250, HD-PVR
Reply With Quote
  #42  
Old 03-13-2014, 06:08 PM
firenice firenice is offline
Sage Advanced User
 
Join Date: Jul 2010
Location: Houston, Texas
Posts: 139
pj

Why don't you take the tp-link out of the equation temporarily. See if your new modem/router will let you access the way you want. If if does then add your tp-link back in as a wireless access point only. Move the cables from the tp-link to the empty ports on the new modem/router or switch as required. The empty ports on the modem will act as a switch and or connect one cable from the new router to the switch. Sounds like you have enough ports to handle it. If it works the wAy you want the reinstall the tp-link and disable it's dhcp capabities.
Reply With Quote
  #43  
Old 03-14-2014, 03:04 PM
pjpjpjpj pjpjpjpj is offline
Sage Icon
 
Join Date: Feb 2008
Posts: 2,164
Quote:
Originally Posted by firenice View Post
pj

Why don't you take the tp-link out of the equation temporarily. See if your new modem/router will let you access the way you want. If if does then add your tp-link back in as a wireless access point only. Move the cables from the tp-link to the empty ports on the new modem/router or switch as required. The empty ports on the modem will act as a switch and or connect one cable from the new router to the switch. Sounds like you have enough ports to handle it. If it works the wAy you want the reinstall the tp-link and disable it's dhcp capabities.
That was my first thought but the stupid Westell is only 10/100. The wireless only has b and g, too. If it were gigabit and wireless n, I'd remove the TP-Link entirely.

I grabbed a bunch of screenshots of the WAN stuff as requested above but last night I wasn't able to get on this forum because the "server was too busy" (I was hoping the board was blowing up because Google had announced a Sage-compatible extender device, but alas, no such luck). I will try to post later this evening when I get home.
__________________
Server: AMD Athlon II x4 635 2.9GHz, 8 Gb RAM, Win 10 x64, Java 8, Gigabit network
Drives: Several TB of internal SATA and external USB drives, no NAS or RAID or such...
Software: SageTV v9x64, stock STV with ADM.
Tuners: 4 tuners via (2) HDHomeruns (100% OTA, DIY antennas in the attic).
Clients: Several HD300s, HD200s, even an old HD100, all on wired LAN. Latest firmware for each.
Reply With Quote
  #44  
Old 03-14-2014, 04:29 PM
Fuzzy's Avatar
Fuzzy Fuzzy is offline
SageTVaholic
 
Join Date: Sep 2005
Location: Jurupa Valley, CA
Posts: 9,957
Quote:
Originally Posted by pjpjpjpj View Post
That was my first thought but the stupid Westell is only 10/100. The wireless only has b and g, too. If it were gigabit and wireless n, I'd remove the TP-Link entirely.
I doubt your DSL is > 100Mbps, so it really doesn't matter if it's only 100. You still have you gigabit switch downstream for int in-house networking.
__________________
Buy Fuzzy a beer! (Fuzzy likes beer)

unRAID Server: i7-6700, 32GB RAM, Dual 128GB SSD cache and 13TB pool, with SageTVv9, openDCT, Logitech Media Server and Plex Media Server each in Dockers.
Sources: HRHR Prime with Charter CableCard. HDHR-US for OTA.
Primary Client: HD-300 through XBoxOne in Living Room, Samsung HLT-6189S
Other Clients: Mi Box in Master Bedroom, HD-200 in kids room
Reply With Quote
  #45  
Old 03-14-2014, 06:29 PM
pjpjpjpj pjpjpjpj is offline
Sage Icon
 
Join Date: Feb 2008
Posts: 2,164
Quote:
Originally Posted by Fuzzy View Post
I doubt your DSL is > 100Mbps, so it really doesn't matter if it's only 100. You still have you gigabit switch downstream for int in-house networking.
The cable to the Sage server (which is the bottleneck through which all incoming HD streams from HDHRs and all outgoing streams to extenders must pass) is plugged into the router. If I moved everything to the new Westell (as firenice suggested), everything would be passing through it into that one single 100-Mbps port. It's not about the DSL, it's about the router ports on the unit....
__________________
Server: AMD Athlon II x4 635 2.9GHz, 8 Gb RAM, Win 10 x64, Java 8, Gigabit network
Drives: Several TB of internal SATA and external USB drives, no NAS or RAID or such...
Software: SageTV v9x64, stock STV with ADM.
Tuners: 4 tuners via (2) HDHomeruns (100% OTA, DIY antennas in the attic).
Clients: Several HD300s, HD200s, even an old HD100, all on wired LAN. Latest firmware for each.

Last edited by pjpjpjpj; 03-14-2014 at 06:35 PM.
Reply With Quote
  #46  
Old 03-14-2014, 06:34 PM
firenice firenice is offline
Sage Advanced User
 
Join Date: Jul 2010
Location: Houston, Texas
Posts: 139
Quote:
Originally Posted by pjpjpjpj View Post
That was my first thought but the stupid Westell is only 10/100. The wireless only has b and g, too. If it were gigabit and wireless n, I'd remove the TP-Link entirely.

I grabbed a bunch of screenshots of the WAN stuff as requested above but last night I wasn't able to get on this forum because the "server was too busy" (I was hoping the board was blowing up because Google had announced a Sage-compatible extender device, but alas, no such luck). I will try to post later this evening when I get home.
How many ports does your switch have? The 10/100 vs 1 gig is a about hype. Most of the sage extenders only work on a 10/100 port and the modem will only have a 10/100 for internet also so sage is geared toward the that. The n wireless does improve speed but most wireless devices use less than that to connect. I have a 60mpbs dl on my cable yet my iPad will only utilize about 20 of it. Unless your transferring tons of files between servers you will not use but a fraction of a gig connection.
Reply With Quote
  #47  
Old 03-14-2014, 07:07 PM
pjpjpjpj pjpjpjpj is offline
Sage Icon
 
Join Date: Feb 2008
Posts: 2,164
Screenshots from the "Advanced>WAN" tabs. I included the first one just because I pulled down the WAN tab and grabbed it with the options showing.

I'm hoping someone will tell me that the "WAN detection" screen indicates I don't have PPPoE and therefore don't need a password from the ISP.
Attached Images
File Type: jpg Adv-version data.JPG (52.4 KB, 132 views)
File Type: jpg adv-VCs.JPG (55.6 KB, 132 views)
File Type: jpg adv-WAN detection.JPG (41.3 KB, 129 views)
File Type: jpg adv-WAN-routes.JPG (142.3 KB, 129 views)
__________________
Server: AMD Athlon II x4 635 2.9GHz, 8 Gb RAM, Win 10 x64, Java 8, Gigabit network
Drives: Several TB of internal SATA and external USB drives, no NAS or RAID or such...
Software: SageTV v9x64, stock STV with ADM.
Tuners: 4 tuners via (2) HDHomeruns (100% OTA, DIY antennas in the attic).
Clients: Several HD300s, HD200s, even an old HD100, all on wired LAN. Latest firmware for each.
Reply With Quote
  #48  
Old 03-14-2014, 07:10 PM
pjpjpjpj pjpjpjpj is offline
Sage Icon
 
Join Date: Feb 2008
Posts: 2,164
A couple more screenshots from the TP-Link router page, possibly pertaining to the stuff in the Westell screenshots posted above.
Attached Images
File Type: jpg TP-Link - Status.JPG (70.5 KB, 127 views)
File Type: jpg TP-Link - DHCP Settings.JPG (71.1 KB, 126 views)
__________________
Server: AMD Athlon II x4 635 2.9GHz, 8 Gb RAM, Win 10 x64, Java 8, Gigabit network
Drives: Several TB of internal SATA and external USB drives, no NAS or RAID or such...
Software: SageTV v9x64, stock STV with ADM.
Tuners: 4 tuners via (2) HDHomeruns (100% OTA, DIY antennas in the attic).
Clients: Several HD300s, HD200s, even an old HD100, all on wired LAN. Latest firmware for each.
Reply With Quote
  #49  
Old 03-14-2014, 07:16 PM
pjpjpjpj pjpjpjpj is offline
Sage Icon
 
Join Date: Feb 2008
Posts: 2,164
Regarding the gigabit router issue, there are times when we have 4 HD shows recording and three extenders running with HD content being watched. My system is all OTA and the HD streams being recorded are in the 12-15 Mbps range, so worst-case that's 60 total incoming. If three extenders are watching the same shows, that would put me near, at, or over 100 Mbps. I have a few files that I have downloaded, as well as our home videos from a camcorder, which are 1080p, and those are even more bandwidth when streaming to an extender. Plus it's a future-proofing thing since my 2-year-old will someday be old enough that we might have four extenders running at once.

Before I went all gigabit, I did occasionally see hiccups with watching shows when I had four shows recording at once and several extenders running, so, at the very least, it's worth this hassle to get it fixed once and be done with it.

Plus I'm learning a LOT from y'all!
__________________
Server: AMD Athlon II x4 635 2.9GHz, 8 Gb RAM, Win 10 x64, Java 8, Gigabit network
Drives: Several TB of internal SATA and external USB drives, no NAS or RAID or such...
Software: SageTV v9x64, stock STV with ADM.
Tuners: 4 tuners via (2) HDHomeruns (100% OTA, DIY antennas in the attic).
Clients: Several HD300s, HD200s, even an old HD100, all on wired LAN. Latest firmware for each.
Reply With Quote
  #50  
Old 03-14-2014, 07:50 PM
firenice firenice is offline
Sage Advanced User
 
Join Date: Jul 2010
Location: Houston, Texas
Posts: 139
Quote:
Originally Posted by pjpjpjpj View Post
Regarding the gigabit router issue, there are times when we have 4 HD shows recording and three extenders running with HD content being watched. My system is all OTA and the HD streams being recorded are in the 12-15 Mbps range, so worst-case that's 60 total incoming. If three extenders are watching the same shows, that would put me near, at, or over 100 Mbps. I have a few files that I have downloaded, as well as our home videos from a camcorder, which are 1080p, and those are even more bandwidth when streaming to an extender. Plus it's a future-proofing thing since my 2-year-old will someday be old enough that we might have four extenders running at once.

Before I went all gigabit, I did occasionally see hiccups with watching shows when I had four shows recording at once and several extenders running, so, at the very least, it's worth this hassle to get it fixed once and be done with it.

Plus I'm learning a LOT from y'all!

The 74.215.xxx.xx address looks to be the IP address that would be assign by your ISP. The tp-link router would have the same 192.168.x.x ip as the other equipment on your subnet. When you access the tp-link router what IP address do you use?
Reply With Quote
  #51  
Old 03-14-2014, 09:21 PM
pjpjpjpj pjpjpjpj is offline
Sage Icon
 
Join Date: Feb 2008
Posts: 2,164
The TPLink access is 192.168.1.1. I believe you are correct that my internet IP address is the 74.215.xx.xx one. I have seen that in several instances when I was trying to get this to work before y'all discovered the "two routers fighting" issue.

So what do I do with that?
__________________
Server: AMD Athlon II x4 635 2.9GHz, 8 Gb RAM, Win 10 x64, Java 8, Gigabit network
Drives: Several TB of internal SATA and external USB drives, no NAS or RAID or such...
Software: SageTV v9x64, stock STV with ADM.
Tuners: 4 tuners via (2) HDHomeruns (100% OTA, DIY antennas in the attic).
Clients: Several HD300s, HD200s, even an old HD100, all on wired LAN. Latest firmware for each.
Reply With Quote
  #52  
Old 03-15-2014, 07:52 AM
firenice firenice is offline
Sage Advanced User
 
Join Date: Jul 2010
Location: Houston, Texas
Posts: 139
Quote:
Originally Posted by pjpjpjpj View Post
The TPLink access is 192.168.1.1. I believe you are correct that my internet IP address is the 74.215.xx.xx one. I have seen that in several instances when I was trying to get this to work before y'all discovered the "two routers fighting" issue.

So what do I do with that?
pj

I now know why you don't use a username and password for a ppoe connection. Your connection is a routed IP which means you do not authenicate each time you go to the internet.

First thing you need to do is change the tp-link routers IP address.
Then disable the DHCP service under WAN.
See this: http://www.tp-link.com/en/article/?faqid=417
This will set the tp-link to an access point without DHCP service since the Westell will handle the DHCP.

Be sure not to duplicate an existing IP address. Log on to the Westell and under My Network view the Device Details. This should give you a list of all equipment attached to your network and the IP adresses assigned to them.

By the way most dumb, non-smart, switches are not assigned an IP address. From your screen shot of the adv-WAN above your IP addresses would be ISP IP > 74.215.xx.xx >tp-link 192.168.x.x > Westell 192.168.x.x > local ip 27.0.0.1. IP address 27.0.0.1 is used for local host and may be the computer you used to set up the Westell. I see also that the that a private LAN2 is setup. The Westell is seeing the tp-link as a private network.

Last edited by firenice; 03-15-2014 at 09:07 AM. Reason: One thing
Reply With Quote
  #53  
Old 03-15-2014, 12:34 PM
pjpjpjpj pjpjpjpj is offline
Sage Icon
 
Join Date: Feb 2008
Posts: 2,164
Quote:
Originally Posted by firenice View Post
First thing you need to do is change the tp-link routers IP address.
.... Be sure not to duplicate an existing IP address.
Just curious, why? Does it matter what the address is when when I disable the DHCP? Or, if so, wouldn't it get reassigned?
Quote:
Originally Posted by firenice View Post
Then disable the DHCP service under WAN.
See this: http://www.tp-link.com/en/article/?faqid=417
That's a link to doing stuff with wireless, I assume you are just referencing step 5 that shows where to disable the DHCP?
Quote:
Originally Posted by firenice View Post
This will set the tp-link to an access point without DHCP service since the Westell will handle the DHCP.
Will the TPLink wireless still work even if the router doesn't handle the DHCP?
Quote:
Originally Posted by firenice View Post
Log on to the Westell and under My Network view the Device Details. This should give you a list of all equipment attached to your network and the IP adresses assigned to them.
I'm guessing this will all show up once I've disabled the DHCP on the TPLink? Right now all the devices are listed in the TPLink setup under "DHCP Clients List", but the Westell only shows one device under "Connected devices" (it shows "Ethernet: 1 Devices", which presumably is the TP Link). So, what you are saying is, when I disable the DHCP on the TPLink, all of the devices listed on the TPLink should then show up under "Ethernet" on the Westell? In other words, having the DHCP enabled on the TPLink is what "blocks" any other downstream devices from showing up in the Westell list?
Quote:
Originally Posted by firenice View Post
I see also that the that a private LAN2 is setup. The Westell is seeing the tp-link as a private network.
Is this why (as I guessed above) the Westell only sees one downstream Ethernet device?

Finally, do I need (would it be recommended) to turn off everything on the entire network when I do this? When I disable the DHCP on the TPLink, will the Westell reassign new IP addresses to everything? Or will the devices' existing IP addresses be detected by the Westell?
__________________
Server: AMD Athlon II x4 635 2.9GHz, 8 Gb RAM, Win 10 x64, Java 8, Gigabit network
Drives: Several TB of internal SATA and external USB drives, no NAS or RAID or such...
Software: SageTV v9x64, stock STV with ADM.
Tuners: 4 tuners via (2) HDHomeruns (100% OTA, DIY antennas in the attic).
Clients: Several HD300s, HD200s, even an old HD100, all on wired LAN. Latest firmware for each.
Reply With Quote
  #54  
Old 03-15-2014, 02:07 PM
pjpjpjpj pjpjpjpj is offline
Sage Icon
 
Join Date: Feb 2008
Posts: 2,164
Also - if I am taking the DHCP off the TPLink, should I have the cable fron the Westell running into the WAN or LAN on the TPLink? It currently runs to the WAN. If I take it off the WAN, will the TPLink wireless work or will I be forced to use the slower Westell wireless?
__________________
Server: AMD Athlon II x4 635 2.9GHz, 8 Gb RAM, Win 10 x64, Java 8, Gigabit network
Drives: Several TB of internal SATA and external USB drives, no NAS or RAID or such...
Software: SageTV v9x64, stock STV with ADM.
Tuners: 4 tuners via (2) HDHomeruns (100% OTA, DIY antennas in the attic).
Clients: Several HD300s, HD200s, even an old HD100, all on wired LAN. Latest firmware for each.
Reply With Quote
  #55  
Old 03-15-2014, 03:11 PM
firenice firenice is offline
Sage Advanced User
 
Join Date: Jul 2010
Location: Houston, Texas
Posts: 139
Quote:
Originally Posted by pjpjpjpj View Post
Also - if I am taking the DHCP off the TPLink, should I have the cable fron the Westell running into the WAN or LAN on the TPLink? It currently runs to the WAN. If I take it off the WAN, will the TPLink wireless work or will I be forced to use the slower Westell wireless?
pj

The link I posted was for setting the tp-link up as an wireless access point. The purpose for changing the IP address is to not interfere with the Westell. Most all routers are accessed with the IP of 192.168.1.1. If the Westell's is different then you do not have to change it.

Connect the Westell to a LAN port, not the WAN port, as in step 1. Once you have disabled the DHCP on the tp-link the Westell will take over that duty and assign IP addresses to everything attached. At this point you will not see the private LAN2 listed on the Westell because now everything will be on the main LAN and will show up in the device list.
Reply With Quote
  #56  
Old 03-15-2014, 03:27 PM
SHS's Avatar
SHS SHS is offline
Moderator
 
Join Date: Mar 2003
Location: Vinita, Oklahoma
Posts: 4,589
Here a idea you could always get a 10/100/1000 Ethernet hub and make use of the Uplink on the Westell Router and set the other router a side or see if you can use you own DSL Modem and order used one from ebay or new like a TP-LINK TD-8616 ADSL2 or D-Link DSL-520B or Actiontec GEU003AD3B-01 Modem.
That or ask the phone people to sent you a reg DSL Modem which is a non Combo DSL Modem Router

Last edited by SHS; 03-15-2014 at 06:08 PM.
Reply With Quote
  #57  
Old 03-15-2014, 03:54 PM
SHS's Avatar
SHS SHS is offline
Moderator
 
Join Date: Mar 2003
Location: Vinita, Oklahoma
Posts: 4,589
Quote:
Originally Posted by firenice View Post
pj

The link I posted was for setting the tp-link up as an wireless access point. The purpose for changing the IP address is to not interfere with the Westell. Most all routers are accessed with the IP of 192.168.1.1. If the Westell's is different then you do not have to change it.

Connect the Westell to a LAN port, not the WAN port, as in step 1. Once you have disabled the DHCP on the tp-link the Westell will take over that duty and assign IP addresses to everything attached. At this point you will not see the private LAN2 listed on the Westell because now everything will be on the main LAN and will show up in the device list.
You have it wrong Westell will be need be in a bridge mode in order for the TP-Link Router to become the main Router

If none else pjpjpjpj
Look up westell a90 bridge mode
maybe you find something here
http://www.dslreports.com/forum/r241...7500-rebooting
here
http://mrwhatis.net/a90-750060-07.html
Your Modem/Router
http://www.westell.com/support/versalink/a90-750060-07

Last edited by SHS; 03-15-2014 at 04:02 PM.
Reply With Quote
  #58  
Old 03-15-2014, 04:22 PM
firenice firenice is offline
Sage Advanced User
 
Join Date: Jul 2010
Location: Houston, Texas
Posts: 139
pj

We have gone full circle on this one.

SHS is correct. Even if you disable the DHCP on the tp-link and use it as an wireless access point you will lose the gigabit routing capablities of the tp-link.

The Westell is only 10/100 as well as any routing it would do. The network will only be as fast as it slowest component.

The Westell will have to be brigded, basically making it just a modem, and the tp-link will have to be setup as the router.

Your best bet is to call your ISP and request a modem only. Tell them you have your own router.
Reply With Quote
  #59  
Old 03-16-2014, 06:37 AM
pjpjpjpj pjpjpjpj is offline
Sage Icon
 
Join Date: Feb 2008
Posts: 2,164
So if I have the Westell running the DHCP but there is only one cable from it which runs to the TPLink (the only thing ever passing through that one cable being internet connection), and the Westell is in bridge mode, and throughput to/from the Sage server runs into and out of the TPLink, the Westell still dictates to everything downstream that it must only operate at 10/100? I thought the throughput was determined by the device through which the data stream entered and left ( i.e. the data from an HDHR running through the TPLink, into the cable to my server, would be subject to the TPLink's bandwidth limitation because it didn't have to run through the Westell).
__________________
Server: AMD Athlon II x4 635 2.9GHz, 8 Gb RAM, Win 10 x64, Java 8, Gigabit network
Drives: Several TB of internal SATA and external USB drives, no NAS or RAID or such...
Software: SageTV v9x64, stock STV with ADM.
Tuners: 4 tuners via (2) HDHomeruns (100% OTA, DIY antennas in the attic).
Clients: Several HD300s, HD200s, even an old HD100, all on wired LAN. Latest firmware for each.
Reply With Quote
  #60  
Old 03-16-2014, 07:36 AM
firenice firenice is offline
Sage Advanced User
 
Join Date: Jul 2010
Location: Houston, Texas
Posts: 139
Quote:
Originally Posted by pjpjpjpj View Post
So if I have the Westell running the DHCP but there is only one cable from it which runs to the TPLink (the only thing ever passing through that one cable being internet connection), and the Westell is in bridge mode, and throughput to/from the Sage server runs into and out of the TPLink, the Westell still dictates to everything downstream that it must only operate at 10/100? I thought the throughput was determined by the device through which the data stream entered and left ( i.e. the data from an HDHR running through the TPLink, into the cable to my server, would be subject to the TPLink's bandwidth limitation because it didn't have to run through the Westell).
The Westell would not do any IP routing when bridged. It would just be a modem. The router, DHCP function, routes IP calls between devices. The Westell used as the DHCP provider would require each packet sent go see where to go ultimately using a 10/100 port to do it. The tp-link being the DHCP provider would be using 10/100/1000 as required by the calling device.

An example for this was stated earlier. A Sage extender only has a 10/100 port but when you run 2 at the same time you need 20/200 bandwidth requirement on your router if both are running full speed. I know this is a simplistic way of stating it but with a 10/100/1000 router you get more bandwidth for the route.

While surfing the web or as with some wireless devices bandwidth only comes in to play when more devices have an active connection. Most all modem only devices only require a 10/100 port since the bandwidth would never exceed the actual bandwidth supplied by the ISP. In your case, you know that your LAN requires more bandwidth and the tp-link solved that with your other ISP which had provided a modem only. This is why when setting up a gigabit network all equipment needs to be gigabit capable with the exception of the modem.
Reply With Quote
Reply


Currently Active Users Viewing This Thread: 1 (0 members and 1 guests)
 

Posting Rules
You may not post new threads
You may not post replies
You may not post attachments
You may not edit your posts

BB code is On
Smilies are On
[IMG] code is On
HTML code is Off

Forum Jump

Similar Threads
Thread Thread Starter Forum Replies Last Post
Caller I.D. Modem Steve52 Hardware Support 3 02-19-2012 07:56 PM
Creativev.92 Modem and Caller I.D. Steve52 Hardware Support 5 01-24-2012 12:19 PM
Caller ID modem for voip tawd1992 Hardware Support 11 10-22-2009 06:17 PM
hd200 connected to modem? ttiell SageTV HD Theater - Media Player 8 10-09-2009 12:13 PM
Help with choosing DSL Modem/Router! JUC Hardware Support 3 05-04-2006 10:46 AM


All times are GMT -6. The time now is 11:34 AM.


Powered by vBulletin® Version 3.8.11
Copyright ©2000 - 2023, vBulletin Solutions Inc.
Copyright 2003-2005 SageTV, LLC. All rights reserved.