Norton history indicates conhost is default blocked.
I had already tried allowing Conhost.exe.
It is a hidden file by default.
I can choose to show all hidden files and I can then see it in C:\Windows\System32.
A Windows search also shows it and at that location.
However when I attempt to allow or unblock it through Program Control, it's not on that list and I can't add it because it doesn't show up when I browse to System32.
The Conhost.exe entry in Norton History is most likely a Norton Product Tamper Protection event. Conhost is being blocked from accessing Norton files and processes. The entry has nothing to do with the firewall (which is why you do not see Conhost there) and would not be related to the issue you are having. Conhost is often logged in the Tamper Protection events - this is normal and can be disregarded.
Looking at the documentation, the port configurations listed below are needed. Norton should be able to do this automatically. First, go to the Smart Firewall Advanced Settings and use the Reset option to revert the Norton Firewall to its default settings. Then go to the Network Security Map and make sure your Network Trust Level is "Shared." Some of the ports listed below are blocked if the trust level is "Protected." If the Ceton is listed as a generic device make sure it is also "Shared."
If you still have problems, you can set the network or device trust level to "Full Trust.' You should not need to manually set any of the following ports, but if all else fails, you may need to do so - but I would put this in the "last resort" catagory.
Non-Windows firewall users need to open the following ports; Name UDP/TCP Port Range In/Out RTP UDP 5001-5016 IN SSDP UDP 1900 IN/OUT RTSP TCP 554 OUT UPnP TCP 2869 IN/OUT WMDRM UDP 5757-5772 OUT
Looking at the documentation, the port configurations listed below are needed. Norton should be able to do this automatically. First, go to the Smart Firewall Advanced Settings and use the Reset option to revert the Norton Firewall to its default settings. Then go to the Network Security Map and make sure your Network Trust Level is "Shared." Some of the ports listed below are blocked if the trust level is "Protected." If the Ceton is listed as a generic device make sure it is also "Shared."
If you still have problems, you can set the network or device trust level to "Full Trust.' You should not need to manually set any of the following ports, but if all else fails, you may need to do so - but I would put this in the "last resort" catagory.
Non-Windows firewall users need to open the following ports; Name UDP/TCP Port Range In/Out RTP UDP 5001-5016 IN SSDP UDP 1900 IN/OUT RTSP TCP 554 OUT UPnP TCP 2869 IN/OUT WMDRM UDP 5757-5772 OUT
Thank you again for your help!
I had set the Ceton tuner card to Full trust but still a black screen and no live tv.
Media Center also wants to run cable card setup again.
In NIS2011 that was the only setting change I had to make after a default install.
I set to Full trust and eveything worked perfectly.
It's a new different issue with NIS2012.
After restoring my NIS2011 Ghost image, all problems are gone.
I vote for running the setup again. Also check the Ceton support site for documentation and a wizard that could be useful. If the Network Security Map is showing the card as Full Trust, there is nothing that the firewall should be blocking. Before opening ports, which could make matters worse or leave your PC vulnerable to attack if done incorrectly, I would fully investigate some of the other avenues.
I vote for running the setup again. Also check the Ceton support site for documentation and a wizard that could be useful. If the Network Security Map is showing the card as Full Trust, there is nothing that the firewall should be blocking. Before opening ports, which could make matters worse or leave your PC vulnerable to attack if done incorrectly, I would fully investigate some of the other avenues.
I'm concerned with rerunning setup as that could require re-entering data for series recording.
As I've said, NIS2011 works flawlessly.
NIS2012 work fine as long as I turn off program control.
I know not to use the pc with program control turned off but clearly, it's blocking something and nothing is indicated as blocked in program control or history (except what I mentioned previously in thread).
When I have time, I may reinstall NIS2012 and set program control to require me to allow or block instead of program control doing that automatically. That may give me a handle on who the bad actor is. I'll document each instance requiring my authorization. If all works well after that, I'll switch program control to automatic.
My custom settings I will have already made will remain and overide whatever auto program control would have chosen.