none
Wireless profile export/import (encryption key import failed when xml profile imported successfully)

    Question

  • This is my steps.

    • netsh wlan export profile name="SSID_NAME"
    • netsh wlan add profile filename="Wireless Network Connection-SSID_NAME.xml"

    Cmd told me "Profile SSID_NAME is added on interface Wireless Network Connection" But I was still unable to connect to the wireless. System told me "A network security key is required to connect to SSID_NAME" in the notification area of the right bottom corner of the screen. Then I checked the properties of the wireless network connection. Please see the following screenshots.

    Screenshot 1: The properties of the wireless after import

    Screenshot 2: When clicking "Show characters"

    jeudi 1 décembre 2011 13:08

Réponses

  • I had the same issue.  Here was a great explanation and solution:

    http://theether.net/kb/100166


    Grant Scheffert

    • Marqué comme réponse 高麻雀 mardi 18 septembre 2012 12:13
    jeudi 15 mars 2012 13:28
  • It will work on different machines if you change the text in the protected tags to false and put the plain text key between the key material tags like this:

    <protected>false</protected>

    <keyMaterial>plaintextkey</keyMaterial>

    Be aware that anyone who opens/edits the .xml wireless profile will be able to see the key in plain text, but at least you can use the netsh command to import the key for different machines.  I do this at work for my users, I just make sure to keep the .xml file on a flash drive.

    • Marqué comme réponse 高麻雀 mardi 18 septembre 2012 12:14
    lundi 17 septembre 2012 21:30

Toutes les réponses

  • Here is the notification message after import. Attached for makeup.

    jeudi 1 décembre 2011 13:12
  • BTW, here is the content of the XML file that was exported/imported.

    <?xml version="1.0"?>
    <WLANProfile xmlns="http://www.microsoft.com/networking/WLAN/profile/v1">
     <name>SSID_NAME</name>
     <SSIDConfig>
      <SSID>
       <hex>457861724C414E</hex>
       <name>SSID_NAME</name>
      </SSID>
     </SSIDConfig>
     <connectionType>ESS</connectionType>
     <connectionMode>auto</connectionMode>
     <MSM>
      <security>
       <authEncryption>
        <authentication>WPA2PSK</authentication>
        <encryption>AES</encryption>
        <useOneX>false</useOneX>
       </authEncryption>
       <sharedKey>
        <keyType>passPhrase</keyType>
        <protected>true</protected>
        <keyMaterial>01000000D08C9DDF0115D1118C7A00C04FC297EB010000007707C487F39D7740A1CAF66FB111AF64000000000200000000001066000000010000200000005CB800463EE944493146A002CD346ACF2740CA34D7060C10D206DDBC3AA4CEFD000000000E8000000002000020000000106A6D123802E525EE14E0760572696230712D1F29731405E43DBA4BD7B49083100000005DC76FE99232D0D971A995ACAABED30040000000CE4EB81E9D3C9BCD6784D42C3DE1CB2860737972DA03FEE27C78D878331AE023EB63DF71474ACCD9BFB83D608D693C92A2F642F620F986F84F096D0EA81ED49A</keyMaterial>
       </sharedKey>
      </security>
     </MSM>
    </WLANProfile>


    • Modifié 高麻雀 samedi 3 décembre 2011 02:34
    jeudi 1 décembre 2011 13:16
  • Is anyone know the reason and how to fix it?
    jeudi 8 décembre 2011 10:13
  • I'm sorry I have to be up this question. Thanks.
    mardi 13 décembre 2011 03:36
  • Sorry, up again.
    jeudi 15 décembre 2011 06:33
  • I'm sorry, up again.

    jeudi 22 décembre 2011 08:16
  • Any experts?

    vendredi 23 décembre 2011 08:16
  • won't stop until being fixed

    lundi 26 décembre 2011 08:13
  • Good good study, day day up!

    jeudi 5 janvier 2012 06:28
  • The problem is that the encrypted password was encrypted with a machine-specific key on the machine you exported the config from. You could import that xml file back into the same machine and it would work just fine. But it won't work on a different machine because the 2nd machine doesn't have the same machine-specific key and can't decrypt the password.

    I'm not exactly sure what netsh uses as the machine-specific key or whether its possible to clone it from one system to another.

    Im wrestling with the same issue.

    lundi 9 janvier 2012 16:06
  • I had the same issue.  Here was a great explanation and solution:

    http://theether.net/kb/100166


    Grant Scheffert

    • Marqué comme réponse 高麻雀 mardi 18 septembre 2012 12:13
    jeudi 15 mars 2012 13:28
  • It will work on different machines if you change the text in the protected tags to false and put the plain text key between the key material tags like this:

    <protected>false</protected>

    <keyMaterial>plaintextkey</keyMaterial>

    Be aware that anyone who opens/edits the .xml wireless profile will be able to see the key in plain text, but at least you can use the netsh command to import the key for different machines.  I do this at work for my users, I just make sure to keep the .xml file on a flash drive.

    • Marqué comme réponse 高麻雀 mardi 18 septembre 2012 12:14
    lundi 17 septembre 2012 21:30
  • Thanks Grant and Mark. I will try the solution when I'm free. It looks like it should be OK. :-)
    mardi 18 septembre 2012 12:13
  • It will work on different machines if you change the text in the protected tags to false and put the plain text key between the key material tags like this:

    <protected>false</protected>

    <keyMaterial>plaintextkey</keyMaterial>

    Perfect!!! Just what I needed! Since this will be handled by local GPO on login, pulling from a UNC share that nobody except for a select few have access to, I'm not too worried by it's lack of security.

    mercredi 11 septembre 2013 20:16
  • Why is it so secret, that your SSID is ExarLAN?
    mercredi 29 janvier 2014 15:34