Miracast connection error after joining ad domain











up vote
0
down vote

favorite












I have a situation where a laptop always ends up have a connection error when trying to establish a screen share using Miracast. Shockingly this phenomenon began right after joining the lenovo laptop to active directory domain. I have attempted to solve the problem by first uninstalling and reinstalling the dual wireless driver.



Secondly Modified Wireless Network Policy Permissions in order resolve the problem by way of going to the Network Permissions tab within the wireless network policy and then in the policy setting Don't allow WiFi Direct groups and unchecking this setting.



Also specifically for WIDI Config Firewall Exception Rules. I went into Windows Firewall Area via Control Panel > System and Security > Windows Firewall > Allow program or feature through firewall . Selected Wireless display and Allowed for Domain, Private and Public. Then click allow another app. Browse and navigated to C:WindowsSystem32WUDFHost.exe and added this rule.



I also checked the policies Computer Configuration > Policies > Windows Settings >Security Settings > Wireless Network (IEEE 802.11) Policies



Double clicked the setting for wireless policies and a dialog box appeared.
Opened the Network Permissions tab and selected Allow everyone to create all user profiles.



Finally opened regedit on laptop and then checked if the following registry entry ComputerHKEY_LOCAL_MACHINESOFTWAREPoliciesMicrosoftWindowsWireless
with the intention to delete the the XP folder if it existed there but there was no folder like that.



At the end of the day all of the above didn't do the trick. What am i missing here. Any suggestions. Workarounds ?










share|improve this question






















  • It may depend on policies at the domain level as those take precedence over local policies.
    – GabrielaGarcia
    Aug 30 at 20:04










  • @GabrielaGarcia can you shed some more light on that. Since i am already aware that some policies taking precedence but which one is taking precedence. ? I already detailed the policy settings in my above question.
    – john zuh
    Sep 1 at 21:30










  • I meant that if there are policies at the domain level (AD) preventing it, then it doesn't matter what you do locally because those polices will be overridden .
    – GabrielaGarcia
    Sep 2 at 19:06










  • @GabrielaGarcia All settings stated above were referring to none other but domain level policies. If all of the above have been double checked for precedence and nothing was found what could be causing this ?
    – john zuh
    Sep 2 at 20:07










  • what could be causing this ? If as you say it's at the domain level then sorry, I have no idea. It wasn't my understanding though because you started by saying the problem happened when the machine joined the domain and then mentioned things like WiFi and firewall settings, and registry which I understood as being done in the computer itself.
    – GabrielaGarcia
    Sep 2 at 20:13

















up vote
0
down vote

favorite












I have a situation where a laptop always ends up have a connection error when trying to establish a screen share using Miracast. Shockingly this phenomenon began right after joining the lenovo laptop to active directory domain. I have attempted to solve the problem by first uninstalling and reinstalling the dual wireless driver.



Secondly Modified Wireless Network Policy Permissions in order resolve the problem by way of going to the Network Permissions tab within the wireless network policy and then in the policy setting Don't allow WiFi Direct groups and unchecking this setting.



Also specifically for WIDI Config Firewall Exception Rules. I went into Windows Firewall Area via Control Panel > System and Security > Windows Firewall > Allow program or feature through firewall . Selected Wireless display and Allowed for Domain, Private and Public. Then click allow another app. Browse and navigated to C:WindowsSystem32WUDFHost.exe and added this rule.



I also checked the policies Computer Configuration > Policies > Windows Settings >Security Settings > Wireless Network (IEEE 802.11) Policies



Double clicked the setting for wireless policies and a dialog box appeared.
Opened the Network Permissions tab and selected Allow everyone to create all user profiles.



Finally opened regedit on laptop and then checked if the following registry entry ComputerHKEY_LOCAL_MACHINESOFTWAREPoliciesMicrosoftWindowsWireless
with the intention to delete the the XP folder if it existed there but there was no folder like that.



At the end of the day all of the above didn't do the trick. What am i missing here. Any suggestions. Workarounds ?










share|improve this question






















  • It may depend on policies at the domain level as those take precedence over local policies.
    – GabrielaGarcia
    Aug 30 at 20:04










  • @GabrielaGarcia can you shed some more light on that. Since i am already aware that some policies taking precedence but which one is taking precedence. ? I already detailed the policy settings in my above question.
    – john zuh
    Sep 1 at 21:30










  • I meant that if there are policies at the domain level (AD) preventing it, then it doesn't matter what you do locally because those polices will be overridden .
    – GabrielaGarcia
    Sep 2 at 19:06










  • @GabrielaGarcia All settings stated above were referring to none other but domain level policies. If all of the above have been double checked for precedence and nothing was found what could be causing this ?
    – john zuh
    Sep 2 at 20:07










  • what could be causing this ? If as you say it's at the domain level then sorry, I have no idea. It wasn't my understanding though because you started by saying the problem happened when the machine joined the domain and then mentioned things like WiFi and firewall settings, and registry which I understood as being done in the computer itself.
    – GabrielaGarcia
    Sep 2 at 20:13















up vote
0
down vote

favorite









up vote
0
down vote

favorite











I have a situation where a laptop always ends up have a connection error when trying to establish a screen share using Miracast. Shockingly this phenomenon began right after joining the lenovo laptop to active directory domain. I have attempted to solve the problem by first uninstalling and reinstalling the dual wireless driver.



Secondly Modified Wireless Network Policy Permissions in order resolve the problem by way of going to the Network Permissions tab within the wireless network policy and then in the policy setting Don't allow WiFi Direct groups and unchecking this setting.



Also specifically for WIDI Config Firewall Exception Rules. I went into Windows Firewall Area via Control Panel > System and Security > Windows Firewall > Allow program or feature through firewall . Selected Wireless display and Allowed for Domain, Private and Public. Then click allow another app. Browse and navigated to C:WindowsSystem32WUDFHost.exe and added this rule.



I also checked the policies Computer Configuration > Policies > Windows Settings >Security Settings > Wireless Network (IEEE 802.11) Policies



Double clicked the setting for wireless policies and a dialog box appeared.
Opened the Network Permissions tab and selected Allow everyone to create all user profiles.



Finally opened regedit on laptop and then checked if the following registry entry ComputerHKEY_LOCAL_MACHINESOFTWAREPoliciesMicrosoftWindowsWireless
with the intention to delete the the XP folder if it existed there but there was no folder like that.



At the end of the day all of the above didn't do the trick. What am i missing here. Any suggestions. Workarounds ?










share|improve this question













I have a situation where a laptop always ends up have a connection error when trying to establish a screen share using Miracast. Shockingly this phenomenon began right after joining the lenovo laptop to active directory domain. I have attempted to solve the problem by first uninstalling and reinstalling the dual wireless driver.



Secondly Modified Wireless Network Policy Permissions in order resolve the problem by way of going to the Network Permissions tab within the wireless network policy and then in the policy setting Don't allow WiFi Direct groups and unchecking this setting.



Also specifically for WIDI Config Firewall Exception Rules. I went into Windows Firewall Area via Control Panel > System and Security > Windows Firewall > Allow program or feature through firewall . Selected Wireless display and Allowed for Domain, Private and Public. Then click allow another app. Browse and navigated to C:WindowsSystem32WUDFHost.exe and added this rule.



I also checked the policies Computer Configuration > Policies > Windows Settings >Security Settings > Wireless Network (IEEE 802.11) Policies



Double clicked the setting for wireless policies and a dialog box appeared.
Opened the Network Permissions tab and selected Allow everyone to create all user profiles.



Finally opened regedit on laptop and then checked if the following registry entry ComputerHKEY_LOCAL_MACHINESOFTWAREPoliciesMicrosoftWindowsWireless
with the intention to delete the the XP folder if it existed there but there was no folder like that.



At the end of the day all of the above didn't do the trick. What am i missing here. Any suggestions. Workarounds ?







windows-10 wireless-networking group-policy windows-firewall miracast






share|improve this question













share|improve this question











share|improve this question




share|improve this question










asked Aug 30 at 19:15









john zuh

53




53












  • It may depend on policies at the domain level as those take precedence over local policies.
    – GabrielaGarcia
    Aug 30 at 20:04










  • @GabrielaGarcia can you shed some more light on that. Since i am already aware that some policies taking precedence but which one is taking precedence. ? I already detailed the policy settings in my above question.
    – john zuh
    Sep 1 at 21:30










  • I meant that if there are policies at the domain level (AD) preventing it, then it doesn't matter what you do locally because those polices will be overridden .
    – GabrielaGarcia
    Sep 2 at 19:06










  • @GabrielaGarcia All settings stated above were referring to none other but domain level policies. If all of the above have been double checked for precedence and nothing was found what could be causing this ?
    – john zuh
    Sep 2 at 20:07










  • what could be causing this ? If as you say it's at the domain level then sorry, I have no idea. It wasn't my understanding though because you started by saying the problem happened when the machine joined the domain and then mentioned things like WiFi and firewall settings, and registry which I understood as being done in the computer itself.
    – GabrielaGarcia
    Sep 2 at 20:13




















  • It may depend on policies at the domain level as those take precedence over local policies.
    – GabrielaGarcia
    Aug 30 at 20:04










  • @GabrielaGarcia can you shed some more light on that. Since i am already aware that some policies taking precedence but which one is taking precedence. ? I already detailed the policy settings in my above question.
    – john zuh
    Sep 1 at 21:30










  • I meant that if there are policies at the domain level (AD) preventing it, then it doesn't matter what you do locally because those polices will be overridden .
    – GabrielaGarcia
    Sep 2 at 19:06










  • @GabrielaGarcia All settings stated above were referring to none other but domain level policies. If all of the above have been double checked for precedence and nothing was found what could be causing this ?
    – john zuh
    Sep 2 at 20:07










  • what could be causing this ? If as you say it's at the domain level then sorry, I have no idea. It wasn't my understanding though because you started by saying the problem happened when the machine joined the domain and then mentioned things like WiFi and firewall settings, and registry which I understood as being done in the computer itself.
    – GabrielaGarcia
    Sep 2 at 20:13


















It may depend on policies at the domain level as those take precedence over local policies.
– GabrielaGarcia
Aug 30 at 20:04




It may depend on policies at the domain level as those take precedence over local policies.
– GabrielaGarcia
Aug 30 at 20:04












@GabrielaGarcia can you shed some more light on that. Since i am already aware that some policies taking precedence but which one is taking precedence. ? I already detailed the policy settings in my above question.
– john zuh
Sep 1 at 21:30




@GabrielaGarcia can you shed some more light on that. Since i am already aware that some policies taking precedence but which one is taking precedence. ? I already detailed the policy settings in my above question.
– john zuh
Sep 1 at 21:30












I meant that if there are policies at the domain level (AD) preventing it, then it doesn't matter what you do locally because those polices will be overridden .
– GabrielaGarcia
Sep 2 at 19:06




I meant that if there are policies at the domain level (AD) preventing it, then it doesn't matter what you do locally because those polices will be overridden .
– GabrielaGarcia
Sep 2 at 19:06












@GabrielaGarcia All settings stated above were referring to none other but domain level policies. If all of the above have been double checked for precedence and nothing was found what could be causing this ?
– john zuh
Sep 2 at 20:07




@GabrielaGarcia All settings stated above were referring to none other but domain level policies. If all of the above have been double checked for precedence and nothing was found what could be causing this ?
– john zuh
Sep 2 at 20:07












what could be causing this ? If as you say it's at the domain level then sorry, I have no idea. It wasn't my understanding though because you started by saying the problem happened when the machine joined the domain and then mentioned things like WiFi and firewall settings, and registry which I understood as being done in the computer itself.
– GabrielaGarcia
Sep 2 at 20:13






what could be causing this ? If as you say it's at the domain level then sorry, I have no idea. It wasn't my understanding though because you started by saying the problem happened when the machine joined the domain and then mentioned things like WiFi and firewall settings, and registry which I understood as being done in the computer itself.
– GabrielaGarcia
Sep 2 at 20:13












1 Answer
1






active

oldest

votes

















up vote
0
down vote



accepted










Works after uninstalling VPN software from affected client. Most third party VPN solutions identify WiFi Direct (the underlying technology for Miracast) as a "Split Tunnel" and deem it a risk to security so they disable the functionality.






share|improve this answer





















    Your Answer








    StackExchange.ready(function() {
    var channelOptions = {
    tags: "".split(" "),
    id: "3"
    };
    initTagRenderer("".split(" "), "".split(" "), channelOptions);

    StackExchange.using("externalEditor", function() {
    // Have to fire editor after snippets, if snippets enabled
    if (StackExchange.settings.snippets.snippetsEnabled) {
    StackExchange.using("snippets", function() {
    createEditor();
    });
    }
    else {
    createEditor();
    }
    });

    function createEditor() {
    StackExchange.prepareEditor({
    heartbeatType: 'answer',
    autoActivateHeartbeat: false,
    convertImagesToLinks: true,
    noModals: true,
    showLowRepImageUploadWarning: true,
    reputationToPostImages: 10,
    bindNavPrevention: true,
    postfix: "",
    imageUploader: {
    brandingHtml: "Powered by u003ca class="icon-imgur-white" href="https://imgur.com/"u003eu003c/au003e",
    contentPolicyHtml: "User contributions licensed under u003ca href="https://creativecommons.org/licenses/by-sa/3.0/"u003ecc by-sa 3.0 with attribution requiredu003c/au003e u003ca href="https://stackoverflow.com/legal/content-policy"u003e(content policy)u003c/au003e",
    allowUrls: true
    },
    onDemand: true,
    discardSelector: ".discard-answer"
    ,immediatelyShowMarkdownHelp:true
    });


    }
    });














    draft saved

    draft discarded


















    StackExchange.ready(
    function () {
    StackExchange.openid.initPostLogin('.new-post-login', 'https%3a%2f%2fsuperuser.com%2fquestions%2f1353896%2fmiracast-connection-error-after-joining-ad-domain%23new-answer', 'question_page');
    }
    );

    Post as a guest















    Required, but never shown

























    1 Answer
    1






    active

    oldest

    votes








    1 Answer
    1






    active

    oldest

    votes









    active

    oldest

    votes






    active

    oldest

    votes








    up vote
    0
    down vote



    accepted










    Works after uninstalling VPN software from affected client. Most third party VPN solutions identify WiFi Direct (the underlying technology for Miracast) as a "Split Tunnel" and deem it a risk to security so they disable the functionality.






    share|improve this answer

























      up vote
      0
      down vote



      accepted










      Works after uninstalling VPN software from affected client. Most third party VPN solutions identify WiFi Direct (the underlying technology for Miracast) as a "Split Tunnel" and deem it a risk to security so they disable the functionality.






      share|improve this answer























        up vote
        0
        down vote



        accepted







        up vote
        0
        down vote



        accepted






        Works after uninstalling VPN software from affected client. Most third party VPN solutions identify WiFi Direct (the underlying technology for Miracast) as a "Split Tunnel" and deem it a risk to security so they disable the functionality.






        share|improve this answer












        Works after uninstalling VPN software from affected client. Most third party VPN solutions identify WiFi Direct (the underlying technology for Miracast) as a "Split Tunnel" and deem it a risk to security so they disable the functionality.







        share|improve this answer












        share|improve this answer



        share|improve this answer










        answered Dec 7 at 13:15









        john zuh

        53




        53






























            draft saved

            draft discarded




















































            Thanks for contributing an answer to Super User!


            • Please be sure to answer the question. Provide details and share your research!

            But avoid



            • Asking for help, clarification, or responding to other answers.

            • Making statements based on opinion; back them up with references or personal experience.


            To learn more, see our tips on writing great answers.





            Some of your past answers have not been well-received, and you're in danger of being blocked from answering.


            Please pay close attention to the following guidance:


            • Please be sure to answer the question. Provide details and share your research!

            But avoid



            • Asking for help, clarification, or responding to other answers.

            • Making statements based on opinion; back them up with references or personal experience.


            To learn more, see our tips on writing great answers.




            draft saved


            draft discarded














            StackExchange.ready(
            function () {
            StackExchange.openid.initPostLogin('.new-post-login', 'https%3a%2f%2fsuperuser.com%2fquestions%2f1353896%2fmiracast-connection-error-after-joining-ad-domain%23new-answer', 'question_page');
            }
            );

            Post as a guest















            Required, but never shown





















































            Required, but never shown














            Required, but never shown












            Required, but never shown







            Required, but never shown

































            Required, but never shown














            Required, but never shown












            Required, but never shown







            Required, but never shown







            Popular posts from this blog

            flock() on closed filehandle LOCK_FILE at /usr/bin/apt-mirror

            Mangá

             ⁒  ․,‪⁊‑⁙ ⁖, ⁇‒※‌, †,⁖‗‌⁝    ‾‸⁘,‖⁔⁣,⁂‾
”‑,‥–,‬ ,⁀‹⁋‴⁑ ‒ ,‴⁋”‼ ⁨,‷⁔„ ‰′,‐‚ ‥‡‎“‷⁃⁨⁅⁣,⁔
⁇‘⁔⁡⁏⁌⁡‿‶‏⁨ ⁣⁕⁖⁨⁩⁥‽⁀  ‴‬⁜‟ ⁃‣‧⁕‮ …‍⁨‴ ⁩,⁚⁖‫ ,‵ ⁀,‮⁝‣‣ ⁑  ⁂– ․, ‾‽ ‏⁁“⁗‸ ‾… ‹‡⁌⁎‸‘ ‡⁏⁌‪ ‵⁛ ‎⁨ ―⁦⁤⁄⁕