But, on the Avast Friends page, although it appears one can add new 'Friends' IP ranges, and when I click under the last one it highlights the empty boxes ready to enter a new definition, it refuses to accept any input - can't paste, can't type. Unfortunately I have no idea how - or if it is even possible - to switch the Miracast connecting between Laptop and Roku to using the 192.168.0.0 - 192.168.255.255 range. So the Avast Firewall thinks they are from a public address outside the private netwrork and is blocking them according to the predefined rule that shows in the logs. However, digging through the Avast 'old settings' to find the 'Friends' settings page that describes what addresses are to be counted as Friends/private by the Avast Firewall, while the 192.168.0.0 - 192.168.255.255 addresses are defined as friends, the 172.16.0.0 - 172.31.255.255 range is not. The Miracast casting from the laptop to the Roku is using addresses in that range for the communications - this is on my private home network, and the Firewall profile is set to Private.
MIRACAST ROKU ANDROID
(Note: I CAN stream media to the Roku, which is DLNA and uses a different standard, addresses, ports etc and I can also Miracast screen mirror my Android phone to the Roku just fine I just can't Miracast screen mirror the laptop to the Roku).Įvery attempt to Connect to the Roku produces Firewall logged blocks of inbound connections from 172.29.243.225 to 172.29.243.226, TCP In by C:\Windows\System32\WUDFHost.exe blocked because of rule 'Public Tcp/Udp In Block'.Īfter further fumbling around trying to look up things I used to know but have forgotten, I have reminded myself that the address range 172.16.0.0 - 172.31.255.255 is reserved as private addresses in a network, like 192.168.0.0 - 192.168.255.255. And after stumbling blindly around I finally found the Firewall logs, switched the filter to just show block events, and indeed found blocks coinciding with each failed attempt to Connect with the Roku for Miracast screen mirroring. Took me far too long and too much looking in the wrong places (thinking it might be the W10 1809-1903 update) before finally remembering last time, when it worked, I was using Comodo Internet Security, whereas now I'm using Avast Premier. Last time I used screen mirroring from the laptop to the Roku a few months ago (via the Connect button in the Action Centre) it worked fine now it isn't working - the connection starts to connect, then stops before the laptop screen would appear on the TV, and I get a failure to connect message from the laptop.
MIRACAST ROKU WINDOWS 10
I have a windows 10 laptop (1903) and also a Roku Express connected to my TV: almost all the time I use the Roku separately from the laptop for NOW TV and Amazon Prime on the TV, but very rarely I want to use the Miracast screen mirroring to put my laptop display on the TV via the Roku (the TV itself does DLNA, so I can use it as a media renderer for media servers on the laptop, but not directly to mirror the screen). Was a time I was good and knowledgable about internet stuff - disability and brain-fogging medications mean I now can't remember most of what I used to know or think clearly, so while I think I have a specific question, I'm going to start with the problem and what I think I've slowly figured out in case I'm actually onto the wrong thing and somebody can see that.