Welcome
Welcome to vistafirewallcontrol

You are currently viewing our boards as a guest, which gives you limited access to view most discussions and access our other features. By joining our free community, you will have access to post topics, communicate privately with other members (PM), respond to polls, upload content, and access many other special features. In addition, registered members also see less advertisements. Registration is fast, simple, and absolutely free, so please, join our community today!

Chromecast

Chromecast

Postby grail » Thu Nov 05, 2015 11:17 pm

Chromecast is setup and working. When I change to enable all mode in the firewall, I can cast from my desktop. Switch back to normal mode and nothing - "No cast devices found." Nothing is blocked in events, all green arrows, and Chrome itself is set to enable all. Suggestions?

Cheers and thanks
Last edited by grail on Mon Nov 09, 2015 4:08 pm, edited 1 time in total.
grail
 
Posts: 5
Joined: Thu Nov 05, 2015 10:49 pm

Re: Chromecast

Postby VistaFirewallControl » Fri Nov 06, 2015 4:25 pm

If the firewall blocks an activity the related blocking event should be saved into access.log file (of the installation folder), listed in the Events pane, and the related notification balloon is shown as well.
Do you have the related application listed in Programs? What permissions?
Did not you check “Disable Notification Balloon” and “Disable in Events and Logfile (EditApplication dialog) for a (set of) application(s) or Settings/Do not show Log Balloon?

Also please take into account that sometimes a function of an application may be implemented in another application/service in fact, so the related network activity may be issued in the name of other application/service.

Do you have a link describing the connectivity details?
We suspect the following scenario. The casting related app sends a broadcast request trying to find the device. The request being blocked once was not resent again, so any attempts to translate to the TV are failed. Could it be helpful to restart the casting application (or the entire PC) and then try to detect the broadcasting application (and the following) communication with the device?
Did you try to switch off WindowsFirewall (WF) temporarily? The default WF policy may block “unknown” incoming connections (replies to the broadcast). So in spite of the broadcast could be sent successfully, replies (“I’m here”) from the device can be blocked by WF.

Unfortunately we have no the required device to experiment with.
Looking forward to hear from you.
Can you send us the access.log file?
VistaFirewallControl
Site Admin
 
Posts: 1493
Joined: Fri Mar 27, 2009 11:25 am

Re: Chromecast

Postby grail » Mon Nov 09, 2015 4:37 pm

Windows firewall is disabled
Balloons all show everything enabled
Chromecast is an extension of Chrome and casts what is on the screen. I assumed that if Chrome was enable all then Chromecast wouldn't be a problem :?:
Watching "events" W 10 Firewall Control when I click on the "cast" button, I do not see anything as disabled.
Relevant log copied below (or at least what I think I relevant :o ). First group is in normal mode. Second group is enable all mode. All after reboot. The casting device was not reset because it is a PITA to set it up when using an Apple router (has to be set up using a wireless connection for a wired connection to work and Apple routers don't seem to like Chromecasts)

Thanks

Normal Mode
Code: Select all
015:11:09|11:29:01|Allowed|IPv4 TCP 127.0.0.1:1268(49634)|Google Chrome|EnableAll/EnableAll Outgoing|C:\program files (x86)\google\chrome\application\chrome.exe
2015:11:09|11:29:01|Allowed|IPv4 UDP ssl.google-analytics.com/74.125.228.222:443(55653)|Google Chrome|EnableAll/EnableAll Outgoing|C:\program files (x86)\google\chrome\application\chrome.exe
2015:11:09|11:29:03|Allowed|IPv4 UDP 224.0.0.251:5353(5353)|Google Chrome|EnableAll/EnableAll Outgoing|C:\program files (x86)\google\chrome\application\chrome.exe
2015:11:09|11:29:03|Allowed|IPv6 UDP [ff02::fb]:5353(5353)|Google Chrome|EnableAll/EnableAll OutgoingV6|C:\program files (x86)\google\chrome\application\chrome.exe
2015:11:09|11:29:03|Allowed|IPv4 UDP 239.255.255.250:1900(55654)|Google Chrome|EnableAll/EnableAll Outgoing|C:\program files (x86)\google\chrome\application\chrome.exe
2015:11:09|11:29:03|Allowed|IPv4 TCP 127.0.0.1:1269(49636)|Google Chrome|EnableAll/EnableAll Outgoing|C:\program files (x86)\google\chrome\application\chrome.exe
2015:11:09|11:29:03|Allowed|IPv4 TCP 127.0.0.1:1270(49638)|Google Chrome|EnableAll/EnableAll Outgoing|C:\program files (x86)\google\chrome\application\chrome.exe
2015:11:09|11:29:03|Allowed|IPv4 TCP 127.0.0.1:1271(49640)|Google Chrome|EnableAll/EnableAll Outgoing|C:\program files (x86)\google\chrome\application\chrome.exe
2015:11:09|11:29:03|Allowed|IPv4 TCP 127.0.0.1:1272(49642)|Google Chrome|EnableAll/EnableAll Outgoing|C:\program files (x86)\google\chrome\application\chrome.exe
2015:11:09|11:29:03|Allowed|IPv4 TCP 127.0.0.1:1273(49644)|Google Chrome|EnableAll/EnableAll Outgoing|C:\program files (x86)\google\chrome\application\chrome.exe
2015:11:09|11:29:05|Allowed|IPv4 TCP 127.0.0.1:1274(49646)|Google Chrome|EnableAll/EnableAll Outgoing|C:\program files (x86)\google\chrome\application\chrome.exe


Enable All Mode
Code: Select all
2015:11:09|11:31:06|Allowed|IPv4 TCP 127.0.0.1:1284(49667)|Google Chrome|EnableAll/EnableAll Outgoing|C:\program files (x86)\google\chrome\application\chrome.exe
2015:11:09|11:31:08|Allowed|IPv4 TCP 127.0.0.1:1285(49669)|Google Chrome|EnableAll/EnableAll Outgoing|C:\program files (x86)\google\chrome\application\chrome.exe
2015:11:09|11:31:12|Allowed|IPv4 TCP 127.0.0.1:1286(49671)|Google Chrome|Mode Override Outgoing|C:\program files (x86)\google\chrome\application\chrome.exe
2015:11:09|11:31:12|Allowed|IPv4 TCP 127.0.0.1:1287(49673)|Google Chrome|Mode Override Outgoing|C:\program files (x86)\google\chrome\application\chrome.exe
2015:11:09|11:31:13|Allowed|IPv4 TCP clients2.google.com/74.125.228.206:443(49350)|Google Chrome|Mode Override Outgoing|C:\program files (x86)\google\chrome\application\chrome.exe
2015:11:09|11:31:13|Allowed|IPv4 UDP www.google-analytics.com/216.58.217.142:443(55908)|Google Chrome|Mode Override Outgoing|C:\program files (x86)\google\chrome\application\chrome.exe
2015:11:09|11:31:16|Allowed|IPv4 TCP ssl.google-analytics.com/216.58.217.136:443(49602)|Google Chrome|Mode Override Outgoing|C:\program files (x86)\google\chrome\application\chrome.exe
2015:11:09|11:31:19|Allowed|IPv4 TCP 127.0.0.1:1288(49675)|Google Chrome|Mode Override Outgoing|C:\program files (x86)\google\chrome\application\chrome.exe
2015:11:09|11:31:19|Allowed|IPv4 UDP ssl.google-analytics.com/216.58.217.136:443(60777)|Google Chrome|Mode Override Outgoing|C:\program files (x86)\google\chrome\application\chrome.exe
2015:11:09|11:31:21|Allowed|IPv4 UDP 224.0.0.251:5353(5353)|Google Chrome|Mode Override Outgoing|C:\program files (x86)\google\chrome\application\chrome.exe
2015:11:09|11:31:21|Allowed|IPv6 UDP [ff02::fb]:5353(5353)|Google Chrome|Mode Override OutgoingV6|C:\program files (x86)\google\chrome\application\chrome.exe
2015:11:09|11:31:21|Allowed|IPv4 UDP 239.255.255.250:1900(60778)|Google Chrome|Mode Override Outgoing|C:\program files (x86)\google\chrome\application\chrome.exe
2015:11:09|11:31:21|Allowed|IPv4 TCP 127.0.0.1:1289(49677)|Google Chrome|Mode Override Outgoing|C:\program files (x86)\google\chrome\application\chrome.exe
2015:11:09|11:31:22|Allowed|IPv4 UDP 10.0.1.2:44170(60779)|Google Chrome|Mode Override Outgoing|C:\program files (x86)\google\chrome\application\chrome.exe
grail
 
Posts: 5
Joined: Thu Nov 05, 2015 10:49 pm

Re: Chromecast

Postby PietO » Mon Nov 09, 2015 10:45 pm

VistaFirewallControl wrote:Unfortunately we have no the required device to experiment with.

If needed i could give it a try: i've got a similar device (EZcast) but never casted via Chrome-extension.
PietO
 
Posts: 192
Joined: Wed Mar 02, 2011 12:09 pm

Re: Chromecast

Postby VistaFirewallControl » Tue Nov 10, 2015 10:12 am

>I assumed that if Chrome was enable all then Chromecast wouldn't be a problem

The behavior depends on implementation. Very often a program (or an extension) calls a third functionality via API, so the related network activity may be issued in the name of a third party (or the system) service. For instance almost every time when a program tried to resolve domain name to IP (DNS resolving), the related DNS network activity is made in the name of Host Process.
There are just several multicasting activity ff02::, 224/8,239/8 in the log, but it was allowed (outgoing at least). all the rest is Chrome interprocess communication.

>Watching "events" W 10 Firewall Control when I click on the "cast" button, I do not see anything as disabled.

Are there any blocked events in the log?
via IGMP protocol as well?
We suspect the device discovery was made _earlier_.
The communication probably starts before the casting is initiated.

>The casting device was not reset because it is a PITA to set it up when using an Apple router

We could suggest the following experiment to find what permission is set incorrectly.
- Set Mode:EnableAll
- check the device casting is OK.
- clear/reset the log (in settings)
- set Mode:Normal
- reproduce the casting problem (should be reproducible we believe)
- check the log for _any_ blocked events (or send us the log file)

If the firewall blocks, the related blocked event should be picked up and saved.
VistaFirewallControl
Site Admin
 
Posts: 1493
Joined: Fri Mar 27, 2009 11:25 am

Re: Chromecast

Postby grail » Fri Nov 13, 2015 10:20 pm

Please do - thanks

PietO wrote:
VistaFirewallControl wrote:Unfortunately we have no the required device to experiment with.

If needed i could give it a try: i've got a similar device (EZcast) but never casted via Chrome-extension.
grail
 
Posts: 5
Joined: Thu Nov 05, 2015 10:49 pm

Re: Chromecast

Postby grail » Fri Nov 13, 2015 11:01 pm

VistaFirewallControl wrote:>I assumed that if Chrome was enable all then Chromecast wouldn't be a problem

The behavior depends on implementation. Very often a program (or an extension) calls a third functionality via API, so the related network activity may be issued in the name of a third party (or the system) service. For instance almost every time when a program tried to resolve domain name to IP (DNS resolving), the related DNS network activity is made in the name of Host Process.
There are just several multicasting activity ff02::, 224/8,239/8 in the log, but it was allowed (outgoing at least). all the rest is Chrome interprocess communication.

>Watching "events" W 10 Firewall Control when I click on the "cast" button, I do not see anything as disabled.

Are there any blocked events in the log?

>> There were no blocking events in the log

VistaFirewallControl wrote:via IGMP protocol as well?

>> Any advice for this with a Mac rotuer?

VistaFirewallControl wrote: We suspect the device discovery was made _earlier_.
The communication probably starts before the casting is initiated.

>The casting device was not reset because it is a PITA to set it up when using an Apple router

We could suggest the following experiment to find what permission is set incorrectly.
- Set Mode:EnableAll
- check the device casting is OK.
- clear/reset the log (in settings)
- set Mode:Normal
- reproduce the casting problem (should be reproducible we believe)
- check the log for _any_ blocked events (or send us the log file)

If the firewall blocks, the related blocked event should be picked up and saved.


>> Think I found it. Enable all to normal while casting produced a blocked event (however I have been unable to repeat this - need a reboot or something?)
Code: Select all
2015:11:13|17:27:05|Blocked|IPv4 UDP 10.0.1.7:56054(54295)|Google Chrome|Detection Outgoing|C:\program files (x86)\google\chrome\application\chrome.exe


Suggestions?

Thanks for your assistance
grail
 
Posts: 5
Joined: Thu Nov 05, 2015 10:49 pm

Re: Chromecast

Postby VistaFirewallControl » Sat Nov 14, 2015 12:27 pm

There is no magic here.
If there is everything is OK in Mode:EnableAll, and something does not work in Mode:Normal, the firewall blocked something, so the permissions should be changed.
All the blocks made by the firewall are registered (saved, displayed and listed)
The log is rotating and limited with 1MB size (the settings pane) by default. So the log includes 1MB of the last events by default.
Could it be a reason of you did not see the related blocked events?

>(however I have been unable to repeat this

>2015:11:13|17:27:05|Blocked|IPv4 UDP 10.0.1.7:56054(54295)|Google Chrome|Detection Outgoing|C:\program files (x86)\google\chrome\application\chrome.exe

It’s the detection event of Chrome listing. The event is probably too old, as Chrome was already listed.


If the block is stable the event should be reproducible.
So we could suggest settings/logsize to a higher value, checking no programs have checked EditApplication/DisableEvents and LogFile and repeating

- Set Mode:EnableAll
- check the device casting is OK. Is it OK?
- clear/reset the log (in settings)
- set Mode:Normal
- reproduce the casting problem (Is it reproducible?)
- check the log for _any_ blocked events
VistaFirewallControl
Site Admin
 
Posts: 1493
Joined: Fri Mar 27, 2009 11:25 am

Re: Chromecast

Postby grail » Thu Nov 19, 2015 8:23 pm

This event is exactly what was blocked - the timing was correct.

2015:11:13|17:27:05|Blocked|IPv4 UDP 10.0.1.7:56054(54295)|Google Chrome|Detection Outgoing|C:\program files (x86)\google\chrome\application\chrome.exe

Chromecast was on and casting. Nothing blocked in allow all mode. I returned the firewall back to normal mode and this one block showed up in the events pane. I noted the time and the event address. I then went into the log, pulled it, and pasted it here.

Is there a way to specifically allow the event noted above? Chrome is "enable all" right now and shouldn't block anything - correct(?)

Thanks
grail
 
Posts: 5
Joined: Thu Nov 05, 2015 10:49 pm

Re: Chromecast

Postby VistaFirewallControl » Fri Nov 20, 2015 12:30 pm

Did you follow the suggested steps precisely?
The block can be made by other (independent) service/application, not from Chrome only.

Regarding
2015:11:13|17:27:05|Blocked|IPv4 UDP 10.0.1.7:56054(54295)|Google Chrome|Detection Outgoing|C:\program files (x86)\google\chrome\application\chrome.exe

It’s the Detection (as listed) event. However we do not think it’s the event we are looking for.
Actually we believe Chrome was already listed before you started the step 1. So Chrome was already detected/listed, so in spite of it’s the blocking event, the block was made earlier.
Or did you mean the event time was after the “reproduce the casting problem" step.

> Is there a way to specifically allow the event noted above?

You can add 10.x.x.x enabling rule from the rules repository to Chrome.
Programs/Chrome/F3/AddFromRepository (on the toolbar)/select 10.x.x.x./click OK (confirm adding)/click OK (confirm zone editing)

>Chrome is "enable all" right now and shouldn't block anything - correct(?)

Correct. We still believe the block was made by not Chrome, but by an independent involved service.
Typically HostProcess/System is involved in multicasting, we are not aware of Chrome specifics though.
Multicasting is a special type of communication. It requires some management on the system level (via IGMP at least). Such management is typically made by System/Host Process.
VistaFirewallControl
Site Admin
 
Posts: 1493
Joined: Fri Mar 27, 2009 11:25 am


Return to My App is blocked, What to do

Who is online

Users browsing this forum: No registered users and 0 guests

cron
suspicion-preferred