Set Unknown Network to Private
Disclaimer: This is a fairly worthless utility
Update: Ceton has informed me that the reason the current InfiniTV4 driver sets their network interface to Public is due to a potential tuner discovery issue. Ceton is looking into how to safely change it to private.
I’m going to keep the tool available to allow users to reset the InfiniTV4 interface back to public. I’m going to keep mine at Private to do some additional troubleshooting.
TheGreenButton member RandomRage asked whether it was normal for the Ceton InfiniTV4 to be put into Public network category.
While it is normal, it did bother me so I wrote a quick utility to change the network category to Private.
I’m hoping it is fairly self-explanatory. Download the tool from the attachment below (you’ll need to be logged in to see attachments). Extract and run.
Change the Category via the drop down and hit Apply. The tool also allows you to rename the Network Name but only for identified networks. I’ll enable renaming the “Unidentified Network” soon but it is a bit of a hack to change that so I wanted to further test. This will be a moot point when the Network Sharing Ceton InfiniTV4 firmware is released since the networks will be bridged anyways.
Quote:Update: Ceton has
[quote]
Update: Ceton has informed me that the reason the current InfiniTV4 driver sets their network interface to Public is due to a potential tuner discovery issue. Ceton is looking into how to safely change it to private.
I’m going to keep the tool available to allow users to reset the InfiniTV4 interface back to public. I’m going to keep mine at Private to do some additional troubleshooting.
[/quote]
Btw…I have a feeling the
Btw…I have a feeling the tuner discovery issue is the same background scanner issue that has plagued the HDHomeRun, HD-PVR w/ DVBLink and others.
A sympton of the issue is the “No Tuner Found” or “All tuners are currently in use” error when attempting to tune a channel. It occurs more frequently after having resumed from sleep or a prolonged system uptime.
A workaround is to disable background scanner with the registry ley below
Click Start and type regedit
Browse to:
Right click and choose New, DWORD.
Name the entry PeriodicScanEnabled and set the value to 0.
Restart the computer (or specifically the Windows Media Center Receiver service)
Note: By disabling background scanning via PeriodicScanEnabled you do lose some functionality, I’ll update with a list tomorrow (getting late and getting tired)
mikinho wrote:
Btw…I have
[quote=mikinho]
Btw…I have a feeling the tuner discovery issue is the same background scanner issue that has plagued the HDHomeRun, HD-PVR w/ DVBLink and others.
A sympton of the issue is the “No Tuner Found” or “All tuners are currently in use” error when attempting to tune a channel. It occurs more frequently after having resumed from sleep or a prolonged system uptime.
A workaround is to disable background scanner with the registry ley below
Click Start and type regedit
Browse to:
Right click and choose New, DWORD.
Name the entry PeriodicScanEnabled and set the value to 0.
Restart the computer (or specifically the Windows Media Center Receiver service)
Note: By disabling background scanning via PeriodicScanEnabled you do lose some functionality, I’ll update with a list tomorrow (getting late and getting tired)
[/quote]
What functionality do you loose by doing this reg hack?
Maybe I’m missing something
Maybe I’m missing something here, but I don’t understand why you would want to change the network type to private if it works as public. My understanding is that that setting determines the firewall rules Windows uses when connecting to that network and it is most secure when connecting to public networks.
I didn’t think that means that the network is actually available to the public, or am I missing some other setting you’re changing behind the scenes?
Depending on the firewall you
Depending on the firewall you use having it set to Public can make setup more difficult. Not that I recommend anything but MSE for HTPC usage…
Another option if you are anal like me and do not like seeing the Unknown Network listed is to set *NdisDeviceType to 1 for the InfiniTV interface. This changes the device to an Endpoint Mapper which is ignored by Windows when it does network identification
I didn’t add *NdisDeviceType feature to the tool since I knew that setting was previously set in the Ceton driver
While I don’t have a Ceton
While I don’t have a Ceton Tuner, I’m planning to use this for my laptop at home because Windows thinks that my wireless network is a private network but my wired network is public. Thanks. 🙂
The current Ceton installer
The current Ceton installer does not set-up the second unknown network and properly assigns binding order so Skype or other programs don’t try to grab the tuner instead of your network card. Just make sure you use http://www.cetoncorp.com/firmware/ceton_infinitv_setup_20110208_1_1_0_3.exe
or later when you install.
Thanks John. Â I meant to
Thanks John. I meant to update the post w/ that but obviously didn’t 🙂