This lead me to think the autochannel feature on Meraki was the culprit, so I disabled all but 2 channels on the nearby access points but to no avail. I also tinkered with a lot of other settings in the radio settings page of the Meraki dashboard but none of those options really made a difference.
Air Marshal found the Miracast devices,but we haven't set it up to do anything with rogue ap's so they just got marked as "uncontained". To make sure Air Marshall wasn't the problem I've whitelisted the Miracast devices.
Hello - curious to hear if any resolution besides killing the 5g spectrum has worked? We are in the same scenario, as we have all our conference room TV/displays using Microsoft Wireless Display Adapters. Laptops will seemingly connect after initial power on, and then disconnect and never re-connect again.
Unfortunately no, I did not find a proper way to get it working without disabling 5Ghz in the Meraki network. Also good to know you tried using widi adapters, my next step was to buy a bunch of Miracast dongles and see if that works.
I did however have a so called "AirServer" lying around which is basically an intel nuc which supports Miracast, Airplay and Chromecast. I've tested this with the 5G network on, and for the last few months it kept running smoothly and I was able to use the Windows 10 miracast function every time.
I hope this fixed the problem for you. I remember when I was tinkering with the Meraki settings, sometimes it would just start to work again and held up for a couple days, I hope this is not the case with your setup.
Wanted to follow-up with a discovery we've had on this. The MAC whitelisting has worked on several Microsoft Surface models, and a few Lenovo ThinkPad's. We have one Dell Latitude 3379, with Intel 7265 NIC that still will not work. It initially connects to the WiDi adapter and screen, but then disconnects within 10secs. Air Marshall shows that it's whitelisted when it sees it within the Dashboard. Head scratching moment for sure....
Another follow-up: this continues to work well for us as a solution. Although tedious, we are able to one-by-one add a new laptop's WiDi adapter to the Air Marshall whitelist and have it remain connected. It would be extremely helpful to be able to leave a note/comment about who's MAC address was added, and very extremely helpful if we could get it to whitelist through to all networks.
In the Air Marshall, add an entry for Matches Wildcard and put the value of 'DIRECT-*' (without quotes). This solved my problem with miracast. If you look in the WLAN-autoconfig logs, the miracast tries to connect with a SSID that begins with DIRECT-. I hope this helps someone out because it caused me a bunch of headaches.
But latest driver 22.130.0.5 causes an issue with Miracast on LG. In most cases I just cannot establish Miracast connection and even if connect successful to display connection is not stable and disconnect in few secs.
Also I found out that on v22.70 Intel driver resolved issue on LG Miracast. So it looks like Intel has been aware of some compatibility issue with Miracast on LG. In 22.70 it was fixed and in 22.130.0.5 is broken again
I wrote that driver version 22.120.1.9 works without issue. Issue is with latest intel driver 22.130.0.5. This one is not stable on LG Miracast connection. Also mentioned that similar problem was already seen in earlier versions and solved in 22.70 (according to Intel releases notes)
Thanks for your patience. I would like to let you know that Intel has discontinued marketing and development for Intel Wireless Display (Intel WiDi) and Intel Pro Wireless Display (Intel Pro WiDi) applications and related receiver certification programs effective immediately.
Because the Miracast standard is natively supported in Windows 10 and Windows 8.1 operating systems for wireless display capabilities with strong user experience, Intel is redirecting resources and focusing on future areas of growth.
intel Widi and Miracast are two different things. WiDi was discontinued SEVEN YEARS AGO. Intel still supports miracast. It seems like you didn't even read his post. He clearly showed the release notes from a recent (less than seven years ago) driver:
"Also I found out that on v22.70 Intel driver resolved issue on LG Miracast. So it looks like Intel has been aware of some compatibility issue with Miracast on LG. In 22.70 it was fixed and in 22.130.0.5 is broken again
Intel does not verify all solutions, including but not limited to any file transfers that may appear in this community. Accordingly, Intel disclaims all express and implied warranties, including without limitation, the implied warranties of merchantability, fitness for a particular purpose, and non-infringement, as well as any warranty arising from course of performance, course of dealing, or usage in trade.
When I connect to a TV, the wifi speed slows to a crawl. I am able to connect an old Dell XPS18 that has an AC7260 as well as a Note5 and with both of these devices, when i connect, I am able to get the full speed from the wifi (150Mbs)
Has anyone else run into this? I should note that I am running the out of the box image on my laptop and am considering wiping and doing a clean install from windows. I'm not sure if maybe there's some option set in the factory image that may cause this.
Not sure exactly what this does (or doesn't do when disabled) but I was starting to worry as from what I've been reading, this laptop is actually geared toward taking advantages of the features of WCU.
Something I just noticed though, I was testing Wifi speed with fast.com and noticed it didn't breakdown download/upload speed so I tried a few others like speedtest.net and Bing's speedtest and found that while the download speed is
Just noticed the same issue, during a local network transfer of a file while using miracast. I was getting about 3-7 Mbps transfer speed which was unacceptable. Checked the solution and after changing the value of "Receive Segment Coalescing State", i went back to full Wifi speed.
I received my Archer T2U Plus today, plugged it in, and downloaded/installed the Win10 driver from the support page, as directed by the instruction booklet. It immediately started working and I was able to connect my PC to my WiFi network. I now had two connections - my preexisting Ethernet connection and my Wifi connection. Excellent!
Then I went to the "Projecting to this PC" Settings page, which was the whole point of getting this product. And, like the last two WiFi adapters I bought, it still says "This device doesn't support receiving Miracast, so you can't project to it wirelessly":
Thank you for your help. I ended up submitting a support request, and am getting help from a senior support engineer. So I'm going to let this thread go silent for a while. However, once the issue gets resolved, I'll post the solution here so that other people with the same problem can see it.
My PC is hardwired and does not natively have wifi so I had the same issue as OP. Once I plugged in the adapter and downloaded the drivers, I was able to easily project to and from this PC. I DID NOT have to connect to wifi to use the miracast feature. I was able to stay hardwired the entire time I was using miracast features. This leads me to conclude that the T2U Nano does support miracast. Hope that helps.
@MandoMK3 It came in yesterday, and I just installed it. NO love. I think the code problem is that there's something deep down in the chipset of the computer's motherboard that doesn't support Miracast. So no matter what WiFi dongle I put on top of it, it just won't work.
Running windows 10 through bootcamp on a new 2020 iMac 27" 3.8GHz Core i7 AMD Pro 5500 XT 8 GB - I am unable to Miracast TO the iMac from my employer's supplied PC laptop as windows on the iMac states Miracast is unsupported.
Does anyone know how I can enable Miracast (through bootcamp and running windows 10) on the iMac? Is it a driver issue? Someone has suggested if I use a USB wifi dongle this may enable the Miracast reception I am looking for, but don't really know enough about Miracast to understand if that would work.
No, still waiting on someone with an actual clue to either supply a solution or explain why it won't work. I suspect its either a driver issue or limitation of either the wifi or graphics card, but can't find any details specific to the components used to confirm. If I find an answer (either way) I will come back and post it here.
It is very likely that it is the wifi hardware, not the wifi driver. I have read about examples where people managed to miracast from laptops to desktops after plugging in an Archer T2U Nano to the desktop (note: only working for miracasting from laptop to the desktop, not the other way around). See more here: _projectionmiracast_only_working_oneway/
I have a strange issue on some hp elitebook 840 G3 in my business. I don't understand the problem but some elitebook cannot use miracast because appear message "you device doens't support miracast" when i try use connect button in Windows 10. But in the past it worked. I already updating OS, wireless drivers and bios but this not fix the problem. Also, if i run the command "netsh wlan show driver" appear
MiracleCast is an open-source implementation of the Miracast technology (also: Wifi-Display (WFD)). It is based on the OpenWFD research project and will supercede it. We focus on proper and tight integration into existing Linux-Desktop systems, compared to OpenWFD which was meant as playground for fast-protoyping.
Despite its name and origin, the project itself is not limited to Miracast. We can support any kind of display-streaming with just a minimal amount of additional work. However, Miracast will remain the main development target due to its level of awareness.
d3342ee215