ClearFoundation

Hello, I'm looking for some suggestions. While attempting to watch videos from www.cbs.com I am receiving an error stating that I'm using a pop up blocker and the website is blocked. I am not currently using any pop up blockers because I'm using the feature built in to ClearOS. When I disable the built-in blocker on the Gateway/Webproxy page Banner and Pop-up Blocker the website loads just fine. I've added the site to the web site bypass list as cbs.com but the videos are still being blocked. Does anyone have any suggestions on how to fix this?

Thanks,
Toasty

Bump does anyone have any ideas on this issue?

Bumping again for assistance

cbs.com may not be associated with the actual IP that is used by the streaming server. That is quite common for streaming media.

To overcome this you need to sleuth a bit. Start by temporarily disabling the pup-up blocker, connect, and start streaming. While doing that, try one of the following:

Save the pup-up page as a link to your desktop. In most case, the sending server to go into the bypass rules is stated in the link's properties (the execption is Torrents, see below). Also, saving a link could be disabled in webpage.

If that does not work, try watching the network traffic report in Webconfig while still streaming. Monitoring your internal NIC (in most case eth1) gives you the local (receiving) IP as well as the sending external IP or server name. You should be able to easily identfy the stream providing the content (it will be constantly near the top) and then enter the sending server name or IP into the bypass rules.

Beware that this works for traditional single server streaming but not for Torrent-like streaming where large numbers of random servers are sending bits and pieces that are then merged into a single stream on your machine. Anyhow, its worthwhile trying.

Peter

Thanks for the help Peter, part of the issue was the hidden but built in add blocker in chrome. The other issue was the ad stream which I've found until they change it again. It now seems to be working as it should be. Thanks

Glad you solved it and thanks for reporting back.

Knowing Google's business model, an add blocker in Chrome sounds like an oxymoron.

Peter