Sharing Ceton InfiniTV Tuners with Client HTPC Systems

Nov 05 2010

Update

Please see our new guide for the official Ceton Network Tuner Wizard which makes the procedure outlined in this guide much simpler and virtually fool-proof.

ceton-network-static.jpg

We have good news, and we have some bad news. The good news is that Ceton has graciously allowed MissingRemote.com to publish a guide to Tuner Sharing with the Ceton InfiniTV beta firmware.  The bad news is that it is still in beta. 

What does that mean to you? Unless you are already part of the beta program you will not be able to utilize the HTPC bliss that is shared Digital Cable tuners. Before anyone starts scouring the Internet for the beta firmware, your InfiniTV serial numbers needs to be registered as part of the beta program for the firmware to install, don’t waste your time.

Assuming the bad news has not completely discouraged you, read on to see what we have in store.

Before I go any further it is important to note that this is a beta firmware.  Not everything will work perfectly and some features may be added or removed before it is released to the public.  Also note that there is no way to revert back to an older firmware so proceed at your own risk.  The beta firmware has worked very well for me but if you are not willing to accept some potential missed recordings or an occasional reboot, do yourself a favor and wait for the production firmware. MissingRemote.com is not responsible for any damage done by this guide to your beloved HTPC...sorry!

For the entirety of the guide I am going under the assumption that you already have the beta firmware installed and have rebooted.  I will make every effort to note areas that I believe will differ from the final firmware and feature set.

Let's get started. The first portion of the guide will focus on the PC with the InfiniTV physically installed in it--I will refer to it as the Host PC.  The second portion will walk you through any steps needed on Client HTPCs for Media Center to discover and use the InfiniTV. 

Network bridging steps on the Host PC

  1. Open Device Manager and go to the Network Adapters section. You will see your Ceton InfiniTV there. Right click it and select properties.

  2. Update: This step is may not be needed depending on the firmware.

    Go to the "Advanced" tab and select "Support Bridging." On the right side select "Yes" in the drop-down menu and hit OK.

    hostpc-enabled-bridging.jpg

  3. Open the Ceton InfiniTV4 device webpage.  The default IP address is http://192.168.200.1/ but you can also access it under Network in Windows Explorer.

    hostpc-device-webpage.jpg

  4. Under the System tab there is a next section under the MAC Address, is a hyperlink called "Network Settings." 

    ceton-network-setup.jpg

    Clicking the hyperlink will take you to http://192.168.200.1/Services/NetworkSetup.html

  5. By default the InfiniTV will be setup as a DHCP Server.  You will need to uncheck "Default IP Settings (DHCP Server)" for network bridging to work.

  6. You now have to choose between static IP address or enabling the DHCP Client.  Either will work however, I highly suggest static IP address.  Windows 7 does a great job of handling network discovery but why risk network discovery issues or delayed DHCP responses preventing a recording?

    ceton-network-static.jpg

    Note: Unlike Windows the Netmask (aka Subnet Mask) will not automatically update to the appropiate value.  Most users will need to use 255.255.255.0.  I am a 10-net fan myself.

    Please ensure you assign an unused IP address in your network subnet.  I'll add instructions soon but the easiest thing to do is: 1- Enable DHCP Client; 2- See what IP address was provided; 3- Setup a static IP address using the address used.  Most home users will have an IP address in the 192.168.1.x-192.168.1.255 range.

  7. Click the "Set Network" button. 

    Note: You will lose connectivity to the InfiniTV device webpage and tuners until the rest of the bridging steps are completed.

  8. Go to Start and type in "View Network Connections" to show your network adapters. You should see a "Ceton InfiniTV Network Device" along with your main network device.

  9. Highlight the Ceton InfiniTV Network Device and your primary network card interface, Right Click and select "Bridge Connections."

    network-connections.jpg

    Note: During the bridging process you will lose network connectivity.  If you are connected over Remote Desktop you may no longer be able to connect as the resulting network bridge will have a new IP address.

  10. The result will be a new device called a "Network Bridge."  That is your PC's primary connection to your network now.  As above, I highly recommend setting up a static IP address on your Network Bridge.  What I don't lke about the Windows Network Bridge implementation is that Windows will generate a dynamic MAC Address for it.  This prevents us from using Static DHCP to assign a reserved IP address from the DHCP Server.  If you need help configuring a static IP address please let us know in the comments and I'll help out.

  11. To confirm your Ceton InfiniTV is working properly as a bridged device try accessing the InfiniTV device webpage as shown above in step #3.  The device webpage should be available from any compter on your network.

  12. That completes the Host PC portion of the network bridging setup.

    Note: You will need to run the Client HTPC portion of the setup found below on the Host PC if it will be used as an HTPC. It is not required if you do not plan to use the Host PC as a HTPC.

Steps on the Media Center Client HTPC to find and configure the networked tuners

  1. Download and install "Mikinho's InfiniTV Network Tuner Config."  You will be able to download the setup from the comments below.

    Note: You you will need to be logged in as a registered user to download the attachment.  Please do not redistribute the tool without my consent.  It should also be considered a beta product.

  2. Once installed run the "InfiniTV Network Tuner Config" via your start menu.  The tool requires administrative rights so if you have UAC enabled (everyone should) you will be prompted to allow the tool to run.  If it is your first time running you will also need to the tool access through the firewall.

    network-disabled.jpg

  3. The first thing you will need to do is enable your primary network adapter under the Network Cards tab so Media Center will know to use it for OCUR network tuner discovery.

    network-enabled.jpg

     

  4. Select "Apply" and proceed to the Tuners tab.

    If this is your first time running the tool or you have added or removed an InfiniTV continue on, otherwise skip to step #7.   

  5. Select "OCUR Unregister."  This will take approximately 30 seconds.

    tuners-not-discovered.jpg

  6. Select "OCUR Discovery."  Again the process should take approximately 30 seconds.

    tuners-discovered.jpg

    After that complets you should see the discovered status from each tuner now set to "Yes"

  7. Enable each tuner you want made available to Media Center.  I highly suggest assigning specific tuners per Client HTPC and excluding those from the Host PC.

    tuners-enabled.jpg

  8. Select "OK" and launch Windows Media Center.

  9. You will need to setup the InfiniTV4 the same as your would on the Host PC. This means running (and passing) the Digital Cable Advisor, installing PlayReady, and running through the CableCARD activation screens. If you have previously activated your CableCARD on the Host PC you will NOT need to do it again.

  10. When you run through the Media Center setup you should only see the tuners you enabled in step #7.

    media-center-06.jpg

     

And that is it! Enjoy your network shared InfiniTV tuner. The tool takes care of the firewall exclusions, network interface setting and OCUR discovery tasks.

Also note that the current implementation is not a shared tuner pool. If a Client HTPC attempts to use a tuner from the Host PC pool you will disconnect the tuner from the Host PC and possibly mark it as inactive in the Host PC tuner pool. A future firmware may change this behavior. For now, I highly recommend assigning tuners to a single Client HTPC.

Please leave any comments, questions or feedback on this guide below.

Special thanks to Ceton for involving us in the beta program, and Ylian Saint-Hilaire and Intel for the Developer Tools for UPnP™ Technologies. Makes UPnP development from C# painless.

Comments

Thanks for all the info here. I have read this thread twice so far but I still have 2 issues which may be really only one. Everything went fine until I tried to disable a tuner for remote use. It would say it was saved but if I go back in all 4 tuners show enabled. So obviously the local host sees all 4 in MC. I saw this problem mentioned earlier and there was mention of a fix on the way but I did not see it.

My other issue is the HW rev upgrade will not take. I have tried twice and both times it goes thru the motions of erasing and writing and says it is completed. Then asks for a reboot but when I check it is still at 4336 and not 4374. Maybe the hw upgradewould fix my tuner issue?

Any ideas?

FW is 1.0.2.8

hw is 4336

driver pkg is 1.0.1.21-20110114

diag ver is 1.2.0.0

kernel is 1.0.1.21

tuner cfg ver is 1.0.3961.20864

When doing hardware revisions you need to power down, not reboot.  I leave it off for a minute and then start the computer.

Thanks, that worked for hw version update but I still have the problem of not being able to disable a tuner. Everything is working fine on the local host but there is no tuner available for a remote host. Here are all my levels:

FW is 1.0.2.8

hw is 4374

driver pkg is 1.1.0.3-20110208

diag ver is 1.3.0.9

kernel is 1.0.1.23

tuner cfg ver is 1.0.3961.20864

1st;  Upgrade to the latest HW version 4790. (remember to completely power off the computer for atleast 1 min for it to take effect)

2nd;  Upgrade to the latest FW 1.0.2.9

3rd;  Run Mike's firewall script on both the host and remote PC, or disable your firewall for private networks only on both PCs.

4th;  On the host PC, Go through the TV signal set up in MC again and disable or de-select the tuner you want to use on the remote PC, complete the TV signal setup and reboot.

5th;  Using Mike's configuration tool, on the remote PC, unregister any OCUR tuners, disable your NIC and reboot.  Then restart Mike's configuration tool, re-enable your NIC, reboot.  Start the config tool again and register any OCUR tuners, and enable all of them, reboot.  Go through your TV signal setup in MC and only select the tuner you want to use on your remote PC, complete the TV signal setup. 

 

Hope this helps.

Mikinho,

Could you do a quick post on how I can get this working on a virtual windows 7 ultimate copy.  I can get the bridging working and all that based on your other instructions, but how do I activate cablecard?

Thanks!

Mark

See http://www.missingremote.com/guide/override-digital-cable-advisor-windows-media-center-7 as your first step to pass DCA.

From there you just use the tool as normal

Awesome!  Can't believe I missed that post.

Hey Guys.....I followed the guide and I am able to share the tuners across multiple computers.  However when I tune into some channels on the client PC I am getting a "Activation Required" message.  I tried to activate the cable card through the Setup-->Tv Signal however it says my computer is not digital cable ready.  Anybody have this issue?  I have CableVision and my host computer does have Tunning Adapters.  Would the client computer need a TA as well?   

Opps I missed the post just before mine.  I think I will try disabling that first. Embarassed

We have four computers, one of which is a server/client and the other three clients.  It seems that any time the server/client is restarted, the other clients loose their connection with the infintv and we get an error stating that there are no tuners available to handle this request.  The server still functions properly Restarting the client restores functionality perfectly, but it would be great to find a work around.

Hardware 4790

Firmware 1.0.2.8

Driver: 1.1.0.3-20110208

I have noticed that if my clients are on when I restart my server, what you are describing will happen.  If I have my clients off, or in sleep mode, and start them up after the server is rebooted, then all is fine.

Any thoughts as to why this is happening?  or what we can do to prevent it?  It's understandable for a beta product, but at some point I believe that this will be a commercial solution.

Hey Mikinho,

I am trying to get this going in a virtual environment.  I've got the card installed on the server and up to date.  Firmware 1.0.3.1 and Hardware 4790.  I've created an internal network connection (Ceton Net) and bridged that with the InfiniTV.  I can access the card at it's new static IP address on the server, but nothing on the virtual machine.  I've added Ceton Net to the virtual machine.  If I try to browse to the webpage it can't be found and if I use your tool it can't find the tuners on the virtual machine.  Can I use an internal network connection, or do I have to bridge with one of my physical NIC's?  Any help you can provide would be great!

Thanks,
Mark

I'm using a dedciated physical NIC at the moment since I'm splitting the tuners among the virtual HTPC and bedroom HTPCs.  When my kids are done w/ the TV I'll remove and test.

I believe I had it working with an internal virtual NIC as well but that it took a little bit of a work to get it working properly.

Great! Thanks!

I changed my virtual HTPC to an internal virtual network card and no issues.

What is your network setup like?

On my virtual I now have two network cards configured:

1- External (for Windows Updates and RDP)

2- Internal (Bridged to the InfiniTV)

On the Hyper-V host, ("SERVER"), I have the below IPv4 configuration settings:

External

IP Address: 10.0.0.10

Subnet: 255.0.0.0

Default Gateway: 10.0.0.1

Internal

IP Address: 10.1.0.10

Subnet: 255.0.0.0

Default Gateway: <Blank>

On the Hyper-V virtual, ("HTPC-V"), I have the below IPv4 configuration settings:

External

IP Address: 10.0.0.25

Subnet: 255.0.0.0

Default Gateway: 10.0.0.1

 

Internal

IP Address: 10.1.0.25

Subnet: 255.0.0.0

Default Gateway: <Blank>

On the InfiniTV, I have the below IPv4 configuration settings:

IP Address: 10.1.0.80

Subnet: 255.0.0.0

Hope this helps.

 

Ok here's what I have

On the Hyper - V Host (SERVER)

I have the following

External (No IP Settings shown here as it is not shared with the server.  It's dedicated to the virtual machine)

Internal (No IP Settings shown here as it is bridged with the Ceton Card)

Ceton (No IP Settings shown here as it is bridged with the internal network)

         In the Ceton network settings I've given the card an IP of 192.168.0.165

Bridge IP 192.168.0.166 Subnet 255.255.255.0

On the Virtual Machine

External IP 192.168.0.178 Subnet 255.255.255.0 Default Gateway 192.168.0.1

Internal IP 169.254.8.249 Subnet 255.255.0.0

This was the problem

I changed it to a valid IP and subnet, and the tuners were immediately found.  Thanks for posting up your settings.  That really helped!!

 

On another note, do you use any Xbox 360 extenders connected to that virtual machine.  I have two connected to mine and after about 5 minutes of playback I get network issues which don't go away.  I am running a gig network throughout so I wouldn't expect any issues.  I've dedicated an Intel Network Card for this virtual machine, given it 4 virtual processors, 4096 mb ram starting.  I've tried playing files direct from the virtual hard drive, from the server, and from a virtual homeserver.  Also, no problems with livetv thus far only recordedtv.  Any suggested network adapter changes to help this issue?

 

I currently do NOT have any extenders connected, just 3 bedroom HTPCs for Recorded TV.  I did have 3 extenders connceted at one point though and did not have a problem.  I do have a "nice" network switch though so I don't have to worry about 100\1000 negotiation.

What kind of disk\VHD do you have setup?  If you have a dynamic VHD that doesn't work too well for I\O.  I have my virtual HTPC setup with a dedicated disk but I did use static VHD with success as well.

Well, I am using a static VHD, but maybe I'll give the dedicated disk idea a try.  What's weird is that live tv has no problems, it's only the recorded tv.  I am trying all sorts of different ideas on the network adapter, so far no luck.

What's the ETA for the new configuration tool?  I just got my serial number added to the Beta program & I'm anxious to get started.  I just updated my Firmware to ver. 1.0.3.1 and the Hardware to rev. 4884.  I would like to get up and running ASAP.  I need to reconfigure my tuners now that I've performed the FW and HW updates, and I'm gonna have to do it now so the wife doesn't freak out about the TV not working when she gets up.  Hopefully this won't cause problems.  Thanks for all the help.

It is actively being worked on but no firm ETA that I can give.

I am having trouble finding the download link for the tuner config.  I am signed in and registered.

Per request I've temporarily removed it.  It will be back up as soon as possible.

I just noticed on Ceton's beta support page that the latest HW IMAGE is v4884. Also, (which seems odd, since I check this page weekly) the changelog was updated 01-10-2011. http://www.cetoncorp.com/infinitv/support/betahwupdate.php#changelog

And, Mikinho states the latest in posts 130 and 135.

Anyone install this latest HW IMAGE without issue yet?

Thanks

I'm not sure what is up with the date on the page, but 4884 is the latest hardware image.  I think it came out last Thursday or Friday.  I installed it early Saturday morning and it is working fine for me.

Ok, thanks. HW IAMGE v4790 has been posted on their beta page for 2 months.

I'll give v4884 a go. Maybe this will finally go publicWink

I was under the impression that a public firmware release required re-certification from CableLABS and that was the real hold-up.  Am I wrong on this?

I just got my card, woo hoo.  I originally ordered it last April.

I got client / server working with the public release of driver (1.1.0.6-20110307) and hardware (4790).  I kept on reading about the necessity of Beta driver / hardware.  Is this true?  What kind of issues would I run into if I use public drivers for client / server setup?

I've been running this setup for 2 days, no issues so far.  But curious of what others have found.

Some beta drivers will inadvertantly cause problems, they are typically fixed quickly but "testing" on a primary HTPC can definitely lower your SAF.

My recommendation is, if it works without issue stick to that firmware/driver until you see a formal announcement Smile

Mikinho,

Is there an ETA (that you can say publicly) of when we can see a formal announcement?

Also, when can we expect your tuner sharing application to be re-posted? I (like many others) are planning on getting thier SB builds ordered. I'm replacing my 360 in the bedroom. This feature is vital to my HTPC bliss & more importantly WAF. Laughing

Thanks again.

I don't have an ETA that I can provide or even know.  I expect it to be very soon though and before you get your Sandy Bridge board fully setup Smile

mikinho wrote:

I don't have an ETA that I can provide or even know.  I expect it to be very soon though and before you get your Sandy Bridge board fully setup Smile

Ok, thanks. I just want to avoid:

Wife: "What do you mean I can't watch live TV on this new fancy HTPC that you just built - yet." Foot in mouth

Me: "Ah, well, ah I dunno honey - but soon."Cry

Thanks again.

Worst case if it isn't available give me a call and I'll walk you through it manually.  The issue with doing it manually is there is so much potential to cause issues since there is a LOT of variations in network equipment and knowledge level.

Thanks Michael, I just may take you up on that.

Now back to newegg...

Thanks.  The public driver is not stable perhaps for bridging purposes.  When I came home today the tuner had froze.  I couldn't ping it and had to reinstall the driver.

Hello,

Sorry if this question is a bit stupid, but I can't find a way to get the beta firmware. Is there a page to sign up for the beta firmware?

Also is your application absolutely needed to split the tuners?

My info: 

Firmware: 1.0.2.2

Hardware:4790

Email their tech support and ask to be included in their Beta test program.

phoneguyinpgh wrote:

Email their tech support and ask to be included in their Beta test program.

 

Cool thanks!

 

So...any ETA when that tuner sharing utility may be re-posted? Smile

Can this be done manually?  I have my card set up and can't get the utility but I would love to try this.

I follow the steps in the tutorial and get my network connection bridged.  It can be seen on PCs throughout the network but I can't add it to WMC on the client.  Also, after I bridge on the host PC, WMC can see the tuners but I can't get them to work. 

I would love to set this up in a server.  I tried setting it up in a WHS Vail environment.  I can't change the Network setting there though for some reason.  I hope that this can be made to work.  I would like to have the Ceton in the Server with the tuning adpaters out of the way and divide the tuners between two PCs.  Better yet would be to have the tuners pooled but I understand that there are issues with that right now.

lawguy wrote:

Can this be done manually?  I have my card set up and can't get the utility but I would love to try this.

I follow the steps in the tutorial and get my network connection bridged.  It can be seen on PCs throughout the network but I can't add it to WMC on the client.  Also, after I bridge on the host PC, WMC can see the tuners but I can't get them to work. 

I would love to set this up in a server.  I tried setting it up in a WHS Vail environment.  I can't change the Network setting there though for some reason.  I hope that this can be made to work.  I would like to have the Ceton in the Server with the tuning adpaters out of the way and divide the tuners between two PCs.  Better yet would be to have the tuners pooled but I understand that there are issues with that right now.

 

I got the same results as you after trying to set this up via the guide, but then WMC won't see the tuner.

I also tried to get onto the beta firmware testing program, but they are not allowing people. Said to check back in 10 days, but probably won't for two weeks.

 

So both the firmware and utility are not obtainable. 

I was able to upgrade to the beta firmware without being part of the beta program.  I just downloaded the beta firmware and installed it. 

I don't know if anyone plans to put the card in a server.  When I tried putting it in a Vail server, I could not change the network settings at all.  The boxes listing IP and subnet were blank.  I had no issue installing the card or the drivers though.  I hope that this will work with Vail. 

I ran an InfiniTV on a Vail box for several weeks for testing.  It works w/o issue.

Sounds like you still have Internet Explorer Ehnached Security Configuration enabled, which is what I recommend for a server product but you'll need to add the InfiniTV diagnostics webpage to the Trusted sites security zone.

Edit: On Vail or any server product it is very important to use a stable network card and corresponding drivers.  Windows Server product base has more aggressive networking settings by default and on lower quality network cards that can easily lead to poor network performance.  With the InfiniTV poor network performances corresponds to low signal warnings and pixelation.

mikinho wrote:

I ran an InfiniTV on a Vail box for several weeks for testing.  It works w/o issue.

Sounds like you still have Internet Explorer Ehnached Security Configuration enabled, which is what I recommend for a server product but you'll need to add the InfiniTV diagnostics webpage to the Trusted sites security zone.

Edit: On Vail or any server product it is very important to use a stable network card and corresponding drivers.  Windows Server product base has more aggressive networking settings by default and on lower quality network cards that can easily lead to poor network performance.  With the InfiniTV poor network performances corresponds to low signal warnings and pixelation.

 

Great.  Thanks. 

It is all coming together, assuming I can get sharing to work after I get the sharing utility. 

I put my whole home network together around a year ago assuming that when the Ceton came out that bridging would not be an issue.  Then, it became an issue and the Ceton cards were backordered for so long.

Here I am a year later.  I have the Ceton and all my connections are waiting.    So close . . .

mikinho wrote:

Sounds like you still have Internet Explorer Ehnached Security Configuration enabled, which is what I recommend for a server product but you'll need to add the InfiniTV diagnostics webpage to the Trusted sites security zone.

 

This worked.  I can now change network settings.  Thanks.

Glad I could help.  And thanks for following up with the outcome, I appreciate that.

One additional question.  As things now stand, it seems best to have specific tuners dedicated to specific PCs.  Will it eventually be possible to have a bank of tuners from which all the PCS draw with WMC resolving conflicts among them?  This, in my opinion, is the ideal situation. 

lawguy wrote:

One additional question.  As things now stand, it seems best to have specific tuners dedicated to specific PCs.  Will it eventually be possible to have a bank of tuners from which all the PCS draw with WMC resolving conflicts among them?  This, in my opinion, is the ideal situation. 

HTPC nirvana, also know as softsled (vapor ware)

http://thegreenbutton.com/forums/t/84313.aspx?PageIndex=1

and

http://www.missingremote.com/blog/why-softsled-shall-always-remain-myth

 

 

st3lvio wrote:

lawguy wrote:

One additional question.  As things now stand, it seems best to have specific tuners dedicated to specific PCs.  Will it eventually be possible to have a bank of tuners from which all the PCS draw with WMC resolving conflicts among them?  This, in my opinion, is the ideal situation. 

HTPC nirvana, also know as softsled (vapor ware)

http://thegreenbutton.com/forums/t/84313.aspx?PageIndex=1

and

http://www.missingremote.com/blog/why-softsled-shall-always-remain-myth

 

 

 

I think I would be happy one step short of softsled.  I could do without the shared program guide.  I would be happy if WMC just knew when a tuner was being used by another PC so it didn't disrupt an ongoing recording. 

Four tuners shared by several PCs go further than strictly allocating those four tuners among the PCs.  It would be rare for me to ever have more than four tuners going at one time, but I plan to use 3 PCs.  At least one of those PCs will not be used at any given time.  So anything that I allocate to that PC is wasted. 

Quote:

 

I think I would be happy one step short of softsled.  I could do without the shared program guide.  I would be happy if WMC just knew when a tuner was being used by another PC so it didn't disrupt an ongoing recording. 

Four tuners shared by several PCs go further than strictly allocating those four tuners among the PCs.  It would be rare for me to ever have more than four tuners going at one time, but I plan to use 3 PCs.  At least one of those PCs will not be used at any given time.  So anything that I allocate to that PC is wasted. 

 

 

I second that.  It would be a nice feature to have, each HTPC would just pick the next available spare.  I would think, however, that it would have to be some sort of update to WMC. 

Recording Broker

http://babgvant.com/files/folders/recbrocker/entry19690.aspx

Although babgvant has gone to sageTV, he still continues to support WMC. Laughing

I'd be curious to hear if other users have used this app.

Comment viewing options

Select your preferred way to display the comments and click "Save settings" to activate your changes.
Website design by Yammm Software
Powered by Drupal